Dispatch, 2026-11-12, SHC Team, Sovereign compute
Where your data sits isn't the same as who controls it
Filed 2026-11-12 · SHC Team
On Saturday, Oct. 24, Amazon Web Services (AWS) ran its European Sovereign Cloud for several hours without the company's private global network. The aim was to show the region can operate without depending on infrastructure outside the European Union (EU). AWS announced the test on Sept. 28 and reported on Nov. 1 that workloads kept running.
What happened
AWS opened the European Sovereign Cloud in January 2026, with its first region in Brandenburg, Germany. AWS says the region is physically and logically separate from its other regions, and that all customer content stays in the EU.
Normally the region uses two global systems: AWS's private network backbone, and a system run by the local EU team for limited transfers of AWS operational data. During the test, the team switched both off and traffic went over the public internet instead. AWS says workloads kept running and customers could still reach their data. Neither AWS post names an outside auditor or observer, so the result rests on AWS's own account.
AWS frames sovereignty as more than location. Its Nov. 1 post says the cloud is managed through "dedicated European legal entities established under German law" and that "only EU residents located in the EU control its operations and support." Its FAQ for the region adds that AWS "can only respond to legal requests for data where we have the technical ability to do so," and that encrypted content "is useless without the applicable decryption keys."
What changes for you
If your business, law firm or co-op keeps its data in the US, location can feel settled. It isn't the whole question. The US CLOUD Act (2018), short for Clarifying Lawful Overseas Use of Data Act, says a provider must meet US legal demands to preserve or disclose customer data in its "possession, custody, or control," whether that data is stored inside or outside the United States. What matters is control: who holds the encryption keys, who holds the top admin accounts, and who can switch your service off. AWS's test asked a version of that last one: what keeps running when the links to the rest of AWS are cut?
Holding your own keys does not put your data beyond the law. It does mean a provider can't hand over what it can't read, which is AWS's own point. For a law firm with client files or a co-op with member records, that difference matters.
What you can do
- Ask who can read your data. Ask your email, file and backup providers, in writing, whether their staff can read your data and whether you can hold the encryption keys.
- Keep the top admin accounts in-house. Someone in your organization, not only a vendor or contractor, should hold the main admin login and recovery codes for your domain, email and cloud accounts.
- Ask how legal demands are handled. Ask which company you actually contract with, and whether it tells customers about a government demand when the law allows it.
- Run your own small unplug test. Once a year, export your email and files and check that you can open them somewhere else.
- Read what providers publish. Our data residency page lists SHC's sites by state and says plainly that the CLOUD Act applies to us as a US company.
Sources
- AWS Security Blog, "AWS European Sovereign Cloud: Demonstrating an independent operation", 2026-09-28
- AWS Security Blog, "Inside a successful AWS European Sovereign Cloud exercise to demonstrate independent operation", 2026-11-01
- Amazon Web Services, "Frequently Asked Questions (FAQ)," AWS European Sovereign Cloud, undated page, accessed 2026-11-06
- U.S. Government Publishing Office, "18 U.S.C. § 2713, Required preservation and disclosure of communications and records" (CLOUD Act, Pub. L. 115-141), enacted 2018-03-23