Model Access and Region Strategy — Access, Regions, and IAM
Model Access and Region Strategy
Model Access Is Account + Region Scoped
Bedrock model availability is not universal across all AWS regions, and having an AWS account does not automatically entitle you to every model. Access is granted per account, per region, per model - and for Anthropic models a one-time use-case form may be required before access activates.
Enabling Model Access (One-Time Setup)
- Open the Bedrock console in your target region and go to Model access.
- Request the specific models you need (e.g. Amazon Nova Pro, Claude, Llama).
- Wait for the status to flip to Access granted - usually seconds to minutes.
- Verify from code:
aws bedrock list-foundation-models --region us-east-1.
Until access is granted, invocations fail with AccessDeniedException even if IAM is perfect - the two entitlement layers are independent.
Choosing Regions Deliberately
| Factor | Question to ask | Consequence of ignoring it |
|---|---|---|
| Model coverage | Is my required model family in this region? | Blocked feature launches, emergency region swaps |
| Data residency | Must prompts/completions stay in a jurisdiction (EU, UK)? | Compliance breaches, failed audits |
| Latency | Where are my users and my backend? | Slow token streaming, poor UX |
| Quota headroom | What are my tokens-per-minute and requests-per-minute limits here? | Throttling at peak traffic |
Cross-Region Inference Profiles & Model Lifecycle
Newer frontier models on Bedrock — including Anthropic Claude 5.x (claude-opus-5-5, claude-sonnet-5-5, claude-haiku-5-5, claude-fable-5-1), Amazon Nova Premier & Nova 2, Meta Llama 4 (Scout, Maverick), and DeepSeek-R1 — require invoking a Cross-Region Inference Profile ID rather than a bare foundation model ID for on-demand throughput (calling bare anthropic.claude-sonnet-5-5 raises ValidationException: Invocation of model ID ... with on-demand throughput isn't supported).
- Geographic prefixes (
us.,eu.,apac.) — route requests strictly within commercial regions in that geography (e.g.us.anthropic.claude-sonnet-5-5,eu.anthropic.claude-sonnet-5-5) to preserve regional data residency. - Global prefix (
global.) — routes dynamically across Bedrock's worldwide commercial capacity pool (e.g.global.anthropic.claude-opus-5-5) for maximum throughput resilience and roughly a 10% cost discount vs regional rates. - Model lifecycle hygiene (
Active → Legacy → Retired/EOL) — AWS never silently hot-swaps retired model IDs. Track deprecation notices (for example,Claude 3.5 Sonnetreached End-of-Life retirement and must be migrated to active successors likeus.anthropic.claude-sonnet-5-5) and keep{region, modelId}externalised in config.
{region, modelId} pairs per environment and alert when they diverge.Configure cross-region inference profiles to ensure multi-region failover and eliminate 429 ThrottlingExceptions.