Ted, the cloud engineer at Windyfront Air Conditioning, has been approached by one of the application teams. They would like to implement a shared services VPC so each of their applications can talk to a central location for these services. After researching, Ted has identified the easiest method to achieve their requirements is to configure VPC peering between the VPCs.
In this lab, you will configure VPC peering between two VPCs.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Configure VPC Peering between VPC 1 and VPC 2
Configure VPC peering between VPC 1 (FirstVPC) and VPC 2 (SecondVPC). The IP address ranges of these VPCs are:
FirstVPC =
10.0.0.0/16SecondVPC =
10.1.0.0/16
Modify the private route table in each VPC to include a route for the peered VPC.
- Enable Fleet Manager in AWS Systems Manager
Log in to AWS Systems Manager > Fleet Manager, and select Get Started.
Reboot all EC2 instances, and check Fleet Manager for their registration.
- Ping Connectivity Test
- Log in to
EC2Instance1and pingEC2Instance2to confirm peering connection configuration.
Note: Check the credentials section for the EC2 instances’ assigned IPs.
- Log in to
