Claude on Amazon Bedrock · EU data residency
Claude in Europe
runs on two lanes.
Pick one on purpose.
AWS offers two European ways to route a Claude request: keep it in one Region, or let AWS route it across EU Regions. The choice decides whether a prompt stays inside one Region, moves across EU Regions, or leaves the EU, and not every model supports both lanes. We help you pick per workload, configure it in your own AWS account and document it so it holds up in review.
Not sure where to start? Try the Claude Deployment Advisor.
The problem
Sound familiar?
Legal stalled the pilot
Procurement and counsel will not sign off on sending customer data through an architecture they cannot clearly explain, and the project has been sitting in review for months.
Teams are blocked
Your engineers know what Claude could unlock for the product. Policy says no. The gap between what you could ship and what you are allowed to ship keeps growing.
Vague residency promises
Every vendor deck says "EU-ready". Nobody shows you the processing scope, the routing decision, the IAM controls or the evidence trail. You need specifics, not adjectives.
The answer
Yes, Claude's prompts and responses can stay in the EU
Claude on Amazon Bedrock can keep prompts and responses processed within EU Regions. AWS operates the inference, and AWS states that model providers do not have access to Bedrock prompts and completions. Your residency footprint depends on how each request is routed.
In-Region
Processing stays in the single AWS Region you choose.
EU Geographic
Requests are processed only in EU Regions when you call from an EU Region.
Global
Requests can be processed in supported AWS Regions worldwide. Not a residency control.
The one-line test: if you need AWS-operated inference with AWS-enforced EU processing controls, use Claude on Amazon Bedrock, not Claude Platform on AWS.
Know which one you need
Residency is not sovereignty
The two get used as if they meant the same thing. They answer different questions, and Claude on Amazon Bedrock only answers the first one.
Data residency
Where is data stored and processed?
- Prompts and responses processed in EU Regions, by routing choice.
- Enforced with IAM and SCPs, evidenced with CloudTrail.
- This is what Claude on Amazon Bedrock in EU Regions gives you, and what we help you set up.
Sovereignty
Who operates it, and whose law applies?
- Operational control: who runs the infrastructure and who can access it.
- Legal control: which jurisdiction can compel access to the data.
- AWS is a US company, and Claude is not on the AWS European Sovereign Cloud today. EU Regions alone do not give you sovereignty.
If a workload truly needs sovereignty, the realistic options today are open-weight models on the AWS European Sovereign Cloud or self-hosting in the EU. Many teams run both: sovereign workloads there, Claude with EU residency for the rest. Read: Data residency vs sovereignty
Why configuration matters
Residency is a set of choices
Using Bedrock is not enough on its own. The model, the Region, the routing profile, the IAM policies, the network path, the logging setup and every surrounding service all need to be chosen deliberately. Get one wrong and data can end up outside the EU without anyone noticing. Get them right and the setup becomes a control you can show an auditor.
What Wolkn Minds does
From "is this allowed?" to "it is in production"
Residency & architecture assessment
We map your workloads, data classifications, security requirements and contractual obligations, then identify which deployment path fits each use case. Where a workload has a genuine sovereignty requirement, we say so and point to a different path.
Region & routing strategy
In-Region, EU Geographic or Global, chosen deliberately per workload, with the trade-offs documented so the decision survives the next audit.
Build & integration
Bedrock, IAM, Organizations controls, Guardrails, PrivateLink, logging, observability and cost controls, implemented in your AWS environment.
Governance pack
The documentation, policies and technical evidence your DPO, auditor and enterprise customers are likely to ask for.
Team enablement
Claude Code, SDKs and developer workflows configured around approved Bedrock patterns. Developers keep useful tools; the organisation keeps the residency footprint.
And what we do not do: we do not hold your prompts, we do not proxy your Bedrock model traffic, we do not sit between you and AWS, and we do not resell you access you already have. Inference runs directly between your workloads and AWS.
Honest limits
What we won't claim
- Not every Claude model supports EU routing, and support changes often.
- EU Geographic routing keeps processing in the EU only when called from an EU Region. Called from Zurich or London, it can process outside the EU.
- Global routing is never a residency answer.
- We design the technical controls. Your counsel and DPO make the legal call.
Technical resources
Go deeper
Book a consultation
Map your Claude residency footprint
Bring your real workloads. We will sort them by residency requirement and show you which architecture fits each one.
Prefer email?
hello@wolknminds.com
What a first call looks like
30 minutes, no slides. We ask about your data, your models, your AWS environment, your security requirements and the blockers stopping the project, then we tell you plainly whether we are the right people to help.
Based in
The Netherlands, working with teams across the EU.