In this post, we share how Amazon Bedrock’s granular cost attribution works and walk through example cost tracking scenarios.

In your CUR 2.0, you can see which AWS Identity and Access Management (IAM) principals are calling Amazon Bedrock and what each is spending when you enable IAM principal data in your data export configuration, as shown in the following example:

Here, you can see that Alice is using Claude 4.6 Sonnet and Bob is using Claude 4.6 Opus, and what each is spending in input and output tokens. The following table shows what the line_item_iam_principal column contains for each identity type:

To aggregate costs by team, project, or cost center, add tags to your IAM principals. Tags flow to your billing data in two ways: