Is an AWS region in Frankfurt enough for GDPR and data sovereignty?
An AWS Frankfurt region can meet GDPR rules with proper safeguards, but it gives you data residency, not true European data sovereignty.
Yes, an AWS region in Frankfurt (eu-central-1) is usually enough for GDPR compliance when paired with the right contracts and technical safeguards, because the GDPR does not strictly require personal data to stay inside the European Union. However, hosting in Frankfurt does not give you European data sovereignty. Selecting a German data center gives you data residency, meaning your files sit on servers in Hesse, but the infrastructure is still ultimately owned and controlled by Amazon, a US corporation subject to extraterritorial US laws such as the CLOUD Act. Note: This article is for informational purposes for technical and business leaders and is not legal advice.
Key takeaways
- Data residency, GDPR compliance, and data sovereignty are three different things. Putting servers in Frankfurt solves residency and helps with GDPR, but does not change which country’s laws govern the cloud provider.
- GDPR is about protection, not just geography. Under Chapter V of the GDPR, personal data can be processed by US-owned providers or transferred outside the EEA if valid legal mechanisms—such as the EU-US Data Privacy Framework (DPF) or Standard Contractual Clauses (SCCs)—are in place.
- The EU-US Data Privacy Framework is valid as of 2026, but under legal scrutiny. Following the EU General Court’s dismissal of the Latombe challenge in September 2025, an appeal (
Case C-703/25 P) is pending before the European Court of Justice, alongside questions over the independence of US oversight bodies. - US law follows the parent company, not the server rack. Under the US CLOUD Act, US authorities can compel a US service provider to produce data in its “possession, custody, or control,” regardless of whether that data is stored in Virginia, Frankfurt, or the AWS European Sovereign Cloud.
- Not every company needs an EU-owned cloud. Standard B2B SaaS startups often do fine in AWS Frankfurt, while companies selling to European public sector bodies, healthcare institutions, defense, or strict financial enterprises increasingly benefit from EU-owned infrastructure.
Three terms that get mixed up: residency, compliance, and sovereignty
When European customers or auditors ask where your data is hosted, “AWS Frankfurt” is the most common answer. To know whether that answer is sufficient for your business, you have to separate three concepts that vendors often blur together.
1. Data residency (Where the disks live)
Data residency is simply the physical and geographic location where your data is stored and processed. When you deploy an RDS database or an S3 bucket in AWS eu-central-1 (Frankfurt), AWS commits not to move your customer content out of that region without your consent or instruction.
Residency solves latency for Central European users and satisfies basic contractual clauses that state “Customer data must be stored within the European Economic Area (EEA).”
2. GDPR compliance (How personal data is protected)
The General Data Protection Regulation (Regulation (EU) 2016/679) does not contain a blanket ban on non-EU cloud providers, nor does it mandate that all data remain inside EU borders. Instead, GDPR requires that:
- You have a lawful basis to process personal data and a Data Processing Addendum (DPA) with your processor under Article 28.
- You implement appropriate technical and organizational security measures under Article 32.
- If personal data is transferred outside the EEA—including remote access by support engineers in Seattle or Bangalore, or routing through global control planes and billing systems—that transfer must comply with Chapter V of the GDPR (Articles 44 to 49).
Because AWS offers a GDPR-compliant DPA, keeps application data in Frankfurt, and certifies under the EU-US Data Privacy Framework, using AWS Frankfurt can be GDPR compliant for most commercial workloads.
3. Data sovereignty (Who has ultimate legal authority)
Data sovereignty is about jurisdiction and control. It asks a blunt question: if a foreign government demands access to your data, or orders your provider to suspend your account, whose law wins?
True European sovereignty means the cloud provider is headquartered in Europe, incorporated under European law, operated by staff in Europe, and free from parent companies in third countries whose laws claim extraterritorial reach. An American hyperscaler operating a data center in Germany provides European data residency, not European sovereignty.
| Requirement | AWS Standard Region (eu-central-1 Frankfurt) |
AWS European Sovereign Cloud (Brandenburg) | EU-Owned Cloud (e.g., UpCloud, Scaleway, OVHcloud, Hetzner) |
|---|---|---|---|
| Physical server location | Germany (EU) | Germany (EU) | EU Member States |
| Control plane & metadata | Integrated with global AWS network | Logically isolated in the EU | Inside the EU |
| Operations & support staff | Global workforce | EU residents/citizens only | Primarily EU-based workforce |
| Ultimate parent company | Amazon.com, Inc. (US) | Amazon.com, Inc. (US) | European parent company (Finland, France, Germany) |
| Subject to US CLOUD Act? | Yes | Yes (via US ownership) | No (assuming no considerable US nexus) |
| Typical cost level | Standard hyperscaler pricing | Premium over standard AWS | Usually 30% to 60% lower on compute and egress |
The jurisdiction gap: Why Frankfurt is still within reach of US law
The core tension between European privacy law and US cloud providers comes down to a conflict of laws.
In 2018, the United States enacted the Clarifying Lawful Overseas Use of Data Act (CLOUD Act), which amended the Stored Communications Act (18 U.S.C. § 2713). The statute states that a provider of electronic communication or remote computing services must comply with valid US obligations to preserve, backup, or disclose the contents of a wire or electronic communication and any record or other information pertaining to a customer within the provider’s “possession, custody, or control,” regardless of whether that communication or record is located within or outside of the United States.
At the same time, Article 48 of the GDPR states that any judgment of a court or tribunal and any decision of an administrative authority of a third country requiring a controller or processor to transfer or disclose personal data may only be recognized or enforceable if based on an international agreement, such as a mutual legal assistance treaty (MLAT).
In daily practice, AWS publishes transparency reports showing that it challenges overbroad requests, redirects government agencies to contact the enterprise customer directly, and discloses enterprise content outside the US only in rare cases. If your threat model is routine commercial risk, the statistical probability of a US law enforcement warrant targeting your Frankfurt PostgreSQL database is very low.
However, for European public sector buyers, banks, healthcare providers, and defense contractors, procurement decisions are based on legal exposure rather than historical averages. If a US court orders a US parent company to hand over data or restrict service, a subsidiary in Luxembourg or Germany faces a direct conflict between US federal law and EU law.
What about the AWS European Sovereign Cloud?
In January 2026, AWS launched the AWS European Sovereign Cloud in Brandenburg, Germany. It is a separate partition from standard AWS regions, with its own billing, identity management, and European certificate authority, operated exclusively by EU residents under a dedicated European corporate structure.
This solves two practical problems that standard AWS Frankfurt had:
- Metadata and control planes: In standard regions, account metadata, IAM configurations, and billing records can touch global systems. In the Sovereign Cloud, metadata stays in the EU.
- Operational autonomy: US-based engineers have no access to the Sovereign Cloud partition, reducing the risk that day-to-day support triggers a third-country data transfer.
Yet two caveats remain. First, because it is a separate partition, moving from eu-central-1 to the AWS European Sovereign Cloud requires migrating your accounts and workloads, and the sovereign region carries a price premium over standard Frankfurt pricing. Second, the ultimate owner of the infrastructure remains Amazon.com, Inc., a US company. While operational isolation makes direct data extraction without EU staff involvement technically difficult, it does not eliminate the legal jurisdiction of the United States over the parent corporation.
The EU-US Data Privacy Framework in 2026: Valid, but fragile
Even when you host in AWS Frankfurt, using a US hyperscaler almost always involves some international data transfer mechanisms—whether for enterprise support cases, global CDN routing, or third-party sub-processors.
Historically, European companies relied on Safe Harbor (struck down by the European Court of Justice in Schrems I in 2015) and then Privacy Shield (struck down in Schrems II in July 2020). In July 2023, the European Commission adopted its third adequacy decision, creating the EU-US Data Privacy Framework (DPF) (Implementing Decision (EU) 2023/1795), backed by US Executive Order 14086.
As of late 2026, here is where the legal foundation stands:
- The DPF is currently in force: AWS, Google Cloud, and Microsoft Azure are all certified under the DPF. Under Article 45 of the GDPR, transfers to certified US organizations do not require additional transfer tools.
- Pending appeal at the CJEU: French MP Philippe Latombe challenged the DPF before the EU General Court (
Case T-553/23). On September 3, 2025, the General Court dismissed the challenge, ruling that at the time of its decision, the US framework provided essentially equivalent safeguards. However, that ruling was appealed to the Court of Justice of the European Union on October 31, 2025 (Case C-703/25 P), where it remains pending. - Questions over US independent oversight: The 2023 adequacy decision relied heavily on the independence of US oversight bodies, including the Privacy and Civil Liberties Oversight Board (PCLOB), the Data Protection Review Court (DPRC), and the Federal Trade Commission (FTC). Staffing dismissals at the PCLOB in 2025 and the June 2026 US Supreme Court ruling in Trump v. Slaughter (which curtailed statutory removal protections for independent agency commissioners) have raised fresh questions from privacy advocates and data protection authorities about whether the US political safeguards underpinning the DPF still hold as originally assessed by the European Commission.
Because no one can guarantee whether the DPF will survive the next three to five years without a “Schrems III” invalidation, legal teams continue to keep Standard Contractual Clauses (SCCs) and Transfer Impact Assessments (TIAs) in place as a fallback.
Technical safeguards if you stay on AWS Frankfurt
If you decide to keep your infrastructure in AWS Frankfurt, location alone should not be your only defense. Following recommendations issued by the European Data Protection Board (EDPB) after Schrems II, you can strengthen your GDPR posture with technical and organizational measures:
- Verify your DPA and SCCs: Ensure your AWS account has the current AWS GDPR Data Processing Addendum active, which includes Standard Contractual Clauses as a backstop if the DPF is ever invalidated.
- Lock down regions with AWS Organizations: Apply Service Control Policies (SCPs) to block the creation of resources outside EU regions (
eu-central-1,eu-west-1,eu-north-1, etc.) so engineers cannot accidentally spin up a test database inus-east-1. - Keep support and logging local: Avoid putting cleartext personal identifiable information (PII) into AWS Support tickets, IAM role names, or resource tags, since global support staff and billing systems may read them.
- Evaluate your encryption key model: Standard AWS KMS keys are managed within AWS infrastructure. If you require strict technical protection against provider access, the EDPB emphasizes encryption where keys are held solely under the customer’s control in the EEA (such as an external HSM or client-side encryption before upload)—though this comes with significant operational complexity and breaks many managed cloud features.
Checklist: Is AWS Frankfurt enough, or is an EU-owned cloud worth it?
Moving clouds takes engineering effort, even when automated. For some companies, staying in Frankfurt is the pragmatic choice; for others, moving to an EU-owned provider (such as UpCloud, Scaleway, OVHcloud, Hetzner, IONOS, or STACKIT) directly removes commercial and regulatory friction.
Staying on AWS Frankfurt is usually fine when:
- You build standard B2B or B2C software and your customers’ security questionnaires only ask that data is hosted in an EU region with a valid DPA.
- You rely heavily on proprietary AWS services—such as DynamoDB, Redshift, or complex Step Functions—where refactoring would take months away from core product development.
- You have an active AWS promotional credit grant covering your infrastructure bill for the next 12 months.
- You are not subject to strict sector regulations regarding third-country cloud concentration or public procurement rules.
Moving to an EU-owned cloud is worth it when:
- You sell to the European public sector, healthcare, or defense. Public tenders in Germany, France, the Nordics, and the Benelux increasingly award points for—or explicitly require—providers free from non-EU extraterritorial laws.
- Enterprise procurement deals are stalling in legal review. If your sales cycle drags out by months because a German Mittelstand customer or French bank demands a 40-page Transfer Impact Assessment for every US sub-processor, using an EU-owned host cuts the Chapter V transfer debate out of the conversation.
- You fall under DORA (Regulation (EU) 2022/2554) or NIS2. Since January 17, 2025, DORA requires financial entities and their critical ICT providers to maintain tested exit strategies and manage third-country concentration risks.
- Your architecture uses standard building blocks. If your stack runs on Linux VMs, Kubernetes, PostgreSQL/MySQL, Redis, and S3-compatible object storage, every component has a direct drop-in equivalent on EU clouds (you can check service parity on our free EU Cloud Service Map).
- You want to cut your monthly cloud bill alongside your legal risk. Standard compute, managed databases, and bandwidth on EU-owned providers are substantially cheaper than AWS Frankfurt, and under Article 29 of the EU Data Act (Regulation (EU) 2023/2854), data egress charges for switching cloud providers are capped at cost until January 12, 2027, and banned entirely from January 12, 2027 onward. You can see what your current setup would cost on European providers using our browser-based Cloud Bill Analyzer, or read how exit fee waivers work in our EU Data Act switching fees guide.
Frequently asked questions
Does GDPR require all personal data to stay inside the EU?
No. GDPR governs the protection of personal data belonging to individuals in the EEA, not its mandatory physical localization. Data can be processed outside the EEA—or by non-EU companies inside the EEA—provided you comply with the conditions in Chapter V of the GDPR, such as relying on an European Commission adequacy decision or Standard Contractual Clauses with appropriate safeguards.
Does encrypting my data with AWS KMS in Frankfurt protect me from the US CLOUD Act?
Standard server-side encryption using AWS Key Management Service (SSE-KMS) protects against physical disk theft and unauthorized external access, and AWS provides strong architectural controls around key usage. However, because AWS manages the KMS service, keys managed inside the cloud environment are generally not considered by EU data protection authorities to be under the exclusive control of the customer unless you manage keys externally (Hold Your Own Key) and encrypt data before it reaches the cloud provider.
Is the AWS European Sovereign Cloud immune to the US CLOUD Act?
The AWS European Sovereign Cloud provides strong operational isolation: it is physically and logically separate from global AWS regions, keeps metadata in Europe, and is operated solely by EU residents. However, because the infrastructure is ultimately owned by Amazon.com, Inc., a US corporation, legal scholars and European regulators note that it does not completely eliminate the extraterritorial reach of US law over the parent company.
How hard is it to move from AWS Frankfurt to an EU-owned cloud?
If your application relies on open-source standards—such as Docker or Kubernetes, PostgreSQL or MySQL, Redis, and S3-compatible object storage—moving is primarily an infrastructure-as-code and database replication task rather than an application rewrite. Under the EU Data Act and AWS’s own switching policies, data egress fees for leaving the platform can also be waived when following formal exit procedures.
How MoveInfra can help
If you decide that an EU-owned cloud makes more sense for your customers and your budget than staying in AWS Frankfurt, MoveInfra moves your infrastructure from AWS, Google Cloud, Azure, or DigitalOcean to European providers such as UpCloud, Scaleway, Hetzner, and OVHcloud for a fixed price. We rebuild your network and infrastructure as Terraform code, keep your databases and object storage in live sync, update your CI/CD pipelines with your team, and switch DNS over with a 30-day rollback window after replication lag drops below five seconds.
Sources
- Regulation (EU) 2016/679 (General Data Protection Regulation) — EUR-Lex
- Commission Implementing Decision (EU) 2023/1795 on the adequate level of protection of personal data under the EU-US Data Privacy Framework — EUR-Lex
- Regulation (EU) 2023/2854 (EU Data Act) — EUR-Lex
- EU-U.S. Data Privacy Framework Program — Official Participant List and Overview
- AWS GDPR Center — Amazon Web Services Compliance