AWS publishes five-step playbook for managing Amazon Bedrock costs

The guide details how to use Amazon Bedrock's granular cost attribution features, which automatically link inference costs to IAM principals in the AWS Cost and Usage Report 2.0. It addresses the "shared-role problem" by recommending per-user session management to restore visibility behind LLM gateways. For observability, AWS suggests using invocation logs to CloudWatch or S3, combined with request metadata, to track workload-level spend. The article notes that while CUR data lags by roughly 24 hours, CloudWatch and OpenTelemetry can provide near-real-time dashboards.

Finally, the playbook presents three tiers for budget enforcement. Tier 1 uses AWS Budgets for alerts without blocking. Tier 2 employs IAM tag enforcement to deny access upon breach, though this is asynchronous. Tier 3 involves a synchronous gateway that blocks requests immediately via HTTP 429 responses, suitable for high-spend environments. AWS recommends choosing a tier based on connectivity and spend velocity, noting that direct Bedrock calls limit options to Tiers 1 and 2.