# Amazon — Tokenomics at scale: Track and cap Amazon Bedrock spend per IAM principal with CUR 2.0 and AWS Budgets

- Company: Amazon (amazon.com)
- Announced: 2026-11-12T19:29:55+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/tokenomics-at-scale-track-and-cap-amazon-bedrock-spend-per-iam-principal-with-cur-2-0-and-aws-budgets/
- Record: https://forck.live/items/35502-tokenomics-at-scale-track-and-cap-amazon-bedrock-spend-per-iam-principal-with
- Subject: Bedrock / Nova

Amazon's guide shows how to attribute and cap Amazon Bedrock generative AI spend per IAM principal using only AWS-native features, with no application code for the common case. Amazon Bedrock records the IAM user or role behind every inference request automatically, so no change to model inference calls is needed. Organizations activate those tags as cost allocation tags, then read the data in Cost Explorer or a CUR 2.0 export for line-item analysis. Enforcement comes from an AWS Budget scoped to Amazon Bedrock and filtered to one identity or tag value, with a budget action that applies a Deny IAM policy when the threshold is crossed. Where several people share one role, principal tags cannot tell them apart, so session tags passed at role assumption time are used instead; up to 50 principal or session tags are allowed per IAM user or role. A tag key appears in the cost allocation list only after the principal has made at least one Amazon Bedrock call.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/tokenomics-at-scale-track-and-cap-amazon-bedrock-spend-per-iam-principal-with-cur-2-0-and-aws-budgets/:

> Generative AI spend is hard to attribute. Before an organization expands AI access, CFOs and CTOs usually want three answers: what do we spend per person or per team, can we cap it, and how much work does it take to get there.
> 
> In our previous post, Tokenomics at Scale: How Jamf Built Real-Time Spend Enforcement for Amazon Bedrock , we explained a custom enforcement loop built on AWS IAM Identity Center , Amazon Athena over Amazon Bedrock model invocation logs , and AWS Lambda . This approach gives near-real-time control, but it requires code you then own and operate.
> 
> 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. The approach relies on three things: IAM principal attribution , which Amazon Bedrock records automatically; AWS Cost and Usage Reports (CUR) 2.0 or AWS Cost Explorer for reporting; and AWS Budgets with budget actions for enforcement. By the end, you will have per-identity cost reporting and an automatic guardrail that restricts Amazon Bedrock access when a threshold is crossed.
> 
> Solution overview

---

Record: https://forck.live/items/35502-tokenomics-at-scale-track-and-cap-amazon-bedrock-spend-per-iam-principal-with
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
