La Ecuación Digital reported on October 25 that AWS carried out its European Sovereign Cloud exercise on October 24, 2026. AWS’s September 28 announcement had described the exercise as a plan and said it would share a follow-up with customers and regulators. The reported completion and AWS’s announced test design are distinct parts of the story; the technical outcome was not part of the completion report.

What AWS planned to disconnect

AWS said the European Sovereign Cloud (ESC), its cloud environment in Brandenburg, Germany, would operate for several hours without a connection to the AWS Global Network backbone, the private network that carries authorized AWS operational traffic between locations. The plan called for that traffic to use dedicated internet connections from European providers. The ESC was to remain connected to the internet.

AWS also planned to disable a separate system used for vetted source-code mirroring, software updates and limited routine operational information. AWS said customer content and customer-created metadata remain in the EU, separate from those operational transfers. Its EU-based operations team was to use ESC hardware and software resources during the exercise.

AWS expected no effect on ESC availability, other AWS Regions or AWS Direct Connect. It also warned that customers could experience brief connectivity disruptions while network routes converged. Those were AWS’s pre-exercise expectations.

The question a several-hour exercise addresses

The announced exercise focused on short-term operational continuity under specific network conditions: whether the ESC could operate for several hours without its AWS Global Network connection and the separate operational-transfer system. It was designed to produce technical and operational evidence aligned with the European Commission’s EU Cloud Sovereignty Framework and Germany’s BSI C3A criteria.

That scope concerns operational continuity during the exercise. Legal jurisdiction and supply-chain dependence are separate questions, and AWS described the exercise as evidence for customer and regulatory assurance, not as a certification.