A US-headquartered global organization required Amazon Bedrock model inference for Claude Code to be processed in London (the eu-west-2 AWS Region), with prompts, completions, and intermediate processing staying inside a single AWS Region. The newest path, Anthropic’s Mantle endpoint on Amazon Bedrock, encountered a limitation. The classic Amazon Bedrock Invoke API with an application inference profile, plus an AWS Identity and Access Management (IAM) Region condition, satisfied the requirement. The post shows both paths, why the choice depends on your Region, the IAM policy that enforces them, and how to verify compliance in AWS CloudTrail. For most Amazon Bedrock workloads, cross-Region inference (CRIS) is the right default; use single-Region patterns only when compliance requires a specific AWS Region. Prerequisites include an AWS account with Amazon Bedrock model access for Claude models, IAM permissions (Path 1: bedrock-mantle:CreateInference, bedrock-mantle:Get*, bedrock-mantle:List*; Path 2: bedrock:CreateInferenceProfile, bedrock:InvokeModel, bedrock:InvokeModelWithResponseStream), both paths requiring iam:CreatePolicy, iam:AttachRolePolicy, iam:PutRolePolicy, Claude Code v2.1.94 or later, and AWS CLI configured for the target Region. Two endpoints exist: classic Amazon Bedrock (bedrock-runtime) uses the Invoke