- Who
- AWS
- What
- explains how to track and cap Amazon Bedrock spend per IAM principal using CUR 2.0 and AWS Budgets
- Quote
This post shows how to get per-identity Amazon Bedrock cost visibility and enforceable spend limits using only AWS-native features, with no application code to write for the common case.
What happened
AWS authors explain how to track Amazon Bedrock costs by IAM user or role and enforce spend limits using cost allocation tags, Cost Explorer or CUR 2.0, and AWS Budgets. The walkthrough covers principal and session tags, Athena queries for detailed reporting, and budget actions that attach a Deny IAM policy. Budget data refreshes up to three times a day, and a shared role’s Deny action blocks everyone using it.
Read next
See the full storyAWS Details Cost Attribution and Spending Controls for AI Tools on Amazon BedrockThe story so far
AWS explains how to attribute Amazon Bedrock inference costs to individual users of AI coding and productivity tools, then compare ways to control their usage. The guide configures IAM Identity Center session identities and tags for CUR 2.0 reporting, with Athena queries and dashboard options for analyzing per-user costs. It also compares AWS Budgets, CloudWatch alarms with Lambda, DynamoDB quotas, and LLM gateways as spending controls. AWS’s earlier walkthrough covers tracking Bedrock costs by IAM user or role with cost allocation tags, Cost Explorer or CUR 2.0, and AWS Budgets actions that attach a Deny policy. Budgets refresh up to three times a day, so spending can exceed a threshold before an action runs. Newly applied cost allocation tags can take up to 24 hours to appear and another 24 hours after activation to populate billing data. A Deny policy on a shared role blocks everyone using that role.