Skip to content
Trusted IT partner since 1994+1 917 628 2365
Free Security Check[email protected]

The trust question every board should ask about AWS, Azure and Google Cloud

Why Move Your Business Data from US Clouds to a Private EU Cloud

Amazon, Microsoft and Google run some of the best-engineered infrastructure in the world. The problem is not their technology. It is that a European company keeping its critical data with them depends on a foreign government’s laws, a foreign government’s politics and a supplier that sets its own prices and exit terms. In 2026 each of those dependencies became visible. A private cloud in a European data center, under EU law, on hardware dedicated to you and encrypted with keys only you hold, removes them, and for steady workloads it often costs less.

Updated · 13 min read

In short: trust in a cloud provider comes down to four questions. Who can be forced to hand over your data? Who can switch your service off? Who sets your price? And can you leave? For a US hyperscaler, the honest answer to the first two includes the US government, and the answer to the last two is mostly the provider. For a private cloud in the EU, the answer to all four is you, under European law. That is why sensitive and critical workloads are moving, while global and commodity ones can stay where they are.

Diagram: a business workload on a US hyperscaler, exposed to US law, a political kill switch and lock-in, is assessed, moved and operated on a private EU cloud with EU jurisdiction, customer-held keys, dedicated hardware and a second EU site for recovery.
70%
of Europe’s cloud market is held by Amazon, Microsoft and Google
Synergy Research Group, 2025
85%
of German companies say they depend too much on US cloud providers
Bitkom Cloud Report, 2026
$2m
a year cut from 37signals’ cloud bill after moving compute off AWS to its own servers
The Register, May 2025
Jan 2027
when the EU Data Act removes all cloud switching and egress charges
European Commission

This is a trust problem, not a technology problem

Nobody serious argues that AWS, Azure or Google Cloud are badly run. They are fast, feature-rich and secure against most attackers. Trust is a different test. It asks what happens when the interests of the provider, or of the government it answers to, stop lining up with yours. For years European businesses could assume that would never matter. Since 2025 a French Senate hearing, a sanctions case, an EU kill-switch debate and a regulator calling out lock-in have shown that it can.

We covered the market data, the full timeline and the EU rules in our earlier analysis, Europe’s Cloud Exit. This article is about the decision itself: why the trust gap exists, why the hyperscalers’ “sovereign” editions narrow it without closing it, and why a private cloud in the EU is, for most critical workloads, the cleanest answer.

1. US law follows the company, not the data center

Putting your data in Frankfurt or Dublin answers where it is. It does not answer who can be compelled to hand it over. The US CLOUD Act requires providers under US jurisdiction to disclose data in response to valid US legal process “regardless of where the company stores the data”, as the US Department of Justice puts it. US intelligence law, notably FISA Section 702, reaches the same companies. When the French Senate asked Microsoft France’s director of legal affairs in June 2025 whether he could guarantee that French customers’ data would never be handed to US authorities without French consent, he answered under oath: “No, I cannot guarantee it.” He added that it had never happened. Both statements can be true. The point is that the guarantee is not his to give, and the same holds for every US-owned provider.

The legal bridge for personal data is shaky too. The EU-US Data Privacy Framework is still in force, but it leans on US oversight bodies whose independence the US Supreme Court weakened in Trump v. Slaughter on 29 June 2026. The European Data Protection Board has asked the Commission to assess the impact, and noyb has asked for the framework to be repealed. The two previous EU-US data deals were struck down by the EU’s top court in 2015 and 2020. A data strategy that depends on a third deal surviving is a bet, not a plan.

2. A political kill switch is no longer theoretical

In May 2025 the Associated Press reported that, after US sanctions on the International Criminal Court, its chief prosecutor lost access to his Microsoft email. Microsoft denies suspending services to the court itself, and the details remain disputed. The lesson businesses drew does not depend on those details: a US provider must follow US sanctions and export rules, and those rules can change with an executive order. The ICC later moved about 1,800 workstations to the German open-source suite openDesk.

Europe’s leaders and its largest companies now say the quiet part out loud. When the Commission presented its tech sovereignty package in June 2026, Executive Vice-President Henna Virkkunen said it wants to make sure cloud providers running critical workloads do not have a “kill switch”, and that US companies would struggle to reach the highest sovereignty levels because of the CLOUD Act. A month later Airbus picked the French provider Scaleway for about 70 critical applications, citing protection against exactly that risk. Microsoft has committed contractually to contest in court any order to suspend its European cloud operations. That is a welcome promise, and it is also an acknowledgement that the order could come.

