AWS European Sovereign Cloud vs EU-Owned Providers Compared

Originally published on moveinfra.eu.

The AWS European Sovereign Cloud, which reached general availability in January 2026 in Brandenburg, Germany, offers physical and logical separation from standard AWS regions and is operated exclusively by EU residents. However, it remains a wholly owned subsidiary of Amazon.com, Inc., a US corporation. For European companies evaluating cloud sovereignty, the core choice comes down to risk tolerance and technical requirements: the AWS European Sovereign Cloud provides strict operational and metadata residency in the EU while preserving access to proprietary AWS services, whereas EU-owned providers (such as UpCloud, Scaleway, OVHcloud, Hetzner, and STACKIT) provide complete legal independence from US extraterritorial laws alongside lower, more predictable infrastructure pricing.

Key takeaways

• Data and operational residency vs. legal sovereignty: The AWS European Sovereign Cloud keeps customer data, metadata, billing, and operations inside the EU under EU-resident staff. EU-owned providers offer this same operational residency, plus ultimate corporate ownership domiciled inside Europe.
• Moving to the AWS Sovereign Cloud is still a migration: Because the AWS European Sovereign Cloud is logically isolated with its own identity, billing, and account systems, moving there from eu-central-1 (Frankfurt) or eu-west-1 (Ireland) requires creating new accounts and migrating data and workloads.
• Service breadth vs. standard primitives: AWS offers a much larger catalog of proprietary managed services than any European provider. However, most 10-to-300-person companies rely primarily on standard primitives—virtual machines, Kubernetes, managed PostgreSQL or MySQL, Redis, and S3-compatible object storage—which EU-owned clouds support natively.
• Cost and egress dynamics: Under Article 29 of the EU Data Act, cloud switching charges (including data egress fees for moving to another provider) are capped at actual cost until 12 January 2027 and banned entirely from 12 January 2027.

What is the AWS European Sovereign Cloud?

In January 2026, Amazon Web Services launched the AWS European Sovereign Cloud with its initial region located in Brandenburg, Germany. AWS built this environment specifically for European public sector bodies and regulated businesses that face strict compliance requirements around data residency and operational autonomy.

In standard AWS European regions—such as Frankfurt (eu-central-1), Ireland (eu-west-1), or Stockholm (eu-north-1)—customer content stays in the selected region by default. However, account management, billing systems, global IAM planes, and certain operational metadata are connected to AWS's global infrastructure, and support or maintenance may involve non-EU personnel.

The AWS European Sovereign Cloud changes this architecture in several ways:

• Physical and logical separation: The infrastructure is separate from existing AWS regions, with no critical dependencies on non-EU infrastructure. It even maintains a local, in-EU copy of the source code required to run the cloud.
• Metadata residency: Not only customer application data, but also customer-created metadata (such as resource tags, IAM role names, and configuration details) and billing records remain inside the EU.
• EU-resident personnel: Day-to-day operations, data center access, and technical support are restricted exclusively to AWS employees who are EU residents located within the European Union.
• Corporate governance: The cloud operates under dedicated European legal entities managed by EU nationals, supported by an independent advisory board. In early 2026, it achieved its initial C5 (BSI Cloud Computing Compliance Criteria Catalogue) and SOC 2 reports alongside ISO certifications.

For organizations that are deeply tied to AWS-specific APIs and need verified assurance that operational metadata and support tickets never leave European borders, this architecture is a major upgrade over standard AWS regions.

How EU-owned cloud providers differ

While AWS has engineered strong technical and operational boundaries in Brandenburg, EU-owned cloud providers start from a fundamentally different legal foundation. Providers such as UpCloud (Finland), Scaleway (France), OVHcloud (France), Hetzner (Germany), STACKIT (Germany), IONOS (Germany), and Exoscale (Switzerland/Austria) are headquartered in Europe and owned by European parent companies.

When comparing these two models, compliance teams, CTOs, and CFOs usually divide sovereignty into three distinct layers:

1. Data and metadata residency

Both the AWS European Sovereign Cloud and EU-owned cloud providers keep your databases, object storage buckets, backups, and operational metadata inside European borders. On this layer, both options satisfy strict geographic localization requirements.

2. Operational sovereignty

Operational sovereignty measures who controls the keyboards and whether the cloud can keep running if cut off from the rest of the world. AWS addresses this in its Sovereign Cloud by staffing exclusively with EU residents and running periodic exercises to demonstrate that the region can operate independently of the global AWS network backbone. EU-owned providers achieve this natively, as their core engineering, executive leadership, and network operations centers are already based in Europe.

3. Legal and corporate sovereignty

This is where the two paths diverge. However autonomous a local European subsidiary may be in its daily operations, the AWS European Sovereign Cloud ultimately belongs to Amazon.com, Inc., a US company.

