Where does Bedrock actually process your data?

A model listed as available in your region is not the same thing as a model that runs in your region. When it is reachable only through a cross-region inference profile, Bedrock serves the request from wherever that profile has capacity — the call succeeds, nothing in the console looks unusual, and the prompt was processed in another country.

This page separates the two. Every model, every jurisdiction, derived from the routes AWS itself declares.

For the reasoning rather than the table: Your Bedrock data residency is probably not what you think →

120/120

models stay in the United States

66/82

stay in the European Union

7/42

stay in France

The finding

Country-level residency on Bedrock is, in practice, a United States feature. All 120 models available in the US are callable without leaving it, because the us. profile only ever routes to US regions. The eu. profile is bounded to the Union but spans 6 member states, so it satisfies an EU constraint and breaks a national one. And in Israel, Malaysia, Taiwan, Thailand, Mexico, New Zealand, South Africa, not a single model available in-country actually stays there.

What each inference profile scope declares

The prefix on a profile ID is the whole residency story. us., au., jp., in., ca. never leave one country. The others cross borders by design.

Scope	Models	Processed in	Bounded to
us.	59	United States	one country
global.	31	not published	nothing — no closed destination list
eu.	21	France, Germany, Ireland, Italy, Spain, Sweden	6 countries
au.	11	Australia	one country
apac.	10	Australia, India, Indonesia, Japan, Singapore, South Korea, Taiwan	7 countries
jp.	8	Japan	one country
in.	6	India	one country
ca.	1	Canada	one country

Destinations are the regions each profile declares through the Bedrock ListInferenceProfiles API. The global. scope is reported as unbounded rather than narrowed to what it declares: AWS documents global routing as worldwide, so the declared list cannot be a complete one.

Every jurisdiction with a Bedrock region

Sorted by the gap that matters: how many models the matrix shows as available and this page cannot certify as staying put.

Jurisdiction	Available	Stays put	Leaves or unverifiable	Regions
Ireland	70	34	36	eu-west-1
France	42	7	35	eu-west-3
Germany	52	17	35	eu-central-1
Singapore	40	5	35	ap-southeast-1
Italy	62	28	34	eu-south-1
South Korea	41	7	34	ap-northeast-2
Spain	35	1	34	eu-south-2
Sweden	54	20	34	eu-north-1
Israel	33	0	33	il-central-1
Malaysia	33	0	33	ap-southeast-5
Taiwan	33	0	33	ap-east-2
Thailand	33	0	33	ap-southeast-7
Indonesia	50	18	32	ap-southeast-3
Canada	45	14	31	ca-central-1 ca-west-1
India	83	52	31	ap-south-1 ap-south-2
Brazil	71	41	30	sa-east-1
Switzerland	32	2	30	eu-central-2
Japan	81	53	28	ap-northeast-1 ap-northeast-3
United Kingdom	79	52	27	eu-west-2
Mexico	25	0	25	mx-central-1
New Zealand	25	0	25	ap-southeast-6
South Africa	25	0	25	af-south-1
Australia	81	57	24	ap-southeast-2 ap-southeast-4
the European Union bloc	82	66	16	eu-central-1 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-3
United States	120	120	0	us-east-1 us-east-2 us-west-1 us-west-2

"Stays put" counts models callable on-demand inside the jurisdiction, plus models whose only route is a profile that declares no destination outside it. Methodology.

Three things that catch people

An `eu-` region code is not a jurisdiction

EU (London) is in United Kingdom and Europe (Zurich) is in Switzerland. Neither is an EU member state. Both countries hold an adequacy decision, which makes a transfer lawful — a different claim from the data never leaving the Union.

Availability is not residency

The matrix cell for a profile-only model is legitimately "available": the API call works. What it cannot show is that the work happens somewhere else. That is the entire gap this page measures, and it is the reason the two surfaces disagree on purpose.

The compliant route is one argument away from the wrong one

A model can be callable in-region by its bare ID and also carry a global. profile. Both are one string in the same SDK parameter. The per-jurisdiction pages name the exact ID that keeps the guarantee, and flag the models where a second, leakier route exists alongside it.

Questions

Does Amazon Bedrock keep my data in the region I call?

Only when you invoke the bare model ID and the model is available on-demand in that region. If the model is reachable only through a cross-region inference profile, Bedrock routes the request to whichever region in that profile's scope has capacity, and the inference runs there. The call looks identical from your side either way, which is why this page separates the two cases.

Is the eu. inference profile enough for EU data residency?

Yes for the Union, no for a single country. The eu. profile declares destinations in 6 member states — France, Germany, Ireland, Italy, Spain, Sweden — so a request issued in Paris can be processed in Ireland or Spain. That satisfies "data stays in the EU" and contradicts "data stays in France".

Are eu-west-2 and eu-central-2 in the European Union?

No. eu-west-2 is London and eu-central-2 is Zurich. The eu- prefix is an AWS region-naming convention with no jurisdictional meaning; the United Kingdom left the Union in 2020 and Switzerland was never a member. Both hold a European Commission adequacy decision, which makes a transfer lawful without making the data resident in the Union.

What about the global. inference profile?

AWS does not publish a closed destination list for global profiles, so no residency claim can be verified about them in either direction. This site reports them as "destination not bounded" rather than inferring a region set from the API response, because the API names fewer regions than the documentation describes.

Where does this data come from?

Region availability and the destinations each inference profile declares come from the AWS Bedrock APIs, rebuilt daily. The mapping from AWS region to country is maintained by hand and changes only when AWS opens a region. This is a description of where inference executes, not legal advice.