AWS Will Unplug Its European Cloud for a Few Hours. An Independent Tracker Scored the Test 'Weight 0.'

On October 24, AWS will disconnect its European Sovereign Cloud from the company’s global network backbone for several hours, rerouting traffic through dedicated EU internet service providers instead. It’s a real, verifiable technical exercise, not a marketing claim dressed up as one. It’s also, by AWS’s own admission, a demonstration of exactly one layer of what “cloud sovereignty” actually means — and an independent tracker scoring sovereignty claims gave the exercise a flat zero on the question that matters most to regulators: who actually owns and controls the infrastructure.

What the test actually does

The European Sovereign Cloud (ESC) normally runs connected to AWS’s global network backbone because it delivers better performance, capacity, and cost than operating in isolation. On October 24, AWS will switch that off: traffic reroutes exclusively through European ISP connectivity, and a separate global channel used for limited operational data transfers — including vetted source-code mirroring and software updates — gets disabled too, not just the main backbone.

Three things AWS is explicit the test does not do: it doesn’t disconnect from the internet entirely, it doesn’t affect service availability in the ESC or any other AWS region, and it doesn’t change who owns the infrastructure. The operations team running the exercise consists entirely of EU residents working within the EU — a real staffing commitment, not just a network configuration detail.

What this does and doesn’t prove

AWS states this plainly in its own materials: the exercise addresses operational independence specifically — can the European Sovereign Cloud function without relying on non-EU infrastructure — and explicitly does not address the broader questions the European Commission’s proposed Cloud and AI Development Act also considers, including company ownership and which country’s law ultimately governs the infrastructure.

An independent project tracking sovereignty claims against concrete criteria, the European Sovereignty Index, scored this specific exercise bluntly: “Weight 0” — no movement on who owns, who operates, or whose law governs, since Amazon remains the owner regardless of how the network test goes. That’s not a dismissal of the test’s technical validity. It’s a precise statement of its scope: proving a system can run without a particular network connection is a real, useful fact for operational-resilience purposes, and a separate fact entirely from who ultimately controls that system and under what legal jurisdiction.

This isn’t a new critique specific to this test, either — a sovereignty analyst flagged the same structural gap back in January, when ESC first launched: operational-independence announcements, however real, don’t by themselves resolve the ownership and jurisdiction questions regulators actually care about.

Why this is happening now, specifically

The timing sits next to a separate, concrete regulatory process worth knowing about: the European Commission is reportedly preparing draft findings — per Bloomberg, citing people familiar with the matter — that both AWS and Microsoft Azure meet the criteria for “gatekeeper” designation under the EU’s Digital Markets Act, with a decision expected in November. Preliminary findings were sent to both companies in June, and both are reportedly pushing back. Nothing here confirms this specific test was scheduled because of that investigation, but a European cloud provider demonstrating EU-specific operational independence in the weeks before a major EU regulatory decision is, at minimum, well-timed from AWS’s perspective.

There’s also a genuinely practical driver independent of any PR angle: the EU’s Digital Operational Resilience Act (DORA) requires regulated financial institutions to be able to test failover without leaning on a vendor’s own support during an actual outage. A bank using AWS’s European Sovereign Cloud needs exactly this kind of demonstrated, intentional “pull the cord” exercise to satisfy that requirement — this test serves a real compliance need for AWS’s regulated customers, separate from whatever signal it sends regulators evaluating gatekeeper status.

The connection worth drawing to AWS’s other recent news

This site covered AWS’s permanent data loss in its Bahrain and UAE regions last month, where drone strikes exceeded what multi-AZ redundancy was ever designed to withstand. That incident and this October test sit on opposite ends of the same underlying question: can a cloud region keep operating when something outside AWS’s control disrupts it? Bahrain and the UAE answered that question the hard way, with real data permanently lost. This October exercise is AWS proactively, deliberately testing a much narrower and more controlled version of the same question for its EU customers — not because the threat models are identical, but because “what happens when connectivity to the rest of our infrastructure breaks” is clearly a question AWS is taking more seriously across its business than it was a year ago.

What to actually take from this if you’re evaluating sovereign cloud options

• Treat “operational independence” and “sovereignty” as genuinely different claims, not interchangeable marketing language — this test is strong evidence for the first, and explicitly not evidence for the second.
• If ownership and jurisdiction matter for your specific compliance requirement, this test doesn’t resolve that question no matter how cleanly it executes on October 24 — you still need to evaluate that separately, likely with legal counsel familiar with your specific regulatory obligation.
• If your actual requirement is DORA-style operational resilience, this is a meaningful, concrete data point in AWS’s favor — a real, scheduled, verifiable drill is a stronger signal than an unverified claim of resilience.
• Watch the DMA gatekeeper decision in November independently of this test’s outcome — that’s a separate, consequential regulatory process that will shape AWS’s EU obligations regardless of how the October 24 exercise goes.

Official reference: AWS’s own announcement via the AWS Security Blog and AWS News Blog (aws.amazon.com), cross-checked against Cloud Computing News, Web Hosting News, and the European Sovereignty Index’s published scoring of the exercise, all dated late September to early October 2026. The DMA gatekeeper designation remains a draft finding as of this writing — confirm current status before treating it as a final decision.