Cross-region inference on Bedrock
Bedrock's geographic cross-Region inference profiles carry a geographic prefix -- us., eu., apac., jp. -- prepended to the base model ID. Calling us.anthropic.claude-3-haiku-20240307-v1:0 from US East (Ohio) can route the request to us-east-1, us-east-2, or us-west-2; the same call made from US West (Oregon) routes only to us-east-1 and us-west-2. This keeps data processing within a chosen geography while giving Bedrock more regional capacity to route around to improve throughput and availability.
Global vs. regional (CRIS) endpoints
Starting with Claude Sonnet 4.5 and all later models, Bedrock exposes two endpoint types per model: a global endpoint (model ID already carries the global. prefix, e.g. global.anthropic.claude-opus-4-6-v1) that dynamically routes to whichever region has capacity, with no pricing premium -- and a regional/CRIS endpoint, reached by simply removing the global. prefix, that guarantees routing stays within a chosen geography (US, EU, Japan, or Australia) for data-residency/compliance needs, at a 10% pricing premium over the global rate. Older model generations (Sonnet 4 and earlier, Opus 4 and earlier) keep their pre-existing pricing structure and don't carry this global/regional split.
Sources: docs.aws.amazon.com/bedrock/.../inference-profiles-support; platform.claude.com/docs/en/build-with-claude/claude-on-amazon-bedrock. See the full cross-region inference rows.