ATAILA Newsroom · Budapest ·
2026-W40
AWS will disconnect its sovereign cloud for a few hours. Sovereignty has layers.
When a Hungarian buyer asks us why not simply use AWS's sovereign region, the honest answer has always had two parts: what such a region can prove, and what it cannot. On 28 September AWS announced a public test of the first part. On the same day a trade-press report put numbers on a third part that neither AWS nor we can claim. This is our reading of both, with the layer we own marked clearly and the layers we do not own marked just as clearly.
The article we are responding to
“AWS European Sovereign Cloud: Demonstrating an independent operation”
AWS Security Blog, 28 September 2026
The exercise
The announcement is precise, which is to its credit. On Saturday 24 October 2026 the AWS European Sovereign Cloud, a separate partition run from Brandenburg and generally available since January, will run for several hours without two systems that connect it to the rest of AWS: the AWS Global Network backbone, and a dedicated system for supervised operational data transfers. AWS writes that "Neither is operation-critical, and neither affects the sovereignty assurance of the AWS European Sovereign Cloud." During the exercise the sovereign cloud "will exclusively use its dedicated internet connectivity from European internet service providers". Customers are warned of brief connectivity disruptions at the start and the end. The team running it is "composed entirely of EU residents within the EU", using only the hardware and software of the sovereign cloud itself.
AWS places the exercise under the European Commission's EU Cloud Sovereignty Framework and the German BSI's C3A criteria. The post names no independent observer and says nothing about repeating the test. It is a vendor demonstrating a property of its own product, on a Saturday, with its own staff. That is not a criticism. It is the scope.
The numbers from the other side
On the same day The Register's Dan Robinson reported a study by the Global Electronics Association with DECISION Études & Conseil, From Chips to Systems: Building an End-to-End EU Strategy for Data Centre, Cloud Infrastructure and AI. Its finding is one sentence: EU-headquartered companies account for "only six percent of the bloc's datacenter semiconductor market, seven percent of server manufacturing and assembly, and eight percent of cloud infrastructure". Taiwan makes most of the leading-edge processors, South Korean and US suppliers dominate memory, and US companies dominate servers, networking and storage, with Lenovo the Chinese exception. The association notes that the Cloud and AI Development Act aims to at least triple EU data-centre capacity within five to seven years, and warns that the gap will widen as it does. Its recommendation is industrial policy: use European demand to pull manufacturing investment into Europe.
The association is an industry body asking for exactly that policy, so the framing is interested. The percentages are not in dispute, and they apply to us as much as to anyone.
24 October
the Saturday on which the AWS European Sovereign Cloud runs for "several hours" without the AWS Global Network backbone and the operational data-transfer system (AWS Security Blog, 28 September)
2
systems disconnected, which AWS describes as not operation-critical; traffic reroutes over dedicated internet connectivity from European providers
100%
of the operational team for the exercise are EU residents within the EU, per AWS
6% · 7% · 8%
EU-headquartered firms' share of the EU data-centre semiconductor market, of server manufacturing and assembly, and of cloud infrastructure (Global Electronics Association study, via The Register, 28 September)
at least 3x
the Cloud and AI Development Act's aim for EU data-centre capacity within five to seven years, which the study says will widen the gap
Sovereignty has layers, and the test covers one of them
It helps to name the layers, because the word gets used for all of them at once.
Silicon and servers. Nobody in Europe owns this layer in this decade, and that includes us. ATAILA runs Nvidia GPUs on US and Taiwanese silicon in servers from non-European vendors. The 6, 7 and 8 percent describe our supply chain too. Anyone selling "sovereign AI" in Europe who does not say this out loud is selling a word.
Operations. Who runs the platform, from where, with whose hands and whose tools. This is the layer the 24 October exercise tests: EU residents, the sovereign cloud's own hardware, no backbone, for a few hours. If it passes, and we expect it will, AWS will have shown that the region can be operated from inside the Union when the cable is cut.
Jurisdiction. Who can compel the operator to hand over data, to switch a customer off, or to change the terms. The announcement does not address this layer at all, and no network exercise can. The operator remains a subsidiary of a United States company, and the question of what a US court or agency can order it to do is a question of law, not of routing. The Commission's own framework assesses this layer apart from operations: ownership, and whether non-EU authorities could compel access, are objectives of their own.
Location. Where the data physically sits. Both AWS's sovereign region and an ATAILA island put it inside the EU; on this layer the two are the same.
For a customer whose AI runs on hardware in its own building, the state AWS is demonstrating for several hours is the normal state every day: no backbone to disconnect, no transfer system to pause. That is not a boast. It is a description of a smaller system with a smaller surface, and it comes with its own costs.
What we concede, and what we will be asked
This is a real test, and it will probably pass. German supervision has asked for exactly this kind of evidence, AWS has announced in public that it will provide it, and for a large share of European buyers the result will be sovereign enough. We will not call it theatre, because it is not.
The study is lobbying. The Global Electronics Association wants industrial policy, and the 6, 7 and 8 percent are its argument for it. The numbers still hold, and they hold against us.
We will be asked for the same evidence. A buyer who reads AWS's announcement is entitled to ask how an ATAILA island behaves when its uplinks are cut, who can reach it from outside, and what we can be compelled to do. We owe that document, in the same plain form AWS used, and we will publish it.
What survives is the layer the test does not reach. Operational independence for a few hours is a fact about engineering. Who can compel the operator is a fact about law, and it does not change on a Saturday.
Sources, and what we did not open
The announcement we are answering: AWS European Sovereign Cloud: Demonstrating an independent operation, Stéphane Israël, AWS Security Blog, 28 September 2026. Opened and read in full; every quoted phrase is from it. That the sovereign cloud is a separate partition in Brandenburg, generally available since January 2026, is from CloudComputing News, 29 September, as read by our research pass.
The study: Europe's AI ambitions rest on somebody else's supply chain, Dan Robinson, The Register, 28 September 2026, reporting the Global Electronics Association and DECISION Études & Conseil white paper From Chips to Systems: Building an End-to-End EU Strategy for Data Centre, Cloud Infrastructure and AI. The 6, 7 and 8 percent figures were confirmed on the association's own page by our research pass; the full PDF was not read, and the page does not print the report's publication date.
The Commission's EU Cloud Sovereignty Framework and the BSI's C3A criteria are named in AWS's post. We checked the framework's published text (version 1.2.1, October 2025), which assesses strategic, legal and jurisdictional, and operational sovereignty as separate objectives, and the C3A catalogue (version 1.0, 27 April 2026), which requires a provider to be able to disconnect all non-EU network connections and to test this at least once a year. Our descriptions of both are our summary, not a quotation.
The original article
“AWS European Sovereign Cloud: Demonstrating an independent operation”
AWS Security Blog, 28 September 2026
- Read it live at AWS Security Blog
- ATAILA archive, captured 22 October 2026
← Back to the Newsroom Press enquiries: contact us