On Saturday, October 24, AWS will disconnect its European Sovereign Cloud from the AWS Global Network backbone and switch off a dedicated channel used for limited data transfers. The region is expected to keep serving customers.
Traffic falls back to public internet links from European providers. Stephane Israel, managing director of the region, says the operation will be run by a team composed entirely of EU residents working in the EU, on the region’s own hardware and software, from data centers in Brandenburg that hold an in-EU copy of the source code. Customers may see brief disruption while routes converge.
AWS is candid about what the exercise does and does not show. Neither severed system is operation-critical. That is precisely why the region survives their absence, and also why both run every other day of the year.
Data handling gets a sharper line. Customer content and customer-created metadata stay in the EU. Some operational data still leaves, and the company says the test maps to the EU Cloud Sovereignty Framework and Germany’s BSI C3A criteria, with results usable in compliance packages. The post stops short of claiming certification.
That gap is where the argument sits. Fadi Dasus, a senior cloud security architect, splits sovereignty into two questions. Does the service keep running if the link to the US is cut? Can US law compel access to the data or force the provider to stop serving?
The first is being tested. The second is untouched by any outage drill, and for European regulators it is the one that carries legal weight.