Under the US Clarifying Lawful Overseas Use of Data (CLOUD) Act of 2018, US law enforcement authorities can compel US-based technology companies to provide data stored on servers regardless of whether that data is located in the United States or a foreign country, provided the parent company exercises "possession, custody, or control" over the subsidiary.

AWS states that it uses strong technical, operational, and legal measures to challenge unlawful or conflicting law enforcement requests, and notes that customer encryption keys can be managed separately. For many commercial companies, those safeguards are sufficient. However, for European businesses whose clients, regulators, or public-sector tenders explicitly require immunity from non-EU extraterritorial laws, only a provider whose ultimate parent company is domiciled in the EU or EEA completely removes US jurisdiction from the legal chain.

Side-by-side comparison

The table below outlines the practical differences between standard AWS EU regions, the AWS European Sovereign Cloud, and EU-owned cloud providers.

Feature / Criterion	Standard AWS EU Regions (e.g., Frankfurt)	AWS European Sovereign Cloud (Brandenburg)	EU-Owned Cloud Providers (UpCloud, Scaleway, OVHcloud, etc.)
Ultimate parent company	Amazon.com, Inc. (US)	Amazon.com, Inc. (US)	European corporate parent (EU / EEA / CH)
Application data location	EU (customer selectable)	EU only (Germany, plus select EU Local Zones)	EU / EEA data centers
Account metadata & billing	Global AWS control plane	Strictly within the EU	Strictly within Europe
Operations & support staff	Global follow-the-sun staff	EU residents located in the EU only	Primarily EU-based staff
Exposure to US CLOUD Act	Yes	Legal debate remains due to US parent ownership	None (for providers without US operations/nexus)
Service catalog depth	200+ services (full AWS catalog)	Comprehensive, though slightly smaller than standard regions	Focused on core IaaS, PaaS, Kubernetes, and managed databases
Migration required from AWS Frankfurt/Ireland?	N/A	Yes (separate accounts, IAM, and network plane)	Yes (rebuild infrastructure and replicate data)
Pricing structure	Complex; high bandwidth and managed service markups	Dedicated sovereign pricing; complex metering	Transparent, flat or bundled bandwidth, lower compute/storage rates

The hidden catch: moving to the AWS Sovereign Cloud is still a migration

A common misconception among executives is that switching from AWS Frankfurt (eu-central-1) to the AWS European Sovereign Cloud is a simple configuration toggle in the AWS Console.

Because the Sovereign Cloud is physically and logically isolated from standard AWS partitions, it does not share a global IAM plane, Organization structure, billing account, or private VPC peering backbone with standard AWS regions.

To move an existing workload from a standard AWS region into the AWS European Sovereign Cloud, your engineering team must:

1. Establish a separate sovereign account and billing agreement.
2. Provision new networks, security groups, IAM policies, and compute resources inside the sovereign partition.
3. Replicate databases and copy S3 buckets across the boundary between the standard AWS partition and the sovereign partition.
4. Update CI/CD pipelines, secrets, and DNS records to point to the new environment.

Your existing Infrastructure-as-Code (such as Terraform or CloudFormation templates) will require far fewer edits when moving to the AWS Sovereign Cloud than when moving to an EU provider, provided all the AWS services you use are available in the Brandenburg region. However, because you still have to perform a full data migration and cutover window, many engineering and finance leaders use this mandatory migration moment to evaluate whether they should move to an EU-owned cloud instead.

Technical trade-offs: proprietary services vs. standard infrastructure

When evaluating whether to stay within the AWS ecosystem or move to an European provider like UpCloud, Scaleway, OVHcloud, or STACKIT, the most important technical question is what services your application actually uses.

When the AWS Sovereign Cloud is the stronger fit

If your software architecture is built heavily around AWS-proprietary services—such as Amazon DynamoDB, AWS Step Functions, Amazon Kinesis, AWS Glue, or Amazon Redshift—moving to an EU-owned cloud requires rewriting application code. Re-architecting a core product away from DynamoDB to PostgreSQL takes engineering time and carries delivery risk. If you need stronger EU operational residency without changing your application code, the AWS European Sovereign Cloud is designed for your situation.

When EU-owned providers are the stronger fit

In practice, a high percentage of European SaaS companies, digital agencies, and mid-market enterprises do not rely deeply on proprietary cloud APIs. Instead, their stack consists of portable, industry-standard components:

• Linux virtual machines or managed Kubernetes clusters (EKS equivalents).
• Relational databases running PostgreSQL or MySQL (RDS equivalents).
• Redis-compatible in-memory caches (ElastiCache equivalents).
• S3-compatible object storage for files and backups.
• Standard load balancers, private networks, and firewalls.

