Choosing an EU region, and how data residency works on Wow Magic
Where your objects physically live is a contractual question as much as a technical one. This article explains how regions work on Wow Magic, what a residency policy does, and how to make "EU only" something the platform enforces rather than something you remember.
By Wow Magic team · · 4 min read

"Keep the data in the EU" is one of the most common requirements we hear, from GDPR data-processing agreements, from public-sector procurement rules and from customers who simply prefer it. It is also one of the easiest requirements to break by accident: a new bucket created in the wrong dropdown, a script that defaults to another region, a colleague who did not know. This article explains the model Wow Magic uses so the requirement can be enforced, not just intended.
Regions: one choice per bucket
Every bucket on Wow Magic belongs to exactly one region, chosen when the bucket is created (in the console, or through the LocationConstraint in an S3 CreateBucket request). Objects written to that bucket are stored in that region's data centre and nowhere else. We do not replicate buckets across regions behind your back; if you want a copy elsewhere, you make one deliberately with a tool like rclone.
The live list of regions, with each one's city, country, jurisdiction zone and renewable energy source, is on the regions page and in the GET /platform/regions API. At the time of writing the available regions include Amsterdam (Netherlands) and Frankfurt (Germany) in the EU alongside US regions, with further locations listed as coming soon. The regions page is the source of truth; this article deliberately does not repeat the table because admins can add and retire regions without republishing it.
One endpoint serves every region. You do not need per-region hostnames; the bucket's region is looked up from its name, and the request is served by the right backend. The region you configure in SDKs is only a signing parameter (we advertise eu-central-1) and does not decide where data goes.
Jurisdiction zones
For residency purposes, countries are grouped into zones. Every EU and EEA member state collapses into a single EU zone; every other country is its own zone (US, GB, SG and so on). The zone of a region is derived from the ISO country code of its data centre, which is shown on the regions page.
This matters because "EU only" should mean any EU member state, not one particular city. A policy expressed in zones survives us opening a new region in, say, Ireland: it is automatically allowed, while a new London region is automatically excluded because the United Kingdom is its own zone.
Residency policies: the enforced version
A residency policy is an account-level rule that restricts which zones new buckets may be created in. When it is enabled, every CreateBucket request, whether from the console, the API or a CLI, is checked against the allowed zones, and a request for a region outside them is rejected with an error instead of quietly succeeding.
You set it yourself under Settings, Data residency in the console. The policy has:
- a list of allowed zones (for example just
EU); - an optional reason, recorded with the policy so that whoever looks at it later knows why it exists;
- a lock flag that only Wow Magic staff can set. A locked policy cannot be relaxed (disabled or widened) from the customer side, which is what organisations with contractual commitments usually want: the policy is part of the account setup, not a preference a new team member can toggle.
Regions whose country has not been classified are never offered to residency-restricted accounts, so a misconfigured or newly added region cannot become a loophole.
A residency policy applies to new buckets. It does not move existing buckets; if you already have data in a region the policy no longer allows, copy it to a compliant bucket and retire the old one.
What residency does and does not cover
It is worth being precise about the boundary:
- Object data and versions live only in the bucket's region. This includes noncurrent versions, delete markers and multipart parts.
- Account metadata, such as your bucket names, access keys, usage statistics, billing records and audit log, lives in the platform's control plane, which is separate from the storage regions.
- Downloads go where you download them to. If a user in another country fetches an object, the bytes leave the region; that is your application's data flow, not replication by us.
If your obligation is specifically about where the storage is, the region model plus a residency policy covers it. If it is broader (for example, processor location clauses in a DPA), read our Data Processing Addendum and talk to us through the contact page.
Practical checklist
- Decide the allowed zones with whoever owns your compliance obligations.
- Create the buckets in a region inside those zones; check the zone column on the regions page.
- Enable a residency policy with exactly those zones and write a one-line reason.
- If the requirement is contractual, ask us to lock the policy.
- In CI scripts and SDK code, set the region explicitly when creating buckets rather than relying on defaults, so the error, if there is one, surfaces at the right moment.
That is the whole model: regions decide where bytes live, zones make "EU" mean the EU, and policies turn the requirement into something the platform refuses to violate.


