AWS / Cloud Infrastructure
November 16, 20268 min read
AWS Switched Off Its European Sovereign Cloud on Purpose. The Question That Matters Isn't Technical.
On October 24, 2026, AWS cut its AWS European Sovereign Cloud off from its global backbone for several hours, on purpose. The region kept running. That proves operational independence. It doesn't settle the legal question your compliance team actually cares about.

On Saturday, October 24, 2026, AWS did something no cloud provider had publicly done before: it cut a production region off from its own global backbone, on purpose, to prove it could keep running without it. The region was the AWS European Sovereign Cloud, located in Brandenburg, Germany. For several hours, operational traffic stopped flowing through AWS's private network and rerouted over the public internet, using the region's own links through European ISPs.
To a technical reader, this is a network-resilience drill. To an enterprise buyer with European operations, it's something else: the first public, verifiable evidence that a sovereign cloud can run autonomously within its own borders. But before that fact changes a single architecture decision, it's worth separating two questions the market keeps conflating.
What October 24 actually demonstrated
The exercise severed two systems: AWS's global network backbone (the private channel that moves operational traffic between AWS locations) and a dedicated channel for limited data transfers. Two systems come out: the Global Network backbone, the private network that moves operational data between AWS locations, and a dedicated channel for limited data transfers, switched off entirely. Traffic then falls back to the public internet over the region's own links from European ISPs. The team running the exercise was composed entirely of EU residents working from the EU, on the region's own hardware and software. Stéphane Israël, managing director of the AWS European Sovereign Cloud, says a team composed entirely of EU residents working in the EU will run it on the region's own hardware and software, out of data centers in Brandenburg that hold a local in-EU copy of the source code.
AWS was careful with the framing: the caveat comes from AWS. Neither system is operation-critical. That is why the region survives without them. The exercise didn't prove the region can live forever without those systems — it uses both every other day of the year because they deliver better performance, capacity, and cost savings. It proved it can when it has to, and that the proof is now documented for auditors and regulators.
€7.8B
Total investment in infrastructure, jobs, and skills
Jan 2026
General availability of the first region, Brandenburg
90+
AWS services available at launch
Oct 24, 2026
First public independent-operation exercise
Operational sovereignty is not legal sovereignty
Here's the distinction that actually matters for whoever decides architecture and budget: the AWS European Sovereign Cloud solves operational control — where data physically lives, who can touch it, which labor law governs the staff. By design, it doesn't resolve the question of legal jurisdiction over the parent company. AWS European Sovereign Cloud remains 100% owned by Amazon.com Inc., a U.S.-headquartered company.
You can't solve legal problems with technical solutions.
That was the reaction from Lars Larsson Lundsten, field CTO at Elastisys, a competing European provider. Lars Larsson Lundsten, field CTO at Elastisys, which sells a European alternative to US cloud platforms, put it harder, calling the architecture a marvel of engineering while also crediting AWS with restraint, noting it is extremely careful not to claim anything besides what this is able to actually prove. Other technical commentators pushed back on the strictly legal framing too: commenter Roelf Zomerman argued that the CLOUD Act and the EU e-Evidence regulation both run through criminal investigations, with judges, provider evaluation and data limits attached, rather than working as a general power to demand data. Building your own, he added, or hosting with EU providers, doesn't automatically imply you are safe from these laws.
Put differently: neither AWS's technical solution nor the "use only European providers" alternative fully eliminates legal exposure. What changes between options is the risk profile — how much legal and operational attack surface remains, and how defensible that posture is in front of a regulator or auditor.
What this means for an enterprise architecture decision
If your organization operates in Europe — or handles European customer data from anywhere — this distinction isn't academic. It determines which AWS partition you deploy into, what IAM and key-management controls you configure, and what you can show a regulator when asked where your data actually lives.
| Dimension | Standard AWS EU Regions | AWS European Sovereign Cloud |
|---|---|---|
| Data location | Within the chosen region, inside the EU | Within the EU, physically separate partition |
| Operating staff | Global AWS team | Exclusively EU residents |
| Non-EU infrastructure dependency | Connected to AWS global network | No critical dependencies outside the EU |
| Legal exposure under the U.S. CLOUD Act | Exists, via Amazon.com Inc. | Exists equally, via Amazon.com Inc. |
| Service portfolio | Full | 90+ services at launch, expanding |
Info
The gap between a standard partition and a sovereign one isn't "secure vs. insecure." It's how much documented operational control you can put in your compliance file, and how much of that actually answers your specific regulatory framework — GDPR, NIS2, DORA, or sector rules in health and finance.
Questions an enterprise buyer should answer before choosing a partition
- The actual regulatory framework: which specific law or standard applies to your sector — BSI C5, DORA, a healthcare-sector rule — and which partition satisfies that exact criterion, not a generic notion of "sovereignty"?
- Parent-entity exposure: does it matter for your use case that the ultimate entity is still U.S.-based, or do you need documented operational control rather than absolute legal immunity?
- The cost of operational friction: isolating a region from global engineers slows support and complex incident resolution; budget for that delay, not just the compute bill.
- Available portfolio: confirm the specific services your architecture needs are already live in the sovereign partition — the catalog keeps growing and isn't identical to standard regions.
- Auditable evidence: ask for the sovereign partition's SOC 2, C5, and ISO reports, not just the launch press release.
The real risk isn't the infrastructure. It's the unadvised decision
AWS European Sovereign Cloud is a solid, well-documented option. The risk isn't in the technology — it's in choosing a partition, region, and data controls based on the marketing headline instead of the exact regulatory requirement that applies to your business. That decision touches infrastructure as code from day one: how data residency gets defined, how IAM policies get locked to a region, how that configuration gets versioned so it survives an audit three years from now.
For organizations already running AWS infrastructure at scale — like the work behind Multimedios on AWS — the sovereignty question doesn't get solved once. It gets revisited every time the regulatory framework shifts, every time a new service lands in the sovereign partition, every time an auditor asks for fresh evidence. That's ongoing architecture work, not a box checked at launch.
Need help with this?
This is exactly what we do in Build (Development). Our team can implement it in your company.
Related Articles
Keep learning with these articles

AWS / Cloud Infrastructure
PHP Has Two Critical Vulnerabilities. The NSA's Advice: Patch or Disconnect.
PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 fix two remote code execution flaws rated CVSS 9.2. There is no complete mitigation. For enterprises running Drupal, WordPress, or Laravel in production, this is no longer a DevOps ticket — it's a business decision on the clock.
8 min readRead this →

AWS / Cloud Infrastructure
AWS CDK: Advantages, Disadvantages, and When It Isn't the Answer
AWS CDK lets your teams write infrastructure in TypeScript or Python instead of YAML. That solves a real problem. It also creates new ones. We compare CDK against Terraform, Pulumi, and CloudFormation with evidence, not preference.
9 min readRead this →
Want to implement this in your company?
We can help you take your business to the next level with cutting-edge technology.