Every major EU-owned cloud provider offers these core building blocks(though Hetzner focuses on unmanaged virtual and dedicated servers where Kubernetes and databases are run directly on instances, while UpCloud, Scaleway, OVHcloud, and STACKIT provide fully managed databases and Kubernetes). When your application uses standard open-source protocols, you can run on European infrastructure without rewriting your application logic.

Pricing, egress fees, and regulatory drivers

Cost and compliance are closely linked when comparing hyperscalers with European providers.

Predictable infrastructure spend

Hyperscaler bills often grow unpredictable due to itemized charges for NAT gateways, cross-AZ data transfer, IOPS provisioning, and high markups on managed databases. European cloud providers typically compete by offering simpler pricing structures, lower baseline costs for CPU, RAM, and NVMe storage, and generous or flat-rate outbound bandwidth allowances. (Because cloud pricing varies by region and instance generation, always check each provider's official pricing page for current 2026 list prices.)

The EU Data Act and switching costs

Historically, high data egress fees made leaving a hyperscaler expensive. Under Article 29 of the EU Data Act (Regulation (EU) 2023/2854), cloud providers may charge no more than their actual, directly incurred costs for switching-related data egress until 12 January 2027. Starting on 12 January 2027, switching charges—including data egress fees when migrating to another provider—are banned across the EU. This removes the financial penalty for copying terabytes of object storage and database state out of standard AWS regions.

DORA and exit strategies

For financial entities and their critical ICT suppliers, the Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) has applied since 17 January 2025. DORA requires covered institutions to manage ICT third-party concentration risk and maintain documented, tested exit strategies for critical services. Moving standard workloads to EU-owned providers—or maintaining portable Terraform configurations that do not rely on proprietary hyperscaler APIs—directly supports DORA compliance.

Decision checklist: which path fits your company?

Use this checklist with your leadership and engineering teams to decide which environment matches your constraints:

1. Audit your customer and regulatory requirements: Do your customers or regulators require only that data and operations stay in the EU, or do they require a provider free from US corporate ownership and the US CLOUD Act?
2. Inventory your cloud bill and service usage: List every AWS service accounting for more than 1% of your monthly spend. Are they standard primitives (EC2, RDS Postgres/MySQL, EKS, S3, ElastiCache) or proprietary services (DynamoDB, Redshift, Cognito)?
3. Compare total cost of ownership (TCO): Model your current resource footprint (vCPUs, RAM, storage, and monthly bandwidth) against the sovereign pricing of AWS versus an EU provider like UpCloud, Scaleway, or OVHcloud.
4. Assess migration effort: Since moving from eu-central-1 to the AWS European Sovereign Cloud already requires provisioning new accounts, networks, and database replication, evaluate whether the effort is comparable to migrating to an EU-owned provider.

Frequently asked questions

Does the AWS European Sovereign Cloud protect against the US CLOUD Act?

The AWS European Sovereign Cloud operates under European legal entities with EU-resident staff and strong technical controls, which lowers the practical risk of routine foreign access. However, because the ultimate parent company is Amazon.com, Inc. (a US corporation), legal experts and European data protection authorities note that it remains within the theoretical reach of the US CLOUD Act. Only providers wholly owned and headquartered outside US jurisdiction avoid the US CLOUD Act entirely.

Can I migrate from AWS Frankfurt to the AWS Sovereign Cloud with one click?

No. The AWS European Sovereign Cloud is a separate logical partition with independent billing, identity (IAM), and network planes. Moving workloads from standard AWS regions requires setting up new sovereign accounts, deploying new infrastructure, and migrating your data across partitions.

Are EU-owned clouds reliable enough for production SaaS workloads?

Yes, provided you choose the right provider and architecture for your needs. Providers such as UpCloud, Scaleway, OVHcloud, Exoscale, and STACKIT offer multi-zone availability, SLA-backed managed Kubernetes and relational databases, ISO 27001 certifications, and high-performance NVMe storage suitable for demanding production SaaS applications.

What happens to AWS data egress fees if we move to an EU provider?

Under Article 29 of the EU Data Act, cloud providers can only pass on the actual cost of switching until 12 January 2027, and from 12 January 2027 onward, all switching charges—including data egress fees when migrating to a new cloud provider—are prohibited by EU law.

Sources

• Regulation (EU) 2023/2854 — The EU Data Act (EUR-Lex)
• Regulation (EU) 2022/2554 — Digital Operational Resilience Act (DORA) (EUR-Lex)
• AWS European Sovereign Cloud Official Page (Amazon Web Services)
• Cybersecurity Certification Framework (ENISA)

---

Drafted with AI assistance and fact-checked by the MoveInfra team. The original, kept up to date, is at moveinfra.eu. Free tools for pricing a move to an EU cloud: moveinfra.eu/tools.