Amazon Bedrock pricing in 2026: every model, hidden costs, and why your bill is higher than the pricing page suggests

The AWS Bedrock pricing page shows clean numbers. $3 per million input tokens for Claude Sonnet 4.6. $0.035 for Amazon Nova Micro. Multiply volume by rate, and you have an estimate. The estimate rarely matches the invoice. Across $14 billion in cloud and AI spend under management, CloudZero consistently sees organizations spending 1.5x to 2x their initial Amazon Bedrock cost estimates.

A team that budgets $50,000 annually ends up at $85,000. A team that budgets $200,000 ends up at $340,000. The overruns are not hidden fees. They are costs the pricing page does not surface until they appear on the invoice: OpenSearch Serverless minimums for Knowledge Bases, embedding model inference for retrieval, Guardrails per-assessment charges, and the token amplification that happens when a Bedrock Agent chains multiple model calls to answer a single query.

And this isn’t theoretical. A recent r/aws thread titled “AWS Bedrock cost spike 14000 USD!” is one of the most-read pages on this exact topic right now, and the pattern it describes (spend discovered at invoice time, cause unknown, panic ensuing) is the default Bedrock experience for teams monitoring costs monthly. The costs below don’t announce themselves; they compound quietly until someone opens Cost Explorer.

This guide covers every Bedrock pricing tier, every model’s per-token rate, the costs that appear on the bill but not on the pricing page, how Bedrock compares to calling model providers directly, and the tactics that close the gap between the estimate and the invoice. For how Bedrock costs connect to broader AI spend, see CloudZero’s AI ROI framework.

What is Amazon Bedrock?

Amazon Bedrock is a fully managed AWS service that provides API access to foundation models from Anthropic, Meta, Mistral, Cohere, AI21, Stability AI, and Amazon’s own Nova family through a single AWS endpoint. You call a model, you pay per token, and AWS handles hosting, scaling, and regional availability. “AWS Bedrock” and “Amazon Bedrock” name the same service; Amazon Bedrock is the official one.

Plainer version: it’s the app store model for AI. AWS runs the store, hosts every model, and puts it all on the bill you already have. Convenient, genuinely. The convenience just has more meters than the storefront suggests.

As of 2026, Amazon Bedrock carries what AWS describes as hundreds of foundation models from 18 providers, available across 33 commercial AWS regions. The catalog covers every major family: Claude (Anthropic), Llama (Meta), Mistral, Nova (Amazon), and Cohere Command.

Amazon Bedrock features include on-demand and batch inference, Agents for multi-step orchestration, Knowledge Bases for retrieval-augmented generation, Guardrails for content safety, model evaluation and fine-tuning, and cross-region inference. For how the components fit together, see the AWS documentation.

Bedrock’s pitch is one API, one billing relationship, and access to every major model family. That single relationship runs five metered modes on the pricing page and at least four more meters off it: Knowledge Bases, Guardrails, Data Automation, and agent amplification. Most teams budget the first one and meet the rest during a monthly bill review rather than at architectural planning.

For the wider context, see CloudZero’s guides on what cloud computing is and how AWS Bedrock fits among the major cloud service providers.

What are Amazon Bedrock’s 5 billing modes?

1. On-demand pricing (pay per token, no commitment)

The default and most common mode. You pay per input and output token with no commitment.

Here is the table for the most-used models (us-east-1):

Note: Claude Sonnet 5 ($2/$10) is the newer, cheaper Sonnet. Its $2/$10 introductory rate became permanent on September 1, 2026; the increase to $3/$15 that Anthropic had scheduled for that date was cancelled. Sonnet 4.6 remains $3/$15.

The 285x spread between Nova Micro ($0.035 input) and Claude Fable 5 ($10 input) is the most important number in the table, and it widens to 428x if you count the legacy Opus 4.1 that AWS still serves at $15 input. That spread defines the Bedrock cost per token range your team operates in, and it makes model routing (cheap models for simple tasks, expensive ones for hard tasks) the single highest-impact cost lever on the platform. More below.

For AWS Bedrock pricing on Anthropic Claude models across the full family, see CloudZero’s Claude pricing guide. And for a quick Bedrock pricing calculator approach: multiply expected monthly token volume by the per-token rate, then add 50-100% for the hidden costs covered below. Yes, really. The second half of that formula is this article’s whole reason to exist.

2. Batch pricing (50% off, async processing)

Batch processes prompts asynchronously at half the on-demand rate: Claude Sonnet 4.6 drops to half its list price, Nova Pro falls from $0.80/$3.20 to $0.40/$1.60. For anything that doesn’t need real-time responses (data extraction, document analysis, bulk classification), batch is the simplest discount on the menu.

3. Bedrock provisioned throughput (pay per hour, guaranteed capacity)

Reserved capacity billed per hour, not per token. Bedrock provisioned throughput pricing fits high-volume, consistent workloads that need guaranteed latency, with 1-month and 6-month commitments (longer is cheaper). You pay for the capacity whether you use it or not, which is either waste or peace of mind depending on your traffic curve. Below the break-even point, which runs roughly 5 to 20 million requests a month depending on the model and commitment length, on-demand usually wins.

On the Amazon Bedrock free tier question: there isn’t a permanent one. New AWS accounts created after July 15, 2025, get up to $200 in credits: $100 on sign-up and $100 for five guided activities, one of which is a Bedrock prompt. The free account plan expires after 6 months or when the credits run out, whichever comes first. Upgrade to a paid plan and unused credits stay usable for up to 12 months from sign-up.

4. Prompt caching (up to 90% off input tokens)