3. “Sovereign” editions narrow the gap but keep the owner

The hyperscalers have answered with sovereign products, and some of the engineering is impressive. The AWS European Sovereign Cloud, live in Brandenburg since January 2026, is run by EU legal entities with EU-resident staff. On 24 October 2026 AWS disconnected it from its global network backbone for several hours as an independence test, and reported on 1 November that service availability was not affected. Microsoft offers sovereign public and private cloud options, and Google sells sovereign tiers through partners such as S3NS in France.

What none of them changes is who owns the company at the top. The AWS offering is, in the words of Forrester’s Dario Maisto, “still entirely owned by the US mother company”. A US parent can be served with US orders, and it controls the software, the updates and the roadmap of what runs in your sovereign region. Independent questions also remain open, such as how long such a region can run without its parent’s control plane, identity tokens and certificates. When the European Commission scored bidders for its own €180 million sovereign cloud tender in April 2026, the contract went to four European groups, and the Google-linked bid reached only the minimum sovereignty level. Sovereign editions are a real step up from a standard EU region. They are not the same thing as European control.

4. You do not set the price, and leaving was built to be hard

Three companies hold about 70% of Europe’s cloud market. That concentration shows up in your contract: proprietary managed services that only run on one platform, discounts tied to multi-year spend commitments, and egress fees for taking your own data out. In June 2026 the European Commission set out its preliminary view that AWS and Azure should be designated gatekeepers under the Digital Markets Act, pointing to lock-in effects. A final decision was reported as possible this month.

The economics can favour leaving. The software company 37signals spent more than $3.2 million a year on AWS. After moving its compute onto about $700,000 of its own Dell servers, its cloud bill fell by about $2 million a year, and replacing its S3 storage with its own arrays was expected to save a further $1.3 million a year, The Register reported in May 2025. Your numbers will differ, and a private cloud needs people to run it. But for steady, predictable workloads, paying a hyperscaler’s premium for elasticity you never use is a choice, not a law of nature. From 12 January 2027 the EU Data Act removes switching and egress charges entirely, so the biggest one-off cost of leaving disappears.

5. Their bad day becomes your bad day

When thousands of European businesses share one provider’s control plane, a single fault lands on all of them at once. In October 2025 an AWS failure in its US-East region disrupted around 2,000 companies for about 14.5 hours, and nine days later an Azure configuration error took retailers and Dutch Railways offline. No data center is immune to failure, private ones included. The difference is that in your own private cloud you decide how many sites you run, how failover works and when it is tested, rather than waiting for a status page.

The trust test: US cloud, sovereign edition or private EU cloud

Illustration: three options scored on four trust questions. A US hyperscaler’s EU region: US law can compel the parent, US sanctions apply, the provider sets prices and exit is hard. A hyperscaler sovereign edition: EU operator but a US parent, and the provider still sets prices. A private cloud in an EU data center: EU law only, no foreign kill switch, your own budget and an open, portable stack.
Trust questionUS hyperscaler, EU regionHyperscaler “sovereign” editionPrivate cloud in an EU data center
Who can compel access to your data?EU authorities, and US authorities through the US parentEU operator, but the US parent remainsEU authorities only, under EU law
Who can switch your service off?The provider, which must follow US sanctions and export rulesReduced: EU staff and contractual pledges, same US parentNo foreign party; you and your EU operator under contract
Who holds the encryption keys?The provider by default; customer-managed keys cost extraCustomer and external key optionsYou, in your own key management or HSM
Who sets the price?The provider, list prices plus commitmentsThe provider, usually at a premiumYou: owned or leased hardware, predictable run costs
Can you leave?Hard: proprietary services, egress fees until January 2027Hard: same proprietary servicesYes: open, portable stack such as Kubernetes and standard storage
Who carries the operations?The providerThe providerYour team or a managed partner, 24/7

Why a private EU cloud is the strongest answer for critical data

A European public cloud already removes the US-parent problem, and for many general workloads it is the right choice. For the data and systems your business cannot afford to lose, leak or have switched off, a private cloud goes further:

  • Jurisdiction you can explain to a regulator: an EU data center, an EU operator and EU law, with no foreign parent in the chain.
  • Keys only you hold — encryption keys in your own key management system or hardware security module, so even your infrastructure partner cannot read your data.
  • Dedicated hardware — no shared tenancy with strangers, and a clean scope for audits under GDPR, NIS2 and DORA.
  • Predictable cost — steady workloads on owned or leased hardware, without egress fees or a supplier’s annual price review.
  • A real exit — open, portable technology such as Kubernetes, standard virtualization and S3-compatible storage, so you are never locked in again, including by us.
  • Resilience by design — two EU sites, rehearsed failover and backups you have actually restored.

