AWS Will Run Its European Sovereign Cloud Without the Global Backbone for Several Hours

On October 24, AWS will temporarily disconnect its European Sovereign Cloud from the AWS Global Network backbone for several hours. The region is expected to continue operating independently during this time, although the implications of this exercise are still being debated.

The disconnection involves two systems: the AWS Global Network backbone, which transfers operational data between AWS locations, and a dedicated channel for limited data transfers that will be completely turned off. As a result, traffic will revert to the public internet using local links from European ISPs.

Stéphane Israël, managing director of the AWS European Sovereign Cloud, stated that the operation will be managed by a team composed entirely of EU residents, utilizing the region’s own hardware and software from data centers in Brandenburg. These centers maintain a local copy of the source code within the EU. Customers may experience brief disruptions as data routes adjust.

AWS clarified that neither of the systems being disconnected is critical for operations, which is why the region can function without them. This setup is typically used every other day of the year. While customer content and metadata remain within the EU, some operational data may still be transferred outside.

Israël emphasized that the exercise aligns with the EU Cloud Sovereignty Framework and Germany’s BSI C3A criteria, allowing customers to incorporate the results into their compliance documentation. Regulatory bodies will also be informed afterward. However, AWS stops short of claiming any certification for this operation.

The exercise has sparked discussions among experts regarding its implications for cloud sovereignty. Fadi Dasus, a senior cloud security architect, pointed out that the test raises two key questions: the technical aspect of service continuity if the US link is severed, and the legal aspect concerning US laws that may compel data access or service interruptions.

Dasus noted that while the technical aspect shows progress in resilience, the legal concerns remain tied to AWS’s US parent company, indicating that true sovereignty has not yet been achieved.

Lars Larsson Lundsten, field CTO at Elastisys, criticized the notion that technical solutions can resolve legal issues, despite acknowledging the engineering excellence of AWS’s architecture. He commended AWS for its cautious approach in this exercise.

Ultimately, while AWS’s efforts demonstrate progress, the conversation around cloud sovereignty continues, highlighting the complexities involved.

Source: InfoQ