From the AWS edition of November 1, 2026
AWS reports its European Sovereign Cloud ran for several hours with its global backbone and operational data transfer system switched off
Amazon Web Services (AWS European Sovereign Cloud) · Government cloud; sovereign and regulated infrastructure · European Union (Brandenburg, Germany); limited U.S. SLED transferability
- Publisher
- AWS Security Blog
- Original publication
- 2026-11-01
- Source retrieved
- 2026-11-02
- Event date
- 2026-10-24
What happened
AWS's sovereign cloud managing director reports (Nov 1) that on Saturday, Oct 24, 2026, the team switched off both global systems the AWS European Sovereign Cloud normally uses: the AWS Global Network backbone and an EU-operated system for limited, controlled transfers of operational data. Traffic rerouted over the public internet, and for several hours the partition ran on its own software and hardware, operated by EU-resident staff. AWS says workloads kept running, customers could access data, and there was no availability impact on the sovereign cloud, other Regions or Direct Connect. AWS calls it the first public technical exercise of a sovereign Region's independence and says customers can use the result with regulators. The post quotes Capgemini, Atos, Genesys and Accenture, all partners.
Why it matters
Limited and indirect. U.S. state and local governments do not buy the EU partition, but state data-residency rules, CJIS and continuity planning raise the same question of what keeps running when a provider's shared systems are cut. The post shows what a provider-run isolation test can look like and what evidence to ask for; it is not evidence about GovCloud or any U.S. Region.
Evidence and measured results
Vendor-authored results report with no published method, duration in hours, metrics, service list, error logs or independent observer. Supporting quotes come from AWS partners. The pre-exercise AWS post (Sep 28) announced the plan; SIPRONE's Oct 26 commentary, filed separately, lists the open questions.
Limitations and uncertainty
Self-reported; short duration; no metrics or observer; EU partition only; ownership and legal jurisdiction unchanged; not AI-specific.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies with residency or continuity mandates cannot verify what their cloud provider can do when shared global systems are cut.
- Stakeholders
- State CIO or CISO
- Continuity of operations planner
- Procurement and contracts lead
- Discovery questions
- Do your laws or contracts require in-jurisdiction operation or isolation capability?
- What evidence would your auditors accept for provider independence?
- Which applications must keep running during a provider network disruption?
- Value hypothesis
- Clear isolation-evidence requirements may strengthen an agency's cloud assurance package; this post alone does not supply that evidence for U.S. Regions.
- Potential engagement
- A short requirements workshop defining provider isolation-test evidence and an agency-side dependency map for one critical system.
- Unsupported claims
- That GovCloud or any U.S. Region has been isolation-tested
- Independent verification of the EU result
- Legal sovereignty or immunity from U.S. jurisdiction
Pre-sales engineering
Role takeaway
- Fit
- Relevant only as a reference for continuity and residency design discussions.
- Architecture and integration
- Informs dependency mapping across identity, DNS, key management, monitoring and update channels for workloads in any Region.
- Prerequisites
- Application dependency inventory
- Test environment able to simulate network cuts
- Constraints
- EU partition only
- Exercise lasted hours, not days
- Region stayed internet-connected
- Security
- Check encryption and monitoring on rerouted paths and certificate and token lifetimes during any isolation scenario.
- Proof of value
- Run a time-boxed isolation drill on a test copy of one application
- Record which dependencies fail and when
- Compare drill results with provider assurance documents
Delivery
Role takeaway
- Work
- Plan and run an agency-side isolation drill and produce a dependency gap report.
- Dependencies
- Continuity office sponsorship
- Test environment
- Application owners' time
- Ownership
- Agency continuity of operations lead with the cloud platform team.
- Skills and adoption
- Operations staff practice dependency mapping and failure drills.
- Governance checkpoints
- Approval of drill scope and safety limits
- Review of findings with security and continuity leads
- Acceptance criteria
- Dependency inventory covers all external services for the chosen application
- Drill run for an agreed duration with failures logged
- Remediation owners assigned for each gap found
- Risks
- Over-reliance on a provider self-report
- Drill disrupts production if scoped poorly
- Assuming EU results apply to U.S. Regions
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
The exercise covers two dependencies (backbone and operational-data transfer) while the region stayed on the public internet. It does not show behavior of identity, DNS, certificate renewal or update channels over a longer cut.
Governance
Who approves, reviews and stays accountable for outcomes?
AWS positions the result as compliance evidence for regulators and boards. Without a method or third-party attestation, governance teams should treat it as a provider statement, not an audit.
Security and privacy
What data, permissions and controls need testing?
Rerouting over the public internet during isolation shifts traffic paths; the post does not describe encryption or monitoring changes during the window.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
No workforce or accessibility content beyond AWS's plan to move to EU-citizen operators.
Procurement
What should contracts, pricing and exit terms secure?
Buyers can ask any cloud provider, including for U.S. government Regions, for isolation-test methods, scope and results in contracts or assurance packages.
Operating model
Which teams own the service once it runs?
Shows a provider-run continuity exercise model; customer application dependencies outside the region are not tested.
Publication history
- 2026-11-01AWS · Issue 044 resources
Stable resource ID: aws-european-sovereign-cloud-independence-exercise-results-20261101