AWS Adds Per-Identity Tracking and Budget Caps for Bedrock Spend
Start here
AWS published a method for tracking and capping Amazon Bedrock generative AI spending per IAM principal using only native AWS features. Bedrock automatically records the IAM user or role on every inference request, and those tags become cost allocation tags readable in Cost Explorer or CUR 2.0 exports, letting teams attribute spend to individual identities. An AWS Budget scoped to Bedrock and filtered to one identity or tag value can attach a budget action that applies a Deny IAM policy once a threshold is crossed. AWS says the common case needs no application code.
Generated from reports · updated 17 h ago
Report timeline
Follow the reports to see the event from different sides.
- AWS Machine Learning BlogTokenomics at Scale: Tracking and Capping Amazon Bedrock Spend per IAM Principal with CUR 2.0 and AWS Budgets
AWS shows how to track and cap Amazon Bedrock generative AI spend per IAM principal using only native features: Bedrock automatically records the IAM user or role on every inference request, and those tags become cost allocation tags readable in Cost Explorer or CUR 2.0 exports. An AWS Budget scoped to Bedrock and filtered to one identity or tag value can attach a budget action that applies a Deny IAM policy once a threshold is crossed, with no application code for the common case.
Heat for this event
Not enough continuous observations yet to draw a trend.