Bedrock supports prompt caching for select models (Claude and Nova families), with cached input tokens at roughly 10% of base rate. For long, repeating system prompts (agentic workflows, Claude Code sessions, RAG pipelines), caching is the second-biggest lever after routing. CloudZero’s Claude Code plugin tracks caching effectiveness in real time.

5. Fine-tuning (per-token training + storage)

Custom training bills per training token plus per-hour training time, and fine-tuned model storage adds monthly charges. Real, but niche next to on-demand and batch.

Those five modes are what the pricing page shows.

What costs does the Amazon Bedrock pricing page not show?

1. Knowledge Bases: the $345/month minimum

Amazon Bedrock Knowledge Bases connect your data to models for RAG, and the default vector store, OpenSearch Serverless, requires a minimum of 2 OpenSearch Compute Units at $0.24/OCU/hour. That is about $350 a month at zero query traffic (2 x $0.24 x 730 hours). Two escape hatches are worth knowing: a dev-test collection halves it, and NextGen collections drop the minimum entirely and scale to zero after 10 minutes idle. On a Classic production collection, the meter is always running.

The 2026 alternative: Amazon S3 Vectors, generally available since December 2025, cuts vector storage costs by up to 90% versus specialized vector databases. For new Knowledge Bases, S3 Vectors should be the default unless you have a hard OpenSearch dependency. Amazon Bedrock Knowledge Bases pricing also includes embedding inference (input tokens only) and Bedrock Data Automation for document parsing at $0.010 per page.

2. Amazon Bedrock Agents: token amplification

AWS Bedrock Agents chain model calls to complete multi-step tasks: one user query can trigger 3-5 invocations as the agent reasons, retrieves, and responds, and each invocation bills separately. If the base model costs $2/$10 per MTok and the agent averages 4 calls per query, the real cost per query is 4x the pricing-page number.

The $14,000 Reddit spike is this: agent amplification plus always-on Knowledge Base minimums, with nobody touching the architecture. Gartner forecasts supply chain software with agentic AI alone growing to $53 billion by 2030; agent amplification is the cost pattern finance teams haven’t budgeted yet. For the pattern in depth, see CloudZero’s agentic AI spend guide.

3. Amazon Bedrock Guardrails: per-assessment charges

AWS Bedrock Guardrails (content filtering, PII detection, prompt injection prevention) bill per 1,000 text units, per policy type: roughly $0.15 per 1,000 for content filters and denied topics, $0.10 per 1,000 for PII and contextual grounding checks. Word filters and regex-based PII rules are free. Stack three or four policy types on every request at volume and the guardrail line can exceed the inference line.

4. Cross-region inference: no surcharge, but regional pricing applies

Cross-region inference carries no routing fee: the price is set by the Region you call from. The lever is which cross-region profile you pick. AWS puts Global cross-region inference at roughly 10% below Geographic cross-region inference, which pins your traffic to one geography. Route globally and pocket the 10%. Pin a geography for compliance reasons, never out of habit.

Amazon Bedrock vs. direct API pricing: is the AWS markup worth it?

Per-token rates match. The difference lives in the adjacent services (Knowledge Bases, Agents, Guardrails) and the operational overhead, which direct Anthropic or OpenAI API calls don’t carry. The tradeoff: Bedrock buys unified billing, VPC integration, IAM controls, and marketplace procurement; direct APIs buy lower operational cost and more billing relationships to manage.

One more layer to the decision, because most enterprises don’t actually choose. The standard 2026 stack runs Bedrock for AWS-native workloads, the OpenAI API or Azure OpenAI for others, and often direct Anthropic calls beside them: three invoices, three formats, one AI strategy, and a board asking for the ROI of the total. Bedrock’s unified billing unifies exactly one of those three invoices, which is why “we use Bedrock for consolidation” is true right up until it isn’t.

For teams running Claude on AWS specifically, CloudZero’s guide compares Bedrock, Claude Platform on AWS, and direct API side by side. For how ChatGPT and OpenAI API pricing stack against Bedrock rates, see the LLM API pricing comparison, and for the Microsoft flavor of the same decision, the Azure OpenAI pricing guide.

AWS Bedrock vs. SageMaker: when should you use which?

The AWS decision guide recommends Bedrock for teams using existing foundation models without managing infrastructure, and SageMaker for custom training with fine-grained control. AWS Bedrock vs. SageMaker isn’t either/or; most enterprise teams run both, Bedrock for prototyping and multi-model access, SageMaker for production pipelines.

How do you reduce AWS Bedrock costs? 7 ways

CloudZero’s Dimensions map every token to the workload that consumed it, and anomaly detection with hour-level data catches agent amplification spikes and runaway Knowledge Base costs while they’re a Tuesday problem instead of a month-end discovery. That’s the exact failure mode in that r/aws thread.

The AI Hub tracks Bedrock alongside Google Vertex AI, GPU clusters, OpenAI, Azure, and 30+ providers in one view, which is what turns “Bedrock cost us $47,000 this month” into “the AI search feature costs $0.003 per enterprise query, and here’s its margin.”

Pete Rubio, SVP of Platform and Engineering at Rapid7, describes managing fast-growing AI costs with CloudZero as “enabling innovation while maintaining financial accountability and control,” which is the Bedrock assignment in one sentence.

Schedule a demo and ask to see Bedrock spend broken down by model, team, feature, and customer, get a free cloud cost assessment to find your own estimate-to-invoice gap, or take the self-guided tour. More stories on the customers page.

Frequently asked questions about Amazon Bedrock pricing

Author Spotlight

Lyne Carolyne

Lyne Carolyne has several years of experience in AI and cloud economics and brings that understanding into the content she creates. Outside work, she's an avid explorer.