AWS Will Cut Its European Sovereign Cloud Off From the Global Backbone for Several Hours on Saturday

On Saturday, October 24, AWS plans to run its European Sovereign Cloud for several hours without the AWS Global Network backbone, using only EU internet providers. Here is what AWS says will happen, and what customers may notice.

Close-up of a server rack with rows of drive bays and green status lights
Photo by Domaintechnik on Unsplash

Amazon Web Services is about to pull a plug on purpose. On Saturday, October 24, 2026, the AWS European Sovereign Cloud will run for several hours without its connection to the AWS Global Network backbone, the company said in an announcement by Stéphane Israël on the AWS Security Blog. The point is to show the region can work "without depending on any infrastructure outside of the European Union (EU)."

The European Sovereign Cloud is based in Brandenburg, Germany. AWS describes its data centers as "physically and logically separate from other AWS Regions, with a local in-EU copy of the source code," operated only by EU residents.

What gets switched off

AWS says the region normally relies on two global systems, and both will be off during the exercise. The first is the AWS Global Network backbone, the private network that carries authorized AWS operational data between AWS locations. During the test, that traffic "will securely reroute over the public internet." The second is a dedicated system, controlled by the local EU team, that handles limited transfers of operational data such as vetted source code mirroring and software updates. AWS says the team will disable it entirely.

Instead of the backbone, the region "will exclusively use its dedicated internet connectivity from European internet service providers." AWS says the exercise will be run by an all-EU-resident team "using only the hardware and software resources of the AWS European Sovereign Cloud."

Will customers notice?

AWS says the exercise "will not affect service availability within the AWS European Sovereign Cloud, other AWS Regions, or private connectivity through AWS Direct Connect." The one expected side effect is routing. AWS warns that customers "may experience brief connectivity disruptions" when traffic moves to the new path at the start and back at the end. It calls this convergence, the short window while other networks update their routing to reflect the change.

For network engineers, that is the interesting part. Moving a whole region's internet-facing traffic from one set of paths to another likely means BGP changes that ripple through other networks, and how quickly that settles depends partly on networks AWS does not control. The announcement does not give an exact start time or duration beyond "several hours."

What it proves, and what it does not

AWS says neither global system is "operation-critical" and that the region "can operate independently at any time." The exercise is meant to back that up with evidence, and AWS says it will share an update with customers and regulators afterward. It does not say who, if anyone, will observe the test independently or what the update will contain.

That matters because sovereignty is mostly a procurement question in Europe right now, and buyers will want more than a provider's own account. Still, a scheduled, public disconnection is a more concrete claim than most cloud providers make.

For customers in the region

  • Expect brief connectivity blips at the start and end of the window on October 24, per AWS. Avoid scheduling sensitive cutovers or maintenance in the region that day.
  • Watch your own monitoring for latency or path changes to internet-facing endpoints during the window; workloads using Direct Connect should not be affected, AWS says.
  • Look out for the post-exercise update AWS has promised to customers and regulators.