Customer or accountant asks in writing for EU data residency
Most major clouds offer EU regions, but there is a gap between "data sits in the EU" and "EU staff and EU jurisdiction only". For most SMB customers the first is enough.
Try this first
- 1Pick the tenant or subscription region at creation in the EU (West Europe for Azure in NL, eu-central-1 Frankfurt or eu-west-1 Ireland for AWS, europe-west4 for GCP)
- 2Read the cloud DPA, which spells out how support staff outside the EU may access data
- 3Document for your processing register where the data sits and which sub-processors are involved
- 4Turn off diagnostic sharing outside the EU explicitly where that toggle exists
When to bring us in
For demands like SecNumCloud or "EU-only sovereign cloud", you are looking at OVHcloud, IONOS, or a specific Microsoft Cloud for Sovereignty offering, not the default region.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.