A US-headquartered global organization recently approached AWS with a data-residency requirement: their engineers needed to use Claude Code, with all processing occurring within the London AWS Region, eu-west-2. Compliance dictated that prompts, completions, and intermediate processing must remain within a single AWS Region. AWS explored two paths: first, the newer Mantle endpoint, but encountered limitations, then reverted to the classic Amazon Bedrock Invoke API with an application inference profile. This combination, paired with an IAM Region condition, met the compliance requirement. The post outlines both approaches, their regional availability, and how to enforce compliance using IAM policies and AWS CloudTrail.
The two paths for single-Region Claude Code execution depend on the endpoint used. Classic Amazon Bedrock requires an inference profile to keep requests within a single Region, while the Mantle endpoint allows direct single-Region routing by setting the AWS_REGION environment variable. Model availability and regional support differ between the two endpoints, with Mantle offering newer models in specific regions like Ireland, Stockholm, Tokyo, and others. For regions not supported by Mantle, the classic Amazon Bedrock approach is necessary. Developers must configure environment variables and IAM policies to ensure compliance with regional constraints.
The post emphasizes that cross-Region inference (CRIS) is the default for most Amazon Bedrock workloads, as it improves throughput and model access. Single-Region patterns should only be used when a specific AWS Region is required for compliance. For example, in London (eu-west-2), the classic Amazon Bedrock approach is needed since Mantle does not support in-Region routing there. The solution involves setting up IAM policies and environment variables to restrict model calls to the target Region.
Source: awsml
