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

This AWS post lays out a five-stage, looped operating model for Amazon Bedrock cost management: attribute every dollar to an owner via IAM principal and session tags in CUR 2.0, make every request observable through model invocation logging and stamped request metadata, enforce budgets at one of three tiers (monitor-only, IAM deny on breach, or synchronous gateway blocking), optimize platform defaults such as intelligent prompt routing and prompt caching, and operate a scorecard with a review cadence. It notes that agentic workloads issue many invocations per task and scale token consumption with autonomy and context size rather than user interactions, and it addresses the shared-role attribution problem in LLM gateways. FinOps leads the attribution and operate stages, platform engineering leads observability, enforcement, and optimization, and the review is joint.