AMAZON BEDROCK / PART V, MULTI-AGENT AND ARCHITECTURE
MULTI-REGION AND DISTRIBUTION
CHAPTER 36 / 36
IN ONE LINE serve many countries, lawfully and fast
REV 2026.07
If your company operates across many countries, two forces shape your agent's deployment: latency (users want a nearby Region) and the law (an EU citizen's data must stay in the EU, and similar rules elsewhere). AgentCore is a regional service, so you distribute it: deploy in each geography, route users to theirs, and use cross-region inference to keep model processing inside the right borders.
New to these words? Read chapter 02. Related: Runtime (chapter 07), Governance at scale (chapter 34), Multi-tenant (chapter 32).
[ 1 ] WHAT TO KNOW FIRST
AgentCore runs in an AWS Region, spread across that Region's Availability Zones for resilience. A Region is independent: your agents, memory, and data live there. To serve the world, you deploy in several Regions and send each user to the closest, or legally required, one.
DRIVEN BY LATENCY
Users want a Region near them for fast responses.
DRIVEN BY LAW
Data-residency rules require processing and storage in a specific geography.
[ 2 ] WHERE IT RUNS, 20 REGIONS
AMERICAS
N. Virginia, Ohio, Oregon, Canada (Central), Sao Paulo, GovCloud (US-West)
EUROPE
Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm
ASIA PACIFIC
Mumbai, Malaysia, Singapore, Sydney, Thailand, Tokyo, Seoul
CHECK BEFORE YOU PICK
Core services are in nearly all Regions. Newer ones (Payments, Registry, Optimization) and GovCloud cover fewer. Read the Regions table first.
[ 3 ] KEEP MODEL PROCESSING IN THE RIGHT PLACE (CROSS-REGION INFERENCE)
GEOGRAPHIC for residency
Bedrock picks the best Region within one geography (US, EU, APAC, ...).
Requests stay inside that geography, where the data lives.
Use when you have data-residency rules. Profile id like eu.anthropic.claude-sonnet-4-6.
GLOBAL for throughput and cost
Routes to the best Region anywhere in the world.
Higher throughput, and cheaper (about 10% on tokens).
Use when you have no residency limit. Profile id like global.anthropic.claude-sonnet-4-6.
Either way, cross-region inference stores your data only in the source Region by default (prompts and results move through the destination Region during inference; if AWS stores data for abuse detection, that is stored in the destination Region). Traffic stays on the AWS network, never the public internet.
[ 4 ] DESIGN FOR LATENCY AND FAILURE
WITHIN A REGION automatic
AgentCore already spreads across Availability Zones and fails over between them without interruption. You get this for free.
ACROSS REGIONS your design
Deploy the stack in each geography; route users by latency or country (for example with Route 53); keep a failover Region ready. Each Region is independent, so replicate config and, where the law allows, data.