AWS’s second cloud Region in Germany is in Brandenburg, but it is not a conventional counterpart to its Frankfurt Region. It is the first Region of the AWS European Sovereign Cloud, a separate cloud offering that AWS announced as generally available on January 15, 2026. Frankfurt, code eu-central-1, remains AWS’s established German Region.
What AWS added in Germany
The new Region is in Brandenburg and belongs to the AWS European Sovereign Cloud. AWS describes the sovereign cloud as a separate offering that operates independently from its existing Regions. It is therefore distinct from Europe (Frankfurt), the earlier German Region.
AWS announced that Frankfurt opened on October 23, 2014, and called it the company’s second Region in the European Union at that time, after Ireland. The chronology explains the two different “second Region” descriptions: Frankfurt was second in the EU in 2014; Brandenburg is the second AWS cloud Region located in Germany in AWS’s current overview, and the first in the European Sovereign Cloud.
How the sovereign cloud differs from Frankfurt
AWS says its European Sovereign Cloud is physically and logically separate from other AWS Regions. AWS also says it is operated exclusively by EU residents located in the EU and designed to keep operating during a communications disruption with the rest of the world. These are AWS’s descriptions of its design and operating model.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
AWS says customer-created metadata—including roles, permissions, resource labels, and configurations—remains in the EU, alongside sovereign identity and access management (IAM), billing, and usage-metering systems. That is a description of AWS’s service design, not a blanket determination that a customer meets every legal requirement or has no remaining legal exposure.
Frankfurt is not thereby established as unsuitable for sovereignty-sensitive workloads. AWS says its six existing EU Regions are sovereign-by-design; it positions the separate European Sovereign Cloud for organizations with more stringent sovereignty and operational-autonomy needs.
Rank #2
Frankfurt and Brandenburg at a glance
| Question | Europe (Frankfurt) | AWS European Sovereign Cloud (Brandenburg) |
|---|---|---|
| Role | AWS’s established German Region; launched in 2014. | First Region of the separate AWS European Sovereign Cloud; generally available January 15, 2026. |
| Region or location detail | Region code eu-central-1. |
Located in Brandenburg, Germany; a Region code is not stated in the cited launch materials. |
| Availability Zones | Three, according to AWS’s live Region documentation. | Not stated in the cited launch materials. |
| Operating model | AWS says its existing EU Regions are sovereign-by-design. | AWS says the cloud is physically and logically separate, operated by EU residents in the EU, and independent of existing Regions. |
| Initial service count | Not stated here. | More than 90 services at launch, according to AWS. |
Service availability changes over time, and an initial service count does not establish that a particular service, feature, or capacity is available for a workload today. Check the current AWS service and Region documentation before designing or migrating.
Does a German AWS Region guarantee data sovereignty?
No. A Region’s location is one part of a sovereignty assessment, not a guarantee of compliance with every law or contractual obligation. Customers still need to determine what data and metadata their applications create, which AWS services process or store them, who can administer the environment, what access and support arrangements apply, and which legal and regulatory rules govern the organization and its data.
Recommended Free Tools
Rank #3
The European Sovereign Cloud has additional controls and operating commitments that AWS says are intended to address stringent sovereignty needs. Whether those characteristics meet a specific organization’s requirements depends on the workload, applicable rules, contracts, and the customer’s own configuration and governance.
Which workloads should consider Brandenburg?
Organizations in government or regulated sectors may want to assess Brandenburg when their requirements call for EU-based operations, separation from AWS’s existing Regions, or additional operational autonomy. The Region’s location alone is not enough to make that choice: a team must also confirm that the services and architecture it needs are available and suitable.
- Start with the requirement: Identify whether the issue is data location, customer-created metadata, operational control, continuity, or a combination.
- Map the workload: List the AWS services, integrations, data flows, administrators, and support dependencies the application actually uses.
- Check current availability: Confirm the required services, features, and capacity in the target Region using live AWS documentation.
- Assess migration and cost: Model architecture changes, latency for users and connected systems, migration effort, and workload-specific pricing. The launch materials do not establish which Region will be cheaper for a given workload.
- Validate the legal position: Have the organization’s legal, security, and compliance teams assess the relevant laws, contracts, and controls rather than treating Region selection as a compliance verdict.
What AWS has announced beyond Brandenburg
At launch, AWS said the European Sovereign Cloud offered more than 90 services and announced sovereign Local Zones planned for Belgium, the Netherlands, and Portugal. Those locations were plans in the launch announcement; check AWS’s current materials to confirm whether they have since opened and what they offer.
AWS also identifies Dedicated Local Zones, AI Factories, and Outposts as options for customers seeking different location or isolation arrangements. These are distinct deployment choices, not substitutes that can be assumed to provide the same architecture or operating model as the Brandenburg Region.
Best Value
Investment figures are company estimates
Amazon Web Services announced plans to invest more than €7.8 billion in the European Sovereign Cloud in Germany. Amazon estimated the investment would support an average of 2,800 full-time-equivalent jobs annually and add approximately €17.2 billion to German GDP. These are company-announced plans and estimates, not figures that establish realized investment, jobs, or economic impact.
Quick Recap
Sources and current checks
- AWS Region and Availability Zone documentation lists Frankfurt as
eu-central-1and shows its Availability Zone count. - AWS News Blog: Introducing the AWS European Sovereign Cloud describes the Brandenburg Region and AWS’s stated operating model.
- AWS’s January 2026 availability announcement provides launch details, service count, planned Local Zones, and company estimates.
- AWS’s Europe infrastructure overview provides regional context.
- AWS’s Frankfurt Region page covers the Region’s launch history.
- About Amazon Deutschland’s AWS overview describes AWS’s German Region footprint.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
