AWS 5 VPC Peering

We create 3 VPC's in the Same Region but different Availability Zones



VPC peering is not  Transitive.
It is only 1 to 1




If we want communication from  Yelow to  RED, we need  to enable  VPC peering over there.








After we create the VPC peering connections, we need to modify the Route Tables
We can restrict the Address space in the routing table.
Specifying the Address range, that needs to have the ip space open.

The routing tables of both the VPC's should be edited to show the route.

The entry in the routing table is nothing but the VPC peering connection Name, that has the entries of both the  VPC's that are participating in the transaction.















We use VPC peering to manage multiple VPC's  instead of having a Jump host in each VPC.






We control the Traffic by editing the Security Groups to particular ports

Windows , we limit to TCP3389
Linux, we limit  to  TCP22