Bottom line: AWS shows two technical ways to operate Claude Code on Amazon Bedrock so that prompt and model processing verifiably never leaves a single AWS region – the classic Invoke API with an Application Inference Profile, or the newer Mantle endpoint with native region binding.
In a recent blog post, AWS describes how Claude Code on Amazon Bedrock can be configured so that model inference verifiably remains within a single AWS region – a scenario relevant to enterprises with strict compliance requirements. The trigger was a request from a globally operating, US-based company that needed inference to be mandatorily processed in London (eu-west-2), not merely invoked from there.
The customer’s specific compliance requirement was: prompts, completions and any intermediate processing must not leave a single AWS region – “approximate” compliance was not acceptable. AWS first tested Anthropic’s newer Mantle endpoint (bedrock-mantle), but ran into limitations regarding regional availability, and instead fell back on the classic Amazon Bedrock Invoke API. Combined with a so-called Application Inference Profile and an IAM region condition, the requirement could be met.
Technically, AWS distinguishes between two endpoints with different region logic. The classic Bedrock Runtime API (enabled via CLAUDE_CODE_USE_BEDROCK=1) routes by default through system-defined, cross-region inference profiles. To keep a request within one region, an Application Inference Profile must be created that explicitly points to the in-region foundation model. For this path, only eu-west-2 (London) currently supports in-region Claude, with the models Claude Opus 4.6 and Sonnet 4.6 (model IDs anthropic.claude-opus-4-6-v1 and anthropic.claude-sonnet-4-6). The newer Mantle endpoint (enabled via CLAUDE_CODE_USE_MANTLE=1, from Claude Code v2.1.94 onward) offers native single-region control solely via the AWS_REGION environment variable, but is available in more regions: Ireland, Stockholm, Tokyo, Melbourne, as well as US East (N. Virginia), US East (Ohio) and US West (Oregon), there with the models Claude Sonnet 5, Opus 4.8 and Haiku 4.5.
For CTOs with data residency obligations – for example due to customer contracts, industry regulation or national requirements as seen in parts of the DACH region – the post provides a solid reference pattern, including an IAM policy to enforce region binding and guidance on verification via AWS CloudTrail. AWS explicitly emphasizes that this single-region pattern should remain the exception: for most Bedrock workloads, Cross-Region Inference (CRIS) remains the more sensible default, since it smooths throughput, provides more capacity and enables earlier access to new models. If the requirement is merely “somewhere in the EU,” AWS recommends an EU cross-region profile instead of the more elaborate single-region solution.
Implementation prerequisites include enabled model access for the respective Claude models as well as IAM permissions, which vary depending on the path: for Mantle, these are bedrock-mantle:CreateInference along with Get* and List* permissions; for the classic path, bedrock:CreateInferenceProfile, bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream. In both cases, additional IAM permissions are required to create and attach the region-bound policy.
Source: aws.amazon.com · Published August 6, 2026
Lumi AI News — AI-assisted curation pursuant to Art. 50 EU AI Act. Paraphrasing and classification by Lumi News Pipeline v1.8.3.