AWS is unplugging its EU cloud from the US — what it proves, and what it doesn't
On 24 October, AWS plans to cut its European Sovereign Cloud off from its global network and run it in isolation. It is a deliberate demonstration of resilience — but the question that matters most for Swedish healthcare and the public sector isn't whether the cloud keeps running with the transatlantic cord pulled. It's who can legally compel access to the data while it does.
What is happening
The European Sovereign Cloud runs from a region in Brandenburg, Germany, operated by staff resident in the EU. The test isolates it from AWS's global network and asks a straightforward question: can it keep serving on its own? Isolating a hyperscale region — identity, networking, operations — and keeping it alive is genuinely hard engineering, and worth proving.
What the test proves — and what it doesn't
What it proves is technical: the platform can operate without a live connection to the US. What it leaves open is legal. Sovereignty is ultimately a question of jurisdiction, not cabling. As long as the operator is a US-headquartered company, US law — the CLOUD Act chief among it — can reach for data regardless of where the servers sit or who is on shift that day. A disconnection test doesn't change which laws apply to the operator.
Some of the hardest questions also sit in the plumbing. Where do identity and access management ultimately resolve? Where does DNS? If the roots of trust or name resolution still trace back across the Atlantic, "disconnected" is carrying a lot of weight. A clean demo doesn't settle that — the architecture does.
Our view: sovereignty is measured in whether you can leave
We've long argued that the real test of sovereignty isn't where your data sits today — it's whether you could move it tomorrow. If leaving a provider means a multi-year rebuild, you are not sovereign; you are dependent, with a European postcode.
That is why we design for portability first: open standards, Kubernetes and infrastructure-as-code that run on more than one provider, data in formats you own, and a written exit plan you could actually execute. Sweden's new cloud policy points the same way — towards exit strategies and open standards rather than trust in any single vendor's goodwill.
A disconnection test makes a good headline. A credible exit plan is what keeps your options open when the headline changes.
Want to know how portable your platform really is?
Talk to us. We'll walk your architecture and tell you honestly how long it would take to leave a provider — and what to change so the answer is "weeks, not years".