How to create VPC PEERING in the same region? Let’s look into the solution in this post. Bobcares offers solutions to your VPC queries as a part of our AWS Support Services.

How to create VPC PEERING in the same region?

A VPC peering is a networking link between two VPCs. Instances can connect with one another as if they were on the same network by using a VPC. Through a VPC peering arrangement, a VPC in your own account or a VPC in another AWS account can be linked.

We can distribute resources from one of the VPCs to other VPCs using a VPC peering connection. The steps to create a VPC peering in same region are as follows:

1. Creating 2 VPCs in the same region

2. Creating 2 subnets in the same region

3. Creating two Gateways and attaching them with the VPC

4. Creating Route Table

Let’s look into the details:

1. Firstly, access the AWS VPC console.

2. Then select ‘Peering connections’ in the navigation pane.

3. Also, select ‘Create peering connection’.

4. Provide the needed details. Then select ‘Create Peering Connection’.

Peering connection name tag: Name of the VPC peering connection.

VPC (Requester): Select the VPC in the account with which we need to create the VPC peering connection.

Under Select another VPC to peer with: Ensure to select My Account and select another of the VPCs.

5. Then hit OK in the confirmation dialog box.

6. Choose Actions, and Accept Request after selecting the VPC peering connection we’ve set up.

7. Select ‘Yes, Accept’ in the confirmation popup box. Choose ‘Modify my route tables now’ to move right to the route tables page, or choose ‘Close’ to do this later. ‘

8. Choose the address type and CIDR.

9. Make a routeing table for both VPCs. Include them in the routing table from the VPC of both machines and add the subnet as well.

10. Establish an Internet gateway and attach them using Vpc so that the State is perceived as being attached.

11. NOW check the DNS settings in the peering connection as there will be a Request VPC and an Acceptor VPC that will send and receive data, respectively.

12. Click on the action and send for ACCEPT REQUEST to submit the request to the acceptor if it is still not accepted.

13. Do not choose the default network for the vpc1 or vpc2 because the subnet will be changed automatically afterward. TURN ON AUTO-ASSIGN PUBLIC IP and CREATE AN ECC2 INSTANCE.

14. Ping the console’s Private IPv4 addresses once it is connected.

15. Ping the second device one more time. Once connected, it will PING the private IPv4 addresses of the second machine.

16. Both result in the ideal Ping performance.

[Searching for a solution to your AWS query? We are just a click away.]

Conclusion

To sum up, our Support team explains the steps to create VPC peering in the same region.