Half 1 launched granular value attribution for Amazon Bedrock. This characteristic mechanically traces each inference request again to the IAM principal that made the decision. It confirmed how the brand new line_item_iam_principal column may give you per-user and per-application visibility. With non-compulsory value allocation tags, it’s also possible to mixture spend by staff, undertaking, or tenant utilizing AWS Value Explorer. With this strategy, you’ll be able to usually monitor utilization on the granularity you need for any Bedrock-powered service or utility, whether or not third-party instruments like Claude Code or Codex or your personal customized builds. This submit reveals find out how to visualize and analyze value attribution for Amazon Bedrock by Amazon Athena queries and CUDOS dashboards.<\/p>\n
First, this submit reveals you find out how to arrange Value and Utilization Report (CUR) 2.0 by Knowledge Exports instrumented with IAM principal knowledge. Subsequent, this submit reveals you find out how to question CUR knowledge with Amazon Athena for evaluation. It then introduces the brand new capabilities of CUDOS dashboards, together with granular Bedrock value and utilization knowledge. Whereas Athena supplies flexibility for aggregations, integration with completely different enterprise intelligence (BI) instruments, and chargeback processes, CUDOS provides pre-built visuals tailor-made to your group\u2019s particular construction.<\/p>\n
![\"Table](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-1.png\")
<\/p>\nInstance question output exhibiting Amazon Bedrock prices by IAM principal and utilization kind<\/p>\n<\/p><\/div>\n
Organising Value and Utilization Experiences (CUR 2.0)<\/h2>\n
Earlier than you’ll be able to analyze Amazon Bedrock prices, arrange a CUR 2.0 knowledge export and join it to Amazon Athena.<\/p>\n
Conditions<\/h3>\n
You want the next:<\/p>\n
An AWS account with billing console entry.
\n IAM permissions for Value and Utilization Experiences, S3, and Athena.
\n An S3 bucket for CUR knowledge storage.
\n Primary familiarity with SQL and the AWS Administration Console.
\n (Elective) Claude Code or Kiro-CLI for automated setup.<\/p>\n
Ensure you have the required IAM permissions.<\/p>\n
For Amazon Bedrock value attribution, you have to allow IAM principal knowledge in your CUR 2.0 export in order that the line_item_iam_principal column and related IAM principal tags are populated.<\/p>\n
Making a CUR 2.0 knowledge export with IAM principal knowledge<\/h3>\n
Observe the directions in Creating a normal knowledge export to arrange your CUR 2.0 export. When configuring the export, make sure that the next choices are a part of your ultimate configuration:<\/p>\n
![\"The](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-2.png\")
<\/p>\nMaking a CUR 2.0 commonplace knowledge export with caller identification (IAM principal) allocation knowledge enabled<\/p>\n<\/p><\/div>\n
In Extra export content material, choose the next checkboxes: <\/p>\n
Embrace caller identification (IAM principal) allocation knowledge \u2014 That is the important setting that populates the line_item_iam_principal column and surfaces IAM principal tags (prefixed with iamPrincipal\/) in your value knowledge.<\/p>\n
In Knowledge desk configurations: <\/p>\n
Time granularity: Choose Hourly for optimum element.<\/p>\n
In Knowledge export supply choices: <\/p>\n
File versioning: Choose Overwrite current report back to keep away from storing duplicate knowledge.<\/p>\n
Necessary: Enabling IAM principal knowledge will increase CUR file sizes as a result of utilization that was beforehand a single row is now expanded into a number of rows, one for every IAM principal that contributed to the utilization. For top-volume workloads with many distinct principals, plan your Amazon S3 storage accordingly and think about Amazon S3 Lifecycle insurance policies for older CUR information.<\/p>\n
It might take as much as 24 hours for AWS to ship your first CUR 2.0 report back to the S3 bucket.<\/p>\n
Connecting CUR 2.0 to Amazon Athena<\/h3>\n
With Amazon Athena, you’ll be able to question your CUR knowledge utilizing commonplace SQL with no infrastructure to handle. To streamline this setup, an non-compulsory agent.md ability repo is obtainable that you need to use with AI assistants like Claude Code, Kiro-CLI, or Codex. It automates the end-to-end means of connecting your Athena atmosphere to your CUR knowledge.<\/p>\n
Clone the repo (git clone https:\/\/github.com\/aws-samples\/sample-cur-iam-principal-bedrock-tracking).
\n Launch Claude Code (claude) or Kiro CLI (kiro) on this listing.
\n Immediate: \u201cLearn agent.md and comply with its workflow to arrange Value and Utilization Report monitoring and run the Amazon Bedrock-by-principal question for the present month.\u201d<\/p>\n
You might also comply with the handbook setup steps.<\/p>\n
When you plan to deploy the CUDOS dashboard as effectively, you’ll be able to deploy it from AWS CloudFormation. This additionally deploys the Athena question database as a part of the method.<\/p>\n
As soon as deployed, here’s a pattern take a look at question within the Athena Question Editor that you need to use:<\/p>\n
\n line_item_iam_principal,
\n line_item_usage_type,
\n line_item_unblended_cost
\n –# Be aware: exchange your_cur_table_name, like `cid_data_export.cur2`
\nFROM your_cur_table_name
\nWHERE line_item_product_code in (‘AmazonBedrock’, ‘AmazonBedrockService’)
\n AND line_item_iam_principal IS NOT NULL
\nLIMIT 10;\n <\/div>\n
If this returns rows with IAM principal ARNs and Bedrock utilization sorts, your setup is full and prepared for deeper evaluation.<\/p>\n
Athena question patterns for Bedrock value monitoring<\/h2>\n
Together with your CUR 2.0 knowledge accessible in Athena, now you can reply granular value attribution questions utilizing SQL. This part supplies three progressively refined question patterns that cowl the commonest evaluation situations.<\/p>\n
Be aware: Within the following queries, exchange your_cur_table_name with the precise title of your CUR Athena desk (for instance, cid_data_export.cur2).<\/p>\n
Question 1: Bedrock prices by IAM principal and utilization kind<\/h3>\n
This question supplies a whole breakdown of Amazon Bedrock spending by caller identification and mannequin utilization. It solutions the query: \u201cWho is asking which fashions, and the way a lot are they spending?\u201d<\/p>\n
\n line_item_iam_principal,
\n line_item_usage_type,
\n SUM(line_item_usage_amount) AS total_tokens,
\n SUM(line_item_unblended_cost) AS total_cost
\nFROM your_cur_table_name
\nWHERE line_item_product_code in (‘AmazonBedrock’, ‘AmazonBedrockService’)
\n AND billing_period = DATE_FORMAT(CURRENT_DATE, ‘%Y-%m’)
\n AND line_item_iam_principal IS NOT NULL
\n — AND line_item_usage_type LIKE ‘%Sonnetpercentinput%’
\nGROUP BY
\n line_item_iam_principal,
\n line_item_usage_type
\nORDER BY total_cost DESC;\n <\/div>\n
Instance output:<\/p>\n
line_item_iam_principal
\n line_item_usage_type
\n total_tokens
\n total_cost<\/p>\n
arn:aws:sts::123456789012:assumed-role\/ChatApp\/session-1
\n USW2-anthropic.claude-opus-4-8-mantle-cache-write-tokens-standard
\n 1629.5
\n $11.2029<\/p>\n
arn:aws:sts::123456789012:assumed-role\/DocProcessor\/batch-7
\n USW2-Claude4.6Sonnet-output-tokens
\n 68.579
\n $1.131<\/p>\n
arn:aws:sts::123456789012:assumed-role\/ClaudeCode\/chat
\n USW2-Claude4.6Sonnet-cache-write-input-token-count
\n 831.74
\n $3.4309<\/p>\n
arn:aws:iam::123456789012:consumer\/alice
\n USW2-Claude4.6Sonnet-input-tokens
\n 17.33
\n $0.0572<\/p>\n
Evaluation ideas:<\/p>\n
Use LIKE patterns corresponding to line_item_usage_type LIKE ‘%Sonnetpercentoutput%’ or %nova% to filter for particular fashions.
\n The line_item_iam_principal column comprises the total ARN. For assumed roles, the session title after the final \/ identifies the particular consumer or session.<\/p>\n
Question 2: Prices damaged down by identified IAM principal tags<\/h3>\n
Whenever you\u2019ve tagged your IAM principals with dimensions like staff, undertaking, or costcenter (and activated these tags as value allocation tags), they seem in your CUR 2.0 knowledge as a part of the tags columns, with the iamPrincipal\/ prefix adopted by your tag key. This question teams prices by these tags to reply questions like: \u201cHow a lot did the engineering staff spend on Bedrock this month?\u201d or \u201cWhat\u2019s the full Bedrock value for the chatbot undertaking?\u201d<\/p>\n
By undertaking:<\/p>\n
\n tags[‘iamPrincipal\/project’] AS undertaking,
\n line_item_usage_type,
\n SUM(line_item_usage_amount) AS total_tokens,
\n SUM(line_item_unblended_cost) AS total_cost
\nFROM your_cur_table_name
\nWHERE line_item_product_code in (‘AmazonBedrock’, ‘AmazonBedrockService’)
\n AND billing_period = DATE_FORMAT(CURRENT_DATE, ‘%Y-%m’)
\n AND line_item_iam_principal IS NOT NULL
\nGROUP BY
\n tags[‘iamPrincipal\/project’],
\n line_item_usage_type
\nORDER BY total_cost DESC;\n <\/div>\n
Instance output:<\/p>\n
undertaking
\n line_item_usage_type
\n total_tokens
\n total_cost<\/p>\n
data-science
\n USW2-Claude4.5Sonnet-cache-write-input-token-count
\n 433.893
\n 1.789808625<\/p>\n
data-science
\n USW2-Claude4.6Sonnet-cache-read-input-token-count
\n 5372.659
\n 1.77297747<\/p>\n
engineering
\n USW2-Claude4.5Sonnet-input-tokens
\n 29.481
\n 0.0972873<\/p>\n
engineering
\n USW2-Claude4.5Sonnet-output-tokens
\n 31.102
\n 0.513183<\/p>\n
Be aware: This question returns outcomes provided that your IAM principals have been tagged with the related keys and people tags have been activated as value allocation tags.<\/p>\n
Question 3: Dynamic tag discovery utilizing UNNEST for unknown tag schemas<\/h3>\n
In massive organizations, it’s possible you’ll not know prematurely which tags have been utilized throughout all IAM principals. Totally different groups may use completely different tag keys, or new tags could be launched over time. The next instance reveals find out how to dynamically discover utilizing Athena\u2019s UNNEST operate.<\/p>\n
This question discovers all IAM principal tags getting used throughout your Bedrock workloads and reveals value allocation for every tag key-value pair:<\/p>\n
\n SELECT
\n t.key AS tag_name,
\n t.worth AS tag_value,
\n line_item_usage_type,
\n line_item_unblended_cost
\n FROM your_cur_table_name
\n CROSS JOIN UNNEST(tags) AS t(key, worth)
\n WHERE line_item_product_code IN (‘AmazonBedrock’, ‘AmazonBedrockService’)
\n AND line_item_iam_principal IS NOT NULL
\n AND line_item_iam_principal != ”
\n AND t.key LIKE ‘iamPrincipal\/%’
\n)
\nSELECT
\n tag_name || ‘: ‘ || tag_value AS tags,
\n line_item_usage_type,
\n SUM(line_item_unblended_cost) AS total_cost
\nFROM iam_principal_costs
\nGROUP BY tag_name, tag_value, line_item_usage_type
\nORDER BY total_cost DESC;\n <\/div>\n
Actual-world use case: Multi-service value comparability<\/h2>\n
Take into account a platform staff working a number of AI-powered companies. For instance, the staff may run a doc summarization pipeline (DocProcessor) and a customer-facing chatbot (ChatApp). The staff can assign every service to its personal IAM function. With the question patterns from the previous part, you’ll be able to isolate how the spend for every service traits with the next question:<\/p>\n
\n line_item_iam_principal,
\n line_item_usage_type,
\n SUM(line_item_usage_amount) AS total_usage,
\n SUM(line_item_unblended_cost) AS total_cost
\nFROM your_cur_table_name
\nWHERE line_item_product_code IN (‘AmazonBedrock’, ‘AmazonBedrockService’)
\n AND billing_period = DATE_FORMAT(CURRENT_DATE, ‘%Y-%m’)
\n AND line_item_iam_principal IS NOT NULL
\n AND (
\n line_item_iam_principal LIKE ‘%DocProcessor%’
\n OR line_item_iam_principal LIKE ‘%ChatApp%’
\n )
\nGROUP BY
\n line_item_iam_principal,
\n line_item_usage_type
\nORDER BY total_cost DESC;\n <\/div>\n
Instance output:<\/p>\n
line_item_iam_principal
\n line_item_usage_type
\n total_usage
\n total_cost<\/p>\n
arn:aws:sts::123456789012:assumed-role\/ChatApp\/session-1
\n USE1-Claude4.6Sonnet-output-tokens
\n 4,800,000
\n $72.00<\/p>\n
arn:aws:sts::123456789012:assumed-role\/ChatApp\/session-1
\n USE1-Claude4.6Sonnet-input-tokens
\n 2,900,000
\n $8.70<\/p>\n
arn:aws:sts::123456789012:assumed-role\/DocProcessor\/batch-7
\n USE1-NovaLite-output-tokens
\n 6,100,000
\n $1.46<\/p>\n
arn:aws:sts::123456789012:assumed-role\/DocProcessor\/batch-7
\n USE1-NovaLite-input-tokens
\n 3,200,000
\n $0.19<\/p>\n
From this output, the platform staff can reply questions like:<\/p>\n
Which utility is the highest contributor to this month\u2019s Bedrock spend? On this instance, ChatApp accounts for over $80 utilizing Claude 4.6 Sonnet, whereas DocProcessor prices below $5 utilizing Nova Lite.<\/p>\n
May we cut back prices by utilizing a distinct mannequin for every workload? DocProcessor is already on Nova Lite (acceptable for simple summarization duties), however the staff may consider whether or not ChatApp might deal with some interactions with a lighter mannequin to cut back the $72 output-token value.<\/p>\n
Value of Athena queries<\/h2>\n
You pay just for the queries that you simply run. You might be charged based mostly on the quantity of knowledge scanned by every question. The console shows this info after every question, and this info can also be accessible within the Latest Queries tab within the Athena console.<\/p>\n
Athena queries are billed at $5 per TB scanned (with a ten MB minimal per question). As a result of our desk mechanically makes use of hive partition projection on billing_period, queries scoped to a single month solely scan the parquet information in that month\u2019s folder. Scans are usually effectively below 10 MB, which prices about $0.00005 per question (the ten MB minimal).<\/p>\n
To maintain prices low, at all times embody a WHERE billing_period = … filter and choose solely the columns you want reasonably than SELECT *.<\/p>\n
The Cloud Intelligence Dashboards framework<\/h2>\n
CUDOS dashboard is a part of the open supply Cloud Intelligence Dashboards (CID) framework, which you’ll deploy in your AWS account utilizing the supplied infrastructure as code (IaC) templates. The framework helps you drive monetary accountability and enhance operational effectivity throughout your AWS organizations. The CUDOS dashboard supplies detailed and actionable insights, supporting data-driven selections for value effectivity throughout your AWS infrastructure.<\/p>\n
Amazon Bedrock value and utilization insights in CUDOS<\/h3>\n
CUDOS model 5.8 introduces a complete Amazon Bedrock part within the AI\/ML tab, with full IAM principal value attribution help. The dashboard supplies:<\/p>\n
Versatile grouping dimensions: Group your Amazon Bedrock spend by IAM Principal, IAM Principal Tags (corresponding to Venture or Workforce), Mannequin\/Useful resource Group, Area, or another value taxonomy fields configured throughout dashboard deployment.
\n Value-per-million-tokens monitoring: A development line overlaid in your spend chart exhibiting how value per million tokens evolves over time, serving to you measure the affect of mannequin choice modifications or immediate optimization efforts, like caching for instance.<\/p>\n
The next determine reveals the Amazon Bedrock Abstract part within the AI\/ML tab of the CUDOS dashboard, grouped by IAM principal, with per-principal value breakdown and cost-per-million-tokens development.<\/p>\n
![\"CUDOS](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-3.png\")
<\/p>\nCUDOS dashboard exhibiting Amazon Bedrock spend grouped by IAM principal<\/p>\n<\/p><\/div>\n
Interactive drill-down filtering: Select any worth within the top-level spend chart (corresponding to a selected undertaking, principal, or account) and each different visible mechanically filters to that choice, letting you drill from a high-level overview into per-model and per-usage-type element with out navigating away from the dashboard.
\n Granular mannequin and utilization breakdown: Extra visuals, filtered by the top-level chart, present spend per mannequin, per utilization kind, and cost-per-million-tokens by mannequin, so you’ll be able to determine which fashions and token sorts are driving prices for a given staff or undertaking.<\/p>\n
Whenever you change the grouping to IAM Principal Tag Venture and select a selected undertaking (on this instance, \u201cchatbot-v2\u201d), all different visuals filter to point out solely that undertaking\u2019s spend. The visuals break down that spend by mannequin, utilization kind, and unit value traits.<\/p>\n
![\"CUDOS](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-4.png\")
<\/p>\nCUDOS dashboard exhibiting Amazon Bedrock spend grouped by IAM principal tag Venture, filtered to the chatbot-v2 undertaking<\/p>\n<\/p><\/div>\n
With these visuals, you’ll be able to shortly reply questions like \u201cWhich undertaking is driving probably the most output token prices?\u201d, \u201cIs our chatbot staff utilizing cost-efficient fashions?\u201d, or \u201cHow has our value per million tokens modified since we switched from Opus to Sonnet?\u201d, with out writing any SQL.<\/p>\n
Getting began with CUDOS<\/h3>\n
To get began with CUDOS, you’ll be able to discover the Bedrock part in an interactive demo dashboard. Observe the deployment information to arrange CUDOS in your group.<\/p>\n
When you\u2019re already utilizing CUDOS, comply with the replace steering to improve to model 5.8. It’s also possible to use the add organizational taxonomy so as to add IAM Principal knowledge to your current CUDOS dashboard.<\/p>\n
Clear up<\/h2>\n
First, drop the Athena desk and AWS Glue database (these are metadata, so no compute is working):<\/p>\n
Warning: Dropping the Athena desk and Glue database will take away your means to question CUR knowledge. You will have to recreate these sources following the previous part if you wish to analyze billing knowledge sooner or later.<\/p>\n
\naws glue delete-database –region us-east-1 –name your_cur_table_name\n <\/div>\n
Second, for those who not want the associated fee knowledge itself, disable the export within the AWS Billing and Value Administration console below Knowledge Exports and empty the S3 prefix it writes to. Be aware that is your uncooked billing historical past, so solely delete it for those who\u2019re positive.<\/p>\n
Lastly, filter any Athena question outcomes which have collected:<\/p>\n
There aren’t any crawlers, AWS Lambda features, or schedules to delete. Partition projection means the one ongoing value is S3 storage for the CUR information themselves, which is often pennies per 30 days.<\/p>\n
For cleansing up CUDOS, seek advice from the CUDOS dashboard teardown directions.<\/p>\n
Conclusion and subsequent steps<\/h2>\n
This two-part sequence walked by a whole toolkit for understanding and managing Amazon Bedrock inference prices:<\/p>\n
Half 1 launched granular value attribution: how Amazon Bedrock mechanically captures the IAM principal behind each inference name, and the way you need to use value allocation tags to mixture spend by staff, undertaking, or tenant.
\n Half 2 (this submit) confirmed you find out how to put that knowledge to work: establishing CUR 2.0 with IAM principal knowledge, querying value patterns in Amazon Athena, and evaluating spend throughout tasks and principals to tell value allocation selections. It additionally introduces the CUDOS dashboard, which supplies a complete AI\/ML sheet with related insights for Bedrock.<\/p>\n
Activate CUR 2.0 with caller identification knowledge within the AWS Billing console, join it to Athena utilizing the supplied agent.md file, and run your first cost-by-principal question. Monitor Bedrock adoption throughout your group with the CUDOS dashboard.<\/p>\n
![\"Abhi](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-5.png\")
<\/p>\n<\/p><\/div>\n![\"Brenno](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-6.png\")
<\/p>\n<\/p><\/div>\n![\"Yash](\"https:\/\/d2908q01vomqb2.cloudfront.net\/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59\/2026\/08\/10\/ML-21078-7.png\")
<\/p>\n<\/p><\/div>\n