Exam Objective Virtual Private Cloud (VPC), is an isolated region that hosts AWS resources. The topic “VPC Peering”, as described in the AWS Blueprint, focuses on the Design and Implementation AWS Networks. Start AWS Certified Advanced Networking Specialty-Free Test Now What is VPC peering? VPC peering allows for two VPC’s to be connected so that they can communicate with one another. VPC’s can be connected to multiple accounts. However, they must be located in the same area. Let’s see how VPC Peering works. Implementation of VPC peering Let’s look at the steps below to learn how VPC peering can be implemented. First, create 2 VPCs before peering them together. Step 1: Log in to your AWS Console. Step 1) Log into your AWS Console. Step 2) Create a VPC with a nametag of VPCA, CIDR Block of 10.0.0.0/16. Step 3) Create another VPC using a nametag of VPCB, CIDR Block of 18.104.22.168/16. Step 4) Now let us create subnets within each of these VPC’s. Let’s create a SubnetA Name tag in VPCA with a CIDR Block of 22.214.171.124/24. Step 5) Now let’s create a Subnet in VPCB. Let’s create a subnet in VPCA with a SubnetB Name tag and a CIDR Block of 10.0.1.0/24. Also read: How to improve connectivity and secure your VPC resources. Step 6: Now we will launch instances in both subnets. Make sure both subnets have Public IP addresses. Make sure that Auto-assign IP settings are enabled for both subnets. Step 7: Now let’s create a VPC peering connection between the VPC’s. On the left, click on Peering connections Step 8. Give the peering connection a name tag. Next, enter the VPCA of the requester. Then select the other VPC that you wish to peer with and click on Create Peering Connection. Step 9: Now, you will see that the VPC Peering Connection is in the Pending Acceptance Status. Click on Actions->Accept request and then accept the request. Step 10: We need to modify both the VPC route tables to ensure that communication can flow through the VPC Peering link. In the Route Table for VPCB, we must add the destination for VPC Peering as the target and the destination for VPC CIDR of VPCA as the destination. The same process is required for the Route Table of VPC A. If you wish to connect to any instance in the VPC via internet, ensure that the internet gateway has been attached to the Route tableau. Step 11) Now, it’s time for each VPC to launch its instances. Now we have two servers. ServerA was launched in VPCA, and ServerB was launched in VPCB. We will now connect to ServerA in VPCA to ping ServerB. ServerB’s private IP is 10.0.1.138. We will use the ping command. Make sure that both instances of the Security Group have the security group changed to allow the ICMP protocol. Once this is done, you can ping ServerB from ServerA. Also read: Introduction to Elastic Network Interface. Important points to remember that transitive VPC peering is not permitted. Let’s suppose you have the following VPC’s peering. We now have VPCA peer to VPCB, and VPCB peer to VPCC. This does not mean that VPCA cannot communicate with VPCC via VPCB. VPCA must establish a VPC Peering connection with VPCC. This is as shown below. To help you grow your professional career, we provide the best and most high-quality preparation materials. The content at Whizlabs is written by industry experts who are passionate about cloud computing. We are constantly expanding our cloud expert community.