Managing Amazon Bedrock costs end to end: A playbook for FinOps and platform teams

Amazon's playbook shows FinOps and platform teams how to attribute, observe, enforce, optimize and review Amazon Bedrock generative AI spend as a five-stage loop.

• It argues that comparing per-model token rates and shortening prompts does not answer which team spent what on which workload, or whether that spend stayed inside an approved budget.
• Agentic workflows issue many invocations per task and carry larger context, so token consumption scales with the autonomy granted and the context carried rather than with user interactions, the post says.
• Amazon Bedrock automatically attributes inference costs to the IAM principal that made the call across all models, with the caller's ARN landing in the line_item_iam_principal column of the AWS Cost and Usage Report 2.0.
• Coverage spans IAM users, roles, federated identities and API keys, and activated tags appear in AWS Cost Explorer under the IAM category within 24–48 hours.
• The post warns that an LLM gateway calling Bedrock through a single IAM role attributes every dollar to that one role, and recommends assuming the invocation role once per user with session names and tags, caching credentials for up to an hour.