> ## Content Index
> Fetch the complete content index at: https://insights.cloudacio.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Your Bedrock bill doesn't say Bedrock
- URL: https://insights.cloudacio.com/your-bedrock-bill-doesnt-say-bedrock/
- Published: 2026-07-28T13:00:00.000Z
- Updated: 2026-08-12T18:34:04.000Z
- Description: If you open Cost Explorer, filter on "Amazon Bedrock" and see a number that looks reassuringly small, you are almost certainly not looking at what you spend on Bedrock.
- Author: Juan Pablo Olivera
- Tags: Artificial Intelligence, Guide

If you open Cost Explorer, filter on "Amazon Bedrock" and see a number that looks reassuringly small, you are almost certainly not looking at what you spend on Bedrock.

## Where the money actually is

Bedrock bills inference under per-model service names. A Claude Sonnet workload does not appear under "Amazon Bedrock" at all — it appears under its own line item:

```
Claude Sonnet 5 (Amazon Bedrock Edition)
Claude Opus 5 (Amazon Bedrock Edition)

```

The "Amazon Bedrock" service line covers the surrounding machinery — knowledge bases, guardrails, provisioned throughput — and on a typical inference-heavy account that is a rounding error next to the model lines themselves.

The gap is not small. On an account we looked at recently, the difference between the two readings was roughly three orders of magnitude.

## What to do instead

Group by **Service** rather than filtering by it, and read the per-model lines. If you want a single number, build a Cost Category that rolls the model services and Bedrock together, and use that everywhere — dashboards, budgets, alerts.

The failure mode worth avoiding is the one where a budget alarm is scoped to "Amazon Bedrock" and never fires, because the thing it watches was never where the spend was.