Amazon VPCs are virtually isolated networks where you can launch resources such as EC2 instances. Amazon VPC peering connections can be used to connect two VPCs and allow them to route traffic between them using IPv4 and IPv6 addresses.
In this Cloud Lab, you will first create two VPCs: a backend VPC in the US East 1 (N. Virginia) region and a frontend VPC in the US East 2 (Ohio) region. You’ll then launch EC2 instances in the private and public subnet of the backend and frontend VPC. Your backend instance will be in a private subnet, so you’ll create an EC2 Instance Connect Endpoint to connect to the EC2 terminal. You’ll then deploy your front- and back-end applications, but they won’t be able to communicate because they’re in different VPCs. Next, you’ll create a VPC peering connection between your VPCs and configure their route tables to ensure traffic can flow between them.
After completing this Cloud Lab, you’ll have an understanding of VPC peering connections and be able to create inter-region VPC peering connections. The following is the high-level architecture diagram of the infrastructure you’ll create in this Cloud Lab:
