How to do VPC Peering in another region?

Table of contents

Reading Time: 4 minutes

VPC Peering:-

Inter-region VPC peering is the peering between VPCs that are situated in several AWS regions. Data transport can be up by using a VPC peering connection. To route traffic using private IPv4/IPv6 addresses, two VPCs must create a networking link known as a VPC peering relationship to connect to each other. Instances can connect with one another through the usage of a VPC just as they were on the same network. You can connect a VPC in your own account with a VPC in another AWS account using a VPC peering arrangement. VPCs might be found all throughout (also known as an inter-region VPC peering connection).

To distribute resources from one of your VPCs to other VPCs, you can also use a VPC peering connection.

Route Table:-

A destination and an objective are provided for each route in a table. For example, to enable your subnet to access the internet through an internet gateway, add the following route to your subnet route table and The route’s final destination is 0.0.0.0/0, which stands for all IPv4 addresses. The target is the internet gateway that is connected to your VPC.

INTERNET Gateway:-

You can use your personal computer as an internet gateway to connect to an EC2 instance in AWS. For traffic that can be routed via the internet, an internet gateway is utilized as a target in your VPC route tables. Network address translation is also done by the internet gateway for IPv4 connections.

STEPS:-

Select two VPCs from two distinct regions (for ex:- One in Tokyo and one in Mumbai).

TOKYO

Establish a VPC in the Tokyo area.
Make a Subnet, and in it select CIDR.
Make sure to create one Internet gateway and connect it to your VPC.
Make a single route table (make sure you have added the subnet and routes in it).

Mumbai

Establish a VPC in the Mumbai area.
Make a Subnet, and in it select CIDR.
A single Internet gateway must be built and connected to your VPC.
Make a single route table (make sure you have added the subnet and routes in it).

When you have finished setting up the VPC in both regions, build an EC2 instance for each to establish a connection between them.

Tokyo:

Make a VPC and add 10.0.0.0/16 to the Ipv4 CIDR.

Route table:

Create the route table, make any necessary edits to the subnet associations, add the subnet you generated for your virtual private server, and then click “Save.” Go to routes after that and edit the routes table there.

Peering Request from Tokyo To Mumbai:-Go to Peering Connection:-

Go to PEERING Connections:-

Give a name to the peering connection (VPC-Tokyo-Mumbai).
There will be 2 types of VPC
- Requestor ID – The one who will request for peering request to private IP addresses.
- Acceptor ID – The one who will accept the peering request to private IP addresses.
Click on Another Region
Now go to service:
- Click on Vpc of Your Mumbai ID.
- Select and copy the VPC ID.
- Paste in the acceptor ID to accept peering from another region.

Go to the Mumbai region:
- Search peering connections
- Click on the request
- Select accept

Mumbai:-

Create a second VPC in a different area and add the 192.168.0.0/16 Ipv4 CIDR for that second VPC.

Route table:–

Peering Accept from Mumbai to Tokyo:-

As soon as it is approved, it will become green, as seen in the Tokyo region above, and its states will change to ACTIVE.

EC2:-

Create an EC2 instance
- Select the Machine.
- Go into the network part and select the particular region.
- Choose the subnet ACCording to your VPC.
- Enable the Auto-assign Public IP.
- Review and launch the Ec2 instance in both regions and connect them to your terminal.