keepcalculator

06 Numbers and Powers

AWS European Sovereign Cloud: Public Internet & Other Regions?

Card No. 06·72179 · Updated · Standard formula, shown below

Yes, the AWS European Sovereign Cloud can access the public internet and other AWS regions, but with strict controls and boundaries. It is a separate, independent AWS infrastructure designed for EU customers who need advanced data residency and sovereignty controls, and it operates under specific networking and governance rules that differ from standard AWS regions.

Background: Why a European Sovereign Cloud Exists

The AWS European Sovereign Cloud was announced in 2023 and launched in 2024, with its first region in Germany (planned for 2025). It is a response to EU regulatory demands for data residency, sovereignty, and operational independence from non-EU jurisdictions. Unlike standard AWS regions, which are operated globally, this cloud is designed so that only EU-based AWS employees can control the infrastructure, and metadata is stored only within the EU. It also uses separate billing, support, and service catalogs.

Key differences from standard AWS regions:

  • Independent infrastructure: separate hardware, networking, and control planes.
  • EU-only operations: no remote access from outside the EU for management.
  • Different service availability: not all AWS services are offered initially.
  • Separate billing and support: you must sign up separately.

How Networking Works: Public Internet and Region Access

The sovereign cloud is a full AWS region, so it uses the same networking fundamentals as other AWS regions. You can create VPCs, subnets, internet gateways, NAT gateways, and VPN connections. This means resources can reach the public internet for outbound traffic (e.g., downloading updates, calling external APIs) and can accept inbound traffic if you configure security groups and load balancers.

However, there are important restrictions:

  • No direct peering with standard AWS regions by default. You cannot simply use VPC peering or a transit gateway to connect to a regular region. Instead, you must use public internet or a VPN/IPsec connection.
  • No shared control plane. The sovereign cloud has its own APIs and endpoints, so tools like AWS CLI must be configured with a separate profile.
  • Data transfer between the sovereign cloud and standard regions is treated like internet traffic, not internal AWS traffic, so it is not covered by standard inter-region data transfer pricing.

In practice, you can access other AWS regions via public internet, but you cannot use AWS PrivateLink or VPC endpoints to reach them privately. This is a deliberate design to keep the sovereign cloud isolated.

How to Choose: When to Use the Sovereign Cloud vs. Standard Regions

Choose the AWS European Sovereign Cloud if you have strict data residency requirements, such as public sector, healthcare, or financial services in the EU, and you need to ensure that only EU personnel can access metadata and control planes. It is also suitable if you want to avoid any non-EU legal jurisdiction over your data.

Choose standard AWS regions (like Frankfurt, Ireland, or Paris) if you need full service availability, low-latency access to other AWS services, or you rely on inter-region features like VPC peering, Transit Gateway, or global accelerators. Standard regions also offer more mature service catalogs and easier integration with global AWS services.

Consider a hybrid approach: keep sensitive data in the sovereign cloud and run less sensitive workloads in standard regions, connecting via VPN or public internet. This is common for customers who need both sovereignty and global reach.

Common Problems and Misconceptions

One common misconception is that the sovereign cloud is just a renamed EU region. It is not. It is a separate, isolated infrastructure, so you cannot migrate by simply copying an AMI or using AWS Resource Access Manager. You must redeploy workloads.

Another issue is that not all AWS services are available at launch. For example, services like AWS Lambda, Amazon S3, and EC2 are available, but many advanced services (e.g., Amazon SageMaker, AWS Glue) may be missing or limited. Check the service catalog before planning a migration.

Networking problems often arise because customers assume VPC peering works with standard regions. It does not. You must use public internet or a VPN, which can introduce latency and data transfer costs. Also, IAM roles and policies are separate, so you cannot use your existing IAM roles from standard regions directly.

Costs and Pricing Differences

The sovereign cloud has its own pricing, which may be higher than standard regions due to the additional operational and compliance overhead. There is no consolidated billing with your standard AWS accounts; you get a separate bill. Data transfer costs for traffic between the sovereign cloud and standard regions are charged at internet egress rates, which are typically higher than inter-region rates. Also, some services may have different pricing tiers. You should review the official pricing page for the sovereign cloud before committing.

Safety and Compliance Considerations

From a security perspective, the sovereign cloud uses the same AWS security features (IAM, KMS, CloudTrail) but with EU-only access. This means you must ensure your own employees or contractors are EU-based if they need to manage the infrastructure, because AWS will not grant non-EU access. Compliance-wise, the sovereign cloud is designed to meet EU data protection regulations, including GDPR, but you still need to perform your own compliance assessments. There is no automatic certification for all workloads; you must verify that the services you use meet your specific regulatory obligations.

Also, note that the sovereign cloud does not have the same global edge network (CloudFront) or availability zones as standard regions. It initially launched with three availability zones in one region, and more regions are planned. This means disaster recovery across multiple EU regions may not be possible until more regions are available.

Alternatives to the AWS European Sovereign Cloud

If the sovereign cloud’s limitations are too restrictive, consider alternatives:

  • Use standard AWS EU regions with additional controls like AWS Control Tower, S3 Object Lock, and AWS KMS with custom key stores to meet most residency requirements.
  • Use third-party services like AWS Outposts or VMware Cloud on AWS, which can be deployed on-premises in the EU.
  • Use other cloud providers that offer EU-specific sovereign clouds, such as Microsoft Cloud for Sovereignty or Google Cloud’s EU regions with data residency controls.
  • Use a hybrid model with on-premises infrastructure for the most sensitive data and standard AWS for the rest.

Each option has trade-offs in cost, latency, and compliance, so evaluate based on your specific workload.

Frequently Asked Questions

Can I use VPC peering between the sovereign cloud and a standard AWS region?

No. VPC peering is not supported between the sovereign cloud and standard regions. You must use public internet or a VPN connection, which means traffic goes over the internet and is subject to egress costs.

Is the AWS European Sovereign Cloud available to customers outside the EU?

Yes, but with restrictions. Any customer can sign up, but AWS will only allow EU-based employees to manage the infrastructure. If you are outside the EU, you can still use the cloud, but you must have EU-based staff for operational access.

Do I need a separate AWS account for the sovereign cloud?

Yes. The sovereign cloud uses a separate billing and account structure. You cannot use your existing AWS account or consolidated billing. You must create a new account specifically for the sovereign cloud.

Can I migrate from a standard AWS region to the sovereign cloud?

Yes, but it is not a simple lift-and-shift. You must redeploy your resources, reconfigure IAM, and adjust networking. There is no automated migration tool for cross-cloud moves. You can export data to S3 and then import it, but you must rebuild infrastructure.

What happens to my data if I stop using the sovereign cloud?

You can delete all data before terminating the account. AWS will follow its standard data deletion processes, but because the sovereign cloud is isolated, you must ensure you have exported any data you need before deletion.

Does the sovereign cloud support AWS Marketplace or third-party software?

Initially, the AWS Marketplace is not available. You must install software manually or use bring-your-own-license. Over time, AWS may add marketplace support, but it is not guaranteed.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →