Track generative AI costs with Amazon Bedrock inference profiles

Summary

When multiple departments share a single foundation model in Amazon Bedrock under one IAM role, usage aggregates into one billing line item, complicating department-level chargebacks and budget tracking. This issue can be resolved by deploying Amazon Bedrock application inference profiles wrapped around the shared foundation model and tagging each profile for cost allocation. The application layer determines the user department during authentication and passes the corresponding inference profile ARN as the model identifier. Once the designated cost allocation tag is activated in the AWS Billing and Cost Management console, usage separates into per-department line items in AWS Cost Explorer. This method incurs standard per-token model rates without extra charges for cost attribution.

Takeaways

1. 1

   Using an application inference profile incurs standard per-token pricing with no additional charges for cost attribution.

2. 2

   Cost allocation tags take 24 to 48 hours after activation in AWS Billing and Cost Management to display tagged costs in Cost Explorer.

3. 3

   Deleting an application inference profile immediately breaks applications relying on its ARN, and recreated profiles receive new ARNs.