- AWS says it will run its European Sovereign Cloud for several hours on October 24, 2026 without its global backbone network or a dedicated data-transfer system.
- A sovereignty claim is a statement about dependencies. Cutting them under controlled conditions turns the claim into evidence, though AWS runs the test itself.
- Customers should ask AWS for the exercise results and check whether their compliance files can use them.
Every sovereign cloud makes the same promise: it can run on its own. A data center in the right country does not prove that. The proof is a list of outside things the system needs, and a test that switches them off.
AWS has now announced a test of exactly that. It says it will cut its European Sovereign Cloud off from two global systems for several hours. The plan is a useful template for judging any provider's independence claim.
What AWS says it will do
AWS Security announced the exercise on September 28. It is set for Saturday, October 24, 2026. On that day, the cloud will spend several hours cut off from the AWS global backbone.
In daily use, AWS's private backbone network carries approved operational data between its locations. That data stays off the public internet. During the test, the same traffic will be rerouted over the public internet. The cloud will rely only on its own links from European internet providers.
AWS says the team running the test will be made up entirely of EU residents working inside the EU. They will use only the hardware and software of the European Sovereign Cloud.
How the test works
AWS names two global systems in everyday operation. The first is the backbone. The second is a dedicated system run and supervised by the local EU team. It handles a small, controlled flow of operational data.
AWS says that system brings in vetted copies of source code and software updates. It sends out only a short list of approved routine information. During the test, the team will switch it off completely.
AWS states that neither system is operation-critical. It also says it has committed to keep customer content, and metadata that customers create, inside the EU. The test is meant to show the cloud keeps running with both systems off.
Switching network routes has a side effect. AWS calls it convergence: other networks need a short time to update their routing tables. Customers may see brief connectivity drops at the start and the end.
AWS says the test will not affect service availability inside the cloud. It says other AWS Regions and Direct Connect private links will also stay unaffected.
Sovereignty is a dependency map
The lesson here is that sovereignty depends less on where servers sit. It depends more on what they need from elsewhere. Software updates, source code and operational data all flow somewhere. Each flow is a possible dependency.
Hospitals test backup power by cutting the mains, not by reading the generator manual. A sovereignty claim deserves the same treatment. A promise of running without outside help means little until someone removes the help.
AWS also explains why it normally stays on the backbone. It says the backbone gives better performance, capacity, reliability, security and cost. That is AWS's own view. It suggests independence is a capability held in reserve, not the daily mode.
What the test cannot settle
AWS runs the exercise, and the results will come from AWS. The company says it will share an update afterwards with regulators and customers.
AWS says the test is designed to be consistent with the objectives of two frameworks. One is the European Commission's EU Cloud Sovereignty Framework. The other is the C3A criteria from Germany's Federal Office for Information Security (BSI). The announcement does not name an outside body that will certify the result.
It also leaves open what exactly will be measured, and who will observe it. Several hours say little about how updates and source mirroring would work over a longer stretch. A single test is one data point, not a track record.
Questions to put to your cloud team
If you run regulated workloads in Europe, start with your AWS account team. Ask what evidence the exercise will produce, and in what form. AWS says the results will add to the compliance and assurance packages that its sovereign reference framework supports. Ask whether yours can use them.
Then ask the harder questions. Which of your own dependencies sit outside the EU? Would your auditors accept a vendor-run test as evidence? Does your team know how brief connectivity drops at the start and end could affect your workloads?
Hold every provider that claims independence to the same standard. Ask what they would switch off, for how long, and who would watch. A claim that has not been tested is still a promise.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: AWS Security.
