AWS Shows Per-User Cost Attribution for Bedrock AI Tools
AWS Machine Learning Blog explains how Amazon Bedrock traces inference calls to IAM principals and carries organizational tags into AWS Cost and Usage Reports and Cost Explorer, without requiring API changes or tool-specific instrumentation. The guide covers identity setup through AWS IAM Identity Center, reporting with Amazon Athena, and usage controls ranging from budgets to CloudWatch alarms, DynamoDB-based quotas, and gateway enforcement. AWS says the same endpoint-level approach applies to Claude Code, Claude Desktop, OpenAI Codex, ChatGPT Work, and OpenCode.
The guide provides a practical FinOps pattern for tracking and controlling AI inference spending by user across multiple developer tools routed through Bedrock.
Amazon Bedrock provides built-in, zero-instrumentation cost attribution that traces every inference call back to the IAM principal that made it. The identity flows along with organizational tags, into AWS Cost and Usage Reports (CUR 2.0) and AWS Cost Explorer while keeping data inside the AWS security boundary. This post shows you how to use these capabilities to answer three questions that every FinOps and AI Platform leader asks as AI tool adoption scales: What is the real per-user cost? Which teams generate the most spend, and does that spend correlate with the value they deliver? How should next year’s budget scale with headcount and adoption?
The approach works identically regardless of which AI coding or productivity tool makes the call. Claude Code, Claude Desktop, OpenAI Codex, ChatGPT Work, and OpenCode all invoke Amazon Bedrock through one of two inference endpoints: bedrock-runtime or bedrock-mantle, and Bedrock’s attribution mechanism operates at the endpoint layer, beneath any tool-specific logic. You configure identity propagation once, and every tool that routes inference through Bedrock inherits per-user cost visibility automatically.
By the end of this post, you will have AWS IAM Identity Center configured with your external identity provider for per-user attribution, session tags (team, cost center) flowing into CUR 2.0, Amazon Athena queries and dashboard options for ongoing cost visibility, and a clear understanding of Bedrock-native usage controls to enforce spending limits.
#Amazon Bedrock#AWS IAM Identity Center#AWS Cost and Usage Reports#AWS Cost Explorer#Amazon Athena#AWS CloudWatch#Amazon DynamoDB#AWS Budgets#Claude Code#Claude Desktop#OpenAI Codex#OpenCode