AWS Details Two Paths for Single-Region Claude Code Deployments on Amazon Bedrock

AWS has published guidance for enforcing strict data-residency requirements when running Claude Code on Amazon Bedrock, addressing a gap that arises when compliance teams demand inference stay within a single named AWS Region rather than a broader geography.

The post stems from a real customer request: a US-headquartered global organization needed Bedrock model inference for Claude Code processed specifically in London (eu-west-2), not merely invoked from London. AWS engineers found that Anthropic's newer Mantle endpoint on Bedrock could not satisfy this requirement for that Region, so they fell back to the classic Bedrock Invoke API combined with an application inference profile and an IAM Region condition.

Two endpoints, two mechanisms

Bedrock exposes Claude through two distinct endpoints, each with different Regional coverage:

• Classic Bedrock (bedrock-runtime): Activated via CLAUDE_CODE_USE_BEDROCK=1. Single-Region routing requires creating an application inference profile pointed at an in-Region foundation model, since system-defined profiles default to cross-Region routing. Per AWS, eu-west-2 (London) currently supports only Claude Opus 4.6 and Sonnet 4.6 for in-Region inference on this path, using model IDs anthropic.claude-opus-4-6-v1 and anthropic.claude-sonnet-4-6.

• Mantle (bedrock-mantle): Activated via CLAUDE_CODE_USE_MANTLE=1. This is Anthropic's native API shape served through Bedrock, requiring only that AWS_REGION be set — no inference profile needed. Mantle supports native in-Region routing in seven Regions: Ireland, Stockholm, Tokyo, Melbourne, US East (N. Virginia), US East (Ohio), and US West (Oregon), with access to newer models including Claude Sonnet 5, Opus 4.8, and Haiku 4.5.

Critically, Mantle has no in-Region-only option for eu-west-2 — only Global and EU-wide endpoints, meaning a London request could be processed in Frankfurt, Ireland, or Paris. For customers requiring London specifically, that disqualifies Mantle entirely, leaving classic Bedrock with an application inference profile as the only compliant route.

AWS requires Claude Code v2.1.94 or later for Mantle support. Both paths use IAM Region conditions (aws:RequestedRegion) attached to the developer's IAM role or user to reject any call not targeting the approved Region, even if environment variables are misconfigured. AWS recommends verifying compliance through CloudTrail logs.

AWS also notes an important caveat: for most Bedrock workloads, cross-Region inference (CRIS) remains the recommended default, since it improves throughput, capacity, and access to new models. The single-Region patterns described apply only when compliance mandates a specific Region rather than a general geography — AWS suggests EU cross-Region profiles suffice when "somewhere in the EU" is an acceptable boundary.

What this means

This is an operational fix for enterprise compliance, not a new model or pricing change. It signals that data-residency enforcement on Bedrock is still uneven across Regions and endpoints — Mantle, Anthropic's newer native-API path, currently cannot guarantee in-Region-only processing in London, forcing reliance on the older Invoke API and manually configured inference profiles. Enterprises with strict per-Region requirements (finance, healthcare, government contractors) need to audit which endpoint and Region combination actually satisfies their obligations before deploying Claude Code, since the two paths differ in available models, IAM permissions, and enforcement mechanics. AWS's explicit advice to escalate to account teams for unsupported Regions suggests this remains a manual, case-by-case problem rather than a fully generalized platform capability.