From the source
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.






