{"id":3017,"date":"2025-11-04T12:48:43","date_gmt":"2025-11-04T10:48:43","guid":{"rendered":"https:\/\/35x.de\/?p=3017"},"modified":"2025-11-04T12:48:45","modified_gmt":"2025-11-04T10:48:45","slug":"aws-european-sovereign-cloud","status":"publish","type":"post","link":"https:\/\/35x.de\/en\/european-sovereign-cloud\/aws-european-sovereign-cloud\/","title":{"rendered":"Why AWS is setting new standards with the European Sovereign Cloud"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Why AWS is setting new standards with the European Sovereign Cloud<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

I was at an AWS partner event in Munich two weeks ago. Among all the exciting presentations, there was one that I found strategically very interesting: The renewed, emphatic emphasis on the imminent launch of the AWS European Sovereign Cloud (ESC)<\/strong> by the end of 2025.<\/p>

For some, this may have been just another regional announcement. I think this move is one of the smartest moves we've seen in the cloud market for a long time. Because it not only introduces a new product, but also tackles head-on and potentially ends a long-standing, deadlocked debate in the European IT market.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"AWS\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The \"feature poverty\" vs. the CLOUD Act<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The last few years in the cloud business have been characterized by a fundamental compromise. As an IT service provider, we (and our customers) were constantly faced with a binary choice:<\/p>

  1. Team A (US Hyperscaler):<\/strong> You get the full power of innovation. The price for this is a massive legal and moral stomach ache called US CLOUD Act<\/strong>. The concern that US authorities could gain access to business secrets, regardless of the storage location in Frankfurt or Dublin.<\/li>
  2. Team B (European hosters):<\/strong> You get real data security and GDPR compliance. You could justifiably argue that the data is secure. But here, too, you pay a price, namely what I simply call \u00a0\u201eFeature poverty\u201c <\/strong>were still in their infancy. Often based on OpenStack or virtualized monoliths, the depth of features and speed of innovation lagged miles behind.<\/li><\/ol>

    For years, our main argument against Team B's lack of features was that you at least get \u201ereal European hosting\u201c with us. It was a valid but defensive argument.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

    \n\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t

    Microsoft's \"sovereignty bluff\"<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Microsoft then tried to bridge this gap with its \u201eEU Data Boundary\u201c. A marketing promise to keep all M365 and Azure data in Europe. What happened? The German data protection conferences called the bluff.<\/p>

    They repeatedly found that the use of M365 in compliance with data protection regulations could not be proven. The problem was never just the Data Residency<\/em> (the storage location), but the Data Sovereignty<\/em> (the control). As long as a US company is in control, the \u201ebackdoor\u201c of the CLOUD Act remains an unsolved problem. Microsoft's headlines in this area have been a PR disaster that has fundamentally damaged the credibility of the \u201eEU Data Boundary\u201c.<\/p>

    And it is precisely into this wound that AWS is now poking with surgical precision.<\/p>

    What AWS is planning in Brandenburg is not \u201eanother EU region\u201c. It is a new architectural and legal building that precisely addresses Microsoft's weak points:<\/p>

    1. Legal decoupling:<\/strong> There will be a new parent company founded in Germany<\/strong> under German law.<\/li>
    2. Operational decoupling:<\/strong> Perhaps the most important point. The operation, support and physical access are exclusively by EU citizens resident in the EU<\/strong> carried out. No US employee should have access - the CLOUD Act is therefore a dead letter.<\/li>
    3. Technical decoupling:<\/strong> This is not a \u201eVLAN region\u201c. The ESC will be its own separate \u201epartition\u201c. It will be connected via a Own, independent Identity and Access Management (IAM)<\/strong>, its own billing and even its own instances for core services such as DNS (Route 53).<\/li><\/ol>

      AWS has analyzed Microsoft's weak response to the sovereignty issue and is now building exactly what the DSK and the BSI have been implicitly demanding for years. It is noteworthy in this context that AWS is already the first provider to receive the BSI's C5 certificate, a clear signal that cyber security and compliance play a central role in building the Sovereign Cloud.<\/p>

      If the ESC were a \u201esovereignty cloud light\u201c - i.e. secure but functionally limited - the market would hardly move.<\/p>

      But AWS promises the opposite. They have announced that the ESC will not only start with the core services (EC2, S3, VPC), but also with the strategically most important innovation drivers.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

      \n\t\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t

      What the European Sovereign Cloud means for us as an IT industry<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
      \n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      There are many advantages AWS European Sovereign Cloud<\/a> is a double declaration of war.<\/p>