AWS Builder Center
Connectivity patterns between AWS European Sovereign Cloud and AWS commercial partition

Connectivity patterns between AWS European Sovereign Cloud and AWS commercial partition

As European organizations adopt the AWS European Sovereign Cloud to meet stringent data residency, sovereignty, and compliance requirements, many need to maintain secure connectivity with their existing workloads in the AWS commercial partition. This blog explores architectural patterns and best practices for establishing hybrid connectivity between these two isolated partitions while maintaining compliance boundaries.

AWS European Sovereign Cloud is architected with strong isolation (both physically and logically) from other AWS partitions for sovereignty and compliance. For this reason, AWS services used to privately interconnect VPC-hosted resources within the same partition - such as AWS PrivateLink, Amazon VPC peering, or AWS Transit Gateway peering - cannot span from AWS European Sovereign Cloud to commercial Regions by design. In conversations with customers, we've found that there may be use cases where they must interconnect both partitions. In some cases, they host workloads in both partitions for cost optimization or even  resilliency  purposes while meeting security demands. For example, there are single data stores (such as Active Directory for identity) that need to be replicated between partitions. Additionally, some customers need to consume a software as a service (SaaS) offering (AWS or third-party) built in one of the two partitions while their workload exists in the other. In other cases, they are looking to establish connectivity between the partitions for orchestration or data transfer purposes.
In this post, we will highlight four connectivity patterns customers can use to interconnect VPC-hosted systems cross-partition. The illustrations below use AWS Region Frankfurt (eu-central-1) as an example.
Note that in patterns 1, 2, and 4, traffic will stay on the AWS backbone network and will not traverse the public internet. Per the  VPC FAQ , when using public IP addresses, all communication between instances and services hosted in AWS use AWS's private network. Packets that originate from the AWS network with a destination on the AWS network stay on the AWS global network, except traffic to or from AWS China Regions. In addition, all data flowing across the AWS global network that interconnects our data centers and Regions is automatically encrypted at the physical layer before it leaves our secured facilities. Additional encryption layers exist as well; for example, all VPC cross-region peering traffic, and customer or service-to-service Transport Layer Security (TLS) connections.

Pattern 1: Connectivity over the internet using native TLS encryption


Figure 1. Architectural Diagram of TLS-Encrypted Connections Between Partitions at the Application Layer
If the application is using TLS encryption natively (such as API traffic on https/443), then use  Elastic IP addresses  (EIPs) to communicate. This is the most performant and operationally sustainable pattern as you remove the requirement to maintain and configure  Amazon Elastic Compute Cloud  (Amazon EC2) based virtual private network (VPN) appliances, and the  Direct Connect gateway  (DXGW). As part of the  shared responsibility model , you are responsible for ensuring encryption-in-transit modules and algorithms meet your compliance needs. This option does not provide encryption at the network transport layer. This is a common architecture used by customers to move for example data between environments using  AWS DataSync .

Pattern 2: Connectivity using IPSec AWS Site-to-Site VPN over the internet


Figure 2. Architectural Diagram of a Site-to-Site VPN Between AWS Partitions Using Transit Gateway and an EC2-Based Appliance
 AWS Site-to-Site VPN  is a managed service that uses Internet Protocol security (IPSec) to create encrypted tunnels. IPSec-based VPN is a common approach for enabling multi-partition private connectivity because it provides encryption-in-transit for those systems that cannot support encryption at the application layer or be exposed via an internet gateway. Although it is isolated, AWS European Sovereign Cloud is not an air-gapped Region. It’s connected to the internet, which allows you to set up point-to-point connections. AWS does not currently support VPNs between gateways (virtual private gateways, Transit Gateways). In order to implement a tunnel, you need to use third-party virtual appliances.
In this scenario, we launch the virtual appliance in AWS European Sovereign Cloud, but the appliance itself can be deployed in either partition. The maximum bandwidth per VPN tunnel is 1.25 gigabits pers second (Gbps). For higher performance, enable equal-cost multipath (ECMP) to aggregate throughput across VPN connections and allow scalability beyond the default maximum limit of 1.25 Gbps per tunnel. This architecture does introduce Transit Gateway data processing charges, Transit Gateway attachment charges, and  Amazon EC2  variable cost based on the size and licensing agreement you have with your specific vendor. If you wish to learn more about variations to this architecture, refer to the  AWS VPC Connectivity Options whitepaper .

Pattern 3: Connectivity through on-premises customer gateway / service provider


Figure 3. Architectural Diagram of Connecting via an On-Premises Gateway Using Direct Connect Gateway
In this scenario, we have separate  AWS Direct Connect  transit virtual interfaces (VIFs) or VPN tunnels to a VPC in each Region (AWS European Sovereign Cloud and commercial). This is a hub and spoke connectivity model where filtering/control needs to occur on premises and pass through some type of firewall-based devices hosted in on-premises data centers. To establish private connectivity back to on premises, use an IPSec VPN over the internet or Direct Connect for more performant, resilient connectivity. Keep in mind that since the traffic is getting hairpinned via the on-premises network, it will add latency, data transfer out (DTO) cost, and Transit Gateway data transfer charges. In the preceding Figure 3, the dashed orange line represents the traffic flows that are permitted. The Direct Connect gateway represented here is a global construct (not tied to a specific Region), allowing you to connect to any AWS Region. It also allows north-south connectivity and does not enable Border Gateway Protocol (BGP) prefix propagation between associated Transit Gateways or virtual private gateways associated with the same Direct Connect gateway on the same virtual interface. This indirectly denies east-west traffic between associations, except when a supernet is advertised across two or more VPCs, which have their attached virtual private gateways associated to the same Direct Connect gateway and on the same virtual interface. In this case, VPCs can communicate with each other through the Direct Connect endpoint. For example, if you advertise a supernet (for example, 10.0.0.0/8 or 0.0.0.0/0) that overlaps with the VPCs attached to a Direct Connect gateway (for example, 10.0.0.0/24 and 10.0.1.0/24), and on the same virtual interface, then from your on-premises network, the VPCs can communicate with each other. From then, your on-premises network, and VPCs can communicate with each other.
The "on-premises network" could also be substituted by a service provider taking care of the cross-connect. Please work with one of our  AWS Partner Network (APN) partners , who can provide these connectivity options.
For reference, AWS European Sovereign Cloud is connected to the following Direct Connect locations (DX Pop) at 100G max. bandwidth:
  • Atlas Edge BER001, Berlin
  • IPB GmbH, Berlin

Figure 4. AWS Direct Connect Locations for AWS European Sovereign Cloud (Germany)
Note if you are using a supernet to connect both partitions without redundancy on your Direct Connect connections, losing a single connection will introduce a single point of failure. To learn more about Direct Connect resilience best practices, please visit  Direct Connect Resiliency Recommendations .

Pattern 4: Connectivity using transit VPC and Transit Gateway Connect attachment


Figure 5: Architectural diagram using transit VPCs
Customers can also use the transit VPC solution. Within the transit VPC, we have redundant third-party virtual appliances in different Availability Zones for high availability purposes. We then connect to Transit Gateway using the Direct Connect attachments to allow BGP over Generic Routing Encapsulation (GRE) tunnels. Note that while GRE provides simplified connectivity with Transit Gateway, it does not provide encryption. If you need to extend encryption, you can use IPSec VPN between the virtual appliances and Transit Gateway instead of GRE (as described in pattern 2 earlier).

Conclusion

In this post, we discussed some common architecture patterns customers can use to connect AWS European Sovereign Cloud and standard AWS Regions. While these architectures allow you to communicate across partition, as part of the  shared responsibility model , you or your designated service provider are responsible for data movement and traffic encryption. For questions do not hesitate to contact us!
Note: Article based on this  blog . Credits to Eric Vasquez, Tushar Jagdale, Vincent Cabosart for their support!
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article