Does Claude actually run in the UK? Every Bedrock route, tested

If you want Claude to run in the UK and nowhere else, the question is narrower than "is Claude available in London?" It is: which specific model ids can be invoked in-region against bedrock-runtime.eu-west-2, today, with a real request?

We could not find a source that answered that reliably. AWS documentation, Anthropic documentation and third-party summaries disagreed with each other, and some were out of date. So we stopped reading and started measuring.

The short answer

As of 3 August 2026, two Claude models can be invoked in-region in AWS Europe (London): Claude Sonnet 4.6 and Claude Opus 4.6, using their bare model ids. Models published only as an eu. cross-region inference profile cannot be pinned to London, because pinning to one region is not what a cross-region profile does.

Why "available in London" is the wrong question

Bedrock gives you two quite different things that both look like a region.

A bare model id — anthropic.claude-sonnet-4-6 — is an in-region invocation. You address the London endpoint and London serves it. The request does not go anywhere else.

A cross-region inference profile — eu.anthropic.claude-sonnet-4-6 — is a routing construct. The eu. prefix means AWS may serve the request from any region in that geography. For the EU profile, AWS documents that as Dublin, London, Paris, Frankfurt, Stockholm, Milan and Madrid. You are addressing London, but London is one of seven possible answers.

There is also a global profile, which may be served anywhere AWS operates. AWS states plainly that with global routing your input prompts and output results may be stored in opt-in regions for abuse detection. That includes the United States.

This distinction is the whole ball game. A page saying "Claude is available in eu-west-2" is not wrong, exactly — but if you read it as "my data stays in London" while calling an eu. profile, your data does not stay in London.

How we tested

We run a command against our own production catalogue that makes a genuine one-token inference call on every configured route and records what came back.

Not a ListFoundationModels call. Listing a model proves only that it appears in a catalogue, not that your credentials can invoke it. We learned that the hard way: an earlier version of this check reported every route healthy while five of them were being refused at invoke time. If your own verification only lists models, it is telling you nothing about what will happen in production.

Each route is called with its exact model id against bedrock-runtime.eu-west-2, with max_tokens of one, so the test costs almost nothing and can be run often.

Results, 3 August 2026

The practical consequence is worth stating bluntly, because it is the part people find disappointing: the newest Claude models are not available as an in-region London invocation. If you need Opus 5 or Sonnet 5, you are accepting EEA-wide routing at best. If you need the processing to stay in the UK, you are choosing between Sonnet 4.6 and Opus 4.6.

Anyone offering you Opus 5 with a UK-only guarantee on Bedrock today is either using a different mechanism entirely or has not checked.

What this means if you are building on it

Pin the model id explicitly. If your code says "the latest Sonnet", you have handed the routing decision to whatever your SDK resolves that to next month. A residency guarantee that depends on a floating alias is not a guarantee.

Decide what happens when the route is unavailable. This is the part most implementations get wrong. If London cannot serve the request, the tempting behaviour is to fall back to the EU profile so the user still gets an answer. That converts a visible outage into an invisible compliance breach. Our resolver walks permitted scopes best-first and throws if none are permitted, so a UK-tier request that cannot be served in London fails closed and returns an error. An error you can explain to a client beats a silent transfer you cannot.

Re-test on a schedule. Model catalogues change, IAM policies change, and inference profiles are added and retired. Every claim on this page is a fact about a live system on a given date, which is why the date is at the top.

Checking your own account

You do not need us for this. Make a real request with a one-token limit against bedrock-runtime.eu-west-2 using the bare model id, and see whether it returns or raises AccessDeniedException.

Do it with the credentials your application actually uses, not an administrator profile. The common failure is an IAM policy that grants the bare model ARNs but not the inference profile ARNs, or the reverse — and an admin session hides that completely.

If it succeeds with a bare model id, that inference happened in London.

Where we come into it

We run this gateway commercially: you call an Anthropic-compatible endpoint, we invoke Claude in-region in London, pseudonymise personal data on the way through, and give you a per-request record of where it ran.

But the honest position is the one at the top of this page. If you have a platform engineer, Bedrock in London is self-serve and you can wire this up yourself in an afternoon. What you would be buying from us is the part after the endpoint: the redaction layer, per-client metering, GBP invoicing, and an attestation naming your sites that you can forward to a client who asked where their data goes.

If none of that is worth paying for in your situation, use Bedrock directly. We would rather you did that than bought something on a claim that did not survive contact with your own testing.

dijitul Ltd is not a law firm and this is not legal advice.

This is general information about how the rules work, not legal advice about your circumstances. If a decision turns on it, take advice.