On Saturday, October 24, AWS disconnected its European Sovereign Cloud from the AWS Global Network backbone for several hours to show that the region, generally available since January with its first site in Brandenburg, Germany, can operate on its own. AWS reports that workloads kept running and customers kept access to their data, and it is careful to say what the exercise does not prove, which has not stopped practitioners from arguing about exactly that.
Two systems were switched off for the exercise: the Global Network backbone, the private network that carries operational data between AWS locations, and a dedicated channel the local team uses for limited, controlled transfers of operational data. Traffic that normally crossed the backbone was rerouted over the public internet through the region's own links from European ISPs, and AWS warned beforehand that customers might see short disruptions while routes converged at either end. Stéphane Israël, managing director of the AWS European Sovereign Cloud, wrote that a team "composed entirely of EU residents working in the EU" would run the region on its own hardware and software, from data centers holding a local in-EU copy of the source code.
AWS supplied the main caveat itself. Neither of the two systems is operation-critical, which is why the region survives without them and also why it uses both on every other day of the year. The data boundary is sharper than the network one: customer content and customer-created metadata stay in the EU, while some operational data normally leaves. Israël writes that the exercise is designed to line up with the EU Cloud Sovereignty Framework and Germany's BSI C3A criteria, that customers can put the results into their compliance packages, and that regulators are briefed afterward. The post stops well short of claiming certification, and it does not pretend the region runs isolated from the rest of the year.
None of that care has settled the argument. Fadi Dasus, a senior cloud security architect, split the question in two:
Sovereignty on a US-owned cloud in the EU comes down to two areas. The technical one: does the service stop if the link to the US is cut? The legal one: can US law order it to hand over your data, or to stop serving you? If the test goes as planned, the first area is no longer entirely in American hands. The second still runs through the US parent. So, this is real progress for resilience. It just isn’t sovereignty.
Lars Larsson Lundsten, field CTO at Elastisys, which sells a European alternative to US cloud platforms, put it harder, writing that "you can't solve legal problems with technical solutions" while calling the architecture a marvel of engineering and crediting AWS with being "extremely careful not to claim anything besides what this is able to actually prove."
The legal framing drew its own pushback. Commenter Roelf Zomerman argued that the CLOUD Act and the EU e-Evidence regulation both operate through criminal investigations, with judges, provider evaluation and data limits attached, rather than as a general power to demand data; building your own or hosting with EU providers, he added, "doesn't automatically imply you are safe from these laws." Anders Bjørnestad, a principal consultant and AWS Community Hero, made a related correction: the exercise tests whether someone can shut the region off, not whether someone can read the data, which encryption can address, and any company doing business with the US is bound by US law regardless of who owns the cloud.
The hardest technical question came from a municipal IT manager rather than a vendor. Odd-Arne Haraldsen, who runs IT operations at Svenljunga Kommun in Sweden, called the design impressive and then asked what a few hours establishes:
How long can it actually operate independently? How long before systems fall out of sync? How long before authentication tokens, certificates, or licences expire? And how long before dependencies on external control planes begin to undermine that resilience? Redundancy is not the same as independence, and continued operation is not the same as sustained autonomy.
The overclaiming charge misses, because AWS has not stretched its evidence; the gap lies between what the exercise measures and what buyers keep asking. The announcement does not say what happens to global services while the backbone is down, and commenters asked how IAM works when the region is cut off from the rest of AWS and whether DNS and internet routing would hold. Commenter Jarrod B. read the audience differently, arguing that the exercise "isn't meant to appease legal purists; it's designed to satisfy European risk officers and regulators," which fits the fact that AWS hands the results to compliance teams. One exchange put the engineering in a longer perspective: a commenter recalled a global AWS outage that appeared to show parts of AWS depending on us-east-1, and Lundsten conceded that if AWS has engineered that dependency away, its architecture is better for it.
On November 1, Israël published the result. The exercise "did not affect service availability within the AWS European Sovereign Cloud, other AWS Regions, or private connectivity through AWS Direct Connect," workloads continued, and traffic returned to its normal path when it ended. The post calls that turning "a design claim into a verified result"; the questions about duration, token expiry and control-plane dependencies that Haraldsen raised remain open.