Part 2: Amazon Bedrock cost attribution with Amazon Athena and CUDOS | Amazon Web Services
Part 1 introduced granular cost attribution for Amazon Bedrock. This feature automatically traces every inference request back to the IAM principal that made the call. It showed how the new line_item_iam_principal column can give you per-user and per-application visibility. With optional cost allocation tags, you can also aggregate spend by team, project, or tenant using AWS Cost Explorer. With this approach, you can typically track usage at the granularity you want for any Bedrock-powered service or application, whether third-party tools like Claude Code or Codex or your own custom builds. This post shows how to visualize and analyze cost attribution for Amazon Bedrock through Amazon Athena queries and CUDOS dashboards.
First, this post shows you how to set up Cost and Usage Report (CUR) 2.0 through Data Exportsinstrumented with IAM principal data. Next, this post shows you how to query CUR data with Amazon Athena for analysis. It then...
Copyright of this story solely belongs to amazon.com. To see the full text click HERE
