# Amazon — Cost attribution and controls for AI developer and productivity tools on Amazon Bedrock

- Company: Amazon (amazon.com)
- Announced: 2026-11-13T18:44:02+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/cost-attribution-and-controls-for-ai-developer-and-productivity-tools-on-amazon-bedrock/
- Record: https://forck.live/items/36023-cost-attribution-and-controls-for-ai-developer-and-productivity-tools-on
- Subject: Bedrock / Nova

Amazon's guide shows FinOps and AI platform teams how to attribute Amazon Bedrock inference spend to individual users through IAM identity, without instrumenting API calls. Bedrock records the IAM ARN of every caller, including the session name for federated users, and publishes it to CUR 2.0 in the line_item_iam_principal column, so per-user spend is queryable alongside the dollars. The approach works the same for any tool routing inference through the bedrock-runtime or bedrock-mantle endpoints, including Claude Code, Claude Desktop, OpenAI Codex, ChatGPT Work and OpenCode. The guide walks through configuring IAM Identity Center with an external identity provider, flowing session tags such as team and cost center into CUR 2.0, and querying the data with Amazon Athena. It notes that CUR aggregates usage per principal and per usage type for each export interval and does not contain per-request cost; per-prompt detail requires model invocation logs or request metadata tagging. Claude Platform on AWS and Claude for Enterprise route inference through Anthropic-managed infrastructure, where usage is visible in Anthropic's admin console and spend limits are enforced by Anthropic.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/cost-attribution-and-controls-for-ai-developer-and-productivity-tools-on-amazon-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.

---

Record: https://forck.live/items/36023-cost-attribution-and-controls-for-ai-developer-and-productivity-tools-on
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