It is not the answer to everything. A private cloud needs round-the-clock operations, which means an in-house team or a managed partner. Spiky workloads, global consumer apps and specialist AI services can still be better on a hyperscaler. That is why only 4% of European organizations plan to use local providers exclusively, according to IDC. The goal is not to leave the hyperscalers on principle. It is to stop trusting them with the things you cannot afford to lose.

Seven questions to ask your cloud provider this quarter

  • 1. Which country’s courts can order you to disclose our data, and has that ever been tested?
  • 2. Under what sanctions, export or government orders could you suspend our service?
  • 3. Who holds our encryption keys, and can your staff or your parent company access them?
  • 4. Which of our workloads depend on services that exist only on your platform?
  • 5. What would it cost, in fees and engineering time, to move all our data out next month?
  • 6. How much notice do you give for price or contract changes, and what can we do about them?
  • 7. If your control plane fails, which of our systems stop, and for how long?

If the answers make your board uncomfortable, that discomfort is the risk you are carrying today.

How to move from a US cloud to a private EU cloud: the first 90 days

  • Days 1 to 30, assess: map your data and workloads, classify each by sensitivity, regulation and business impact, and price your current exposure and exit costs.
  • Days 31 to 60, design: choose the EU data centers, build the landing zone with your own keys, identity and network segmentation, and set up the second site for recovery.
  • Days 61 to 90, prove it: migrate a first wave of sensitive, loosely coupled systems, test failover and restores, and measure cost and performance against the old platform.
  • After day 90, move in waves: replace proprietary services with portable ones as you go, use the Data Act’s switching terms, and keep on the hyperscaler only what earns its place there.

How RHC Solutions moves your data to a private EU cloud

RHC Solutions has run, secured and recovered critical infrastructure for businesses since 1994, with teams in Lisbon, Sofia and Larnaca inside the EU. We are not tied to one platform: we work with European providers such as OVHcloud and with AWS, Azure and Google Cloud, so we can tell you honestly which workloads should move and which should stay. We assess your trust exposure, design a private cloud in European data centers chosen with you, migrate in phases without big-bang downtime, and then run it 24/7 with managed security, tested disaster recovery across two sites and the audit evidence your GDPR, NIS2 and DORA obligations require. You keep the keys.

Sources and further reading

News coverage

Primary sources and data

Frequently asked questions

Why shouldn’t a European business trust AWS, Azure or Google Cloud with critical data?
Not because of their technology, which is excellent, but because of structure. As US companies they can be compelled by US law to disclose data wherever it is stored, they must follow US sanctions and export rules that can change quickly, and they set the prices and exit terms of your contract. For critical data, those are dependencies a business does not control.
Isn’t storing data in an EU region of a US cloud enough?
It meets GDPR residency, but not jurisdiction. The US CLOUD Act reaches providers under US jurisdiction regardless of where data is stored, and Microsoft France told the French Senate under oath in 2025 that it could not guarantee data would never be handed to US authorities.
Are AWS, Microsoft and Google “sovereign cloud” offerings a good alternative?
They are a real improvement over a standard EU region, with EU operating entities, EU staff and stronger key options. But the US parent company remains the owner, and it controls the software and the roadmap. For the most sensitive workloads, infrastructure with no foreign parent in the chain gives a cleaner answer.
Is a private EU cloud more expensive than a hyperscaler?
For steady, predictable workloads it is often cheaper: 37signals cut about $2 million a year from its cloud bill after moving compute to its own servers. You must budget for 24/7 operations, by your own team or a managed partner, and from January 2027 the EU Data Act removes the switching and egress charges that used to make leaving expensive.
Do we have to move everything out of the US cloud?
No. Move the data and systems you cannot afford to lose, leak or have switched off, such as customer data, financial systems, intellectual property and regulated workloads, to a private EU cloud first. Global, spiky or commodity workloads can stay on a hyperscaler where it makes sense.

Ready to take back control of your data?

Talk to a senior consultant about which workloads to move, where they should run in Europe, and how to get there without downtime.