Artificial Intelligence · 12.08.2026, 17:56 UTC
Part 2: Amazon Bedrock cost attribution with Amazon Athena and CUDOS
| Schweregrad | info |
|---|---|
| Kategorie | Artificial Intelligence |
| Quelle | AWS Machine Learning ↗ |
| Veröffentlicht | 12.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
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 Exports instrumented with IAM principal data. Next, this post shows you how to query CUR data with Amazon Athena for analysis. It then introduces the new capabilities of CUDOS dashboards, including granular Bedrock cost and usage data. While Athena provides flexibility for aggregations, integration with different business intelligence (BI) tools, and chargeback processes, CUDOS offers pre-built visuals tailored to your organization’s specific structure.
Example query output showing Amazon Bedrock costs by IAM principal and usage type Setting up Cost and Usage Reports (CUR 2.0) Before you can analyze Amazon Bedrock costs, set up a CUR 2.0 data export and connect it to Amazon Athena. Prerequisites You need the following: An AWS account with billing console …