This tutorial outlines how to visualize and analyze cost attribution for Amazon Bedrock. It focuses on using Amazon Athena queries and CUDOS dashboards to gain insight into Bedrock spending. The approach allows for tracking usage at a granular level for any Bedrock-powered service or application.
To begin, users must set up a CUR 2.0 data export and connect it to Amazon Athena. A critical step is enabling IAM principal data in the CUR 2.0 export. This populates the line_item_iam_principal column and associated IAM principal tags, which are essential for granular cost attribution.
Once CUR data is configured, it can be queried with Amazon Athena for analysis. Athena provides flexibility for aggregations, integration with various business intelligence tools, and chargeback processes. Additionally, CUDOS dashboards offer pre-built visuals tailored to an organization’s specific structure, including granular Bedrock cost and usage data.
Users need an AWS account with billing console access, IAM permissions for Cost and Usage Reports, S3, and Athena, and an S3 bucket for CUR data storage. Basic familiarity with SQL and the AWS Management Console is also required. Optional tools like Claude Code or Kiro-CLI can assist with automated setup.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
A tutorial details how to visualize and analyze Amazon Bedrock costs using Amazon Athena queries and CUDOS dashboards. This process involves setting up Cost and Usage Report (CUR) 2.0 with IAM principal data and then querying this data for granular cost attribution. This enables per-user and per-application visibility of Bedrock spend.