Vpc Peering Between Different Regions

Aws vpc peering across region environment overview.

Vpc peering between different regions. Inter region vpc peering allows vpc resources like ec2 instances rds databases and lambda functions running in different aws regions to communicate with each other using private ip addresses without requiring gateways vpn connections or separate network appliances. As you all know vpc peering is the private connection between two different vpc s. Amazon ec2 now allows peering relationships to be established between virtual private clouds vpcs across different aws regions.

Now that we ve created our vpc s and subnets for each vpc we want to peer our two vpc s with each other so that we have a direct connection between our vpc s so that our ec2 instances from our green account is able to connect with our ec2 instances in our blue account. Aws uses existing vpc infrastructure for peering connections. For this we are connecting two vpc s between tokyo and ohio.

Later aws transit gateway akin to a virtual router provided a more scalable simpler networking solution within a given aws region. Setup vpc peering connection. Go to first vpc 1 mumbai region and copy cidr.

How to create vpc. A vpc peering connection is a networking connection between two vpcs that enables you to route traffic between them privately. Peering connection name tag.

In the mumbai region i have created a vpc with two subnets in a different availability zone. Vpc peering enabled instances in different vpcs to communicate with each other as if they were within the same network. Configure the information as follows and choose create peering connection when you are done.

In the routes paste cidr in the destination which was copied from vpc 1 mumbai region and select peering connection in the target the click on save routes. In this blog we will show you the steps to create aws vpc peering across region environment. Instances in either vpc can communicate with each other as if they are within the same network.