Amazon Bedrock Launches CUR 2.0 and AWS Budgets for Cost Control
The story so far
Amazon has released CUR 2.0 and AWS Budgets to track and limit per-user spending on Amazon Bedrock. Amazon Bedrock automatically records the identity of the caller, and users can assign tags through IAM hosts, activate cost allocation tags, and use CUR 2.0 or AWS Cost Explorer to report data, combining AWS Budgets to set budget actions to achieve spending limits. When the threshold is reached, budget actions will automatically apply Deny IAM policies. This solution is applicable to accounts that have used IAM roles and supports both static primary tags and dynamic session tags for identity mapping.
AI-written from the reports · Updated 22 hours ago
Coverage timeline
Follow the coverage to see every side of the story.
- AWS Machine Learning BlogHow Amazon Bedrock achieves cost attribution and control for AI development tools
Amazon Bedrock tracks every inference call to an IAM principal with built-in zero instrumentation cost attribution, passing identity information and organizational tags to AWS Cost and Usage Reports (CUR 2.0) and AWS Cost Explorer while keeping data within AWS security boundaries.
- AWS Machine Learning BlogHow to use CUR 2.0 and AWS Budgets to track and limit per-user Amazon Bedrock spending
Amazon Bedrock automatically records caller identity, users can assign tags through IAM hosts, activate cost allocation tags, and use CUR 2.0 or AWS Cost Explorer to report data, combined with AWS Budgets to set budget actions for spending limits. No application code needs to be written, when the threshold is reached, budget actions will automatically apply Deny IAM policies. This solution is suitable for accounts already using IAM roles, supporting both static primary tags and dynamic session tags for identity mapping.
Heat over time
- Now
- 5
- Peak
- 1014 Nov, 03:00
- 24h change
- -2%
Hover or tap the chart to see each hour; use the arrow keys on a keyboard.