Claude on Amazon Bedrock

Bedrock is partner-operated: AWS invoices you, AWS sets the quotas, and — the part that bites — AWS sets its own model retirement schedule.

The three differences that matter

1. Different model IDs. anthropic.claude-haiku-4-5-20251001-v1:0 rather than claude-haiku-4-5-20251001. See model IDs and versioning.

2. Different lifecycle. Anthropic’s deprecation dates apply to Anthropic-operated platforms. Bedrock publishes its own. The live example: Claude Opus 4.1 retired on the Claude API on 5 August 2026 and remains available on Bedrock. Running the same model on both means tracking two calendars.

3. Different pricing surface. Rates come from AWS. Regional endpoints carry a 10% premium over global endpoints for Claude Sonnet 4.5, Haiku 4.5, Opus 4.5 and everything after.

Endpoint types

From Claude Sonnet 4.5 onward, Bedrock offers two:

• Global — dynamic routing for maximum availability, standard price
• Regional — guaranteed routing through a specific geography, +10%

Choose regional only if you have a data-residency requirement that demands it.

Not the same as Claude Platform on AWS

This catches people. Claude Platform on AWS also runs on AWS and also bills through AWS Marketplace — but it is Anthropic-operated, uses Claude API-style model IDs, and follows Anthropic’s deprecation schedule. Two different products on the same cloud.

Also relevant for Claude Code

Claude Code can be pointed at Bedrock as its model backend, which is how many organisations run it under an existing AWS agreement.