Vpc Peering Limitations
Instances in either vpc can communicate with each other as if they were within the same network.
Vpc peering limitations. Vpc peering limitations vpc peering connection cannot be created between vpcs that have matching or overlapping cidr blocks. Data can be. A inter region peering doesn t support ipv6 b peering vpcs must not have overlapping ip cidr blocks.
Vpc peering does not support transitive peering relationships. A vpc peering connection is a networking connection between two vpcs that enables you to route traffic between them using private ip addresses. Unicast reverse path forwarding in vpc peering connections is not supported.
Vpc peering connections created between vpcs that have overlapping subnet cidr blocks may not take effect. You cannot create a vpc peering connection between vpcs that have matching or overlapping ipv4 or ipv6 cidr blocks. This is actually a good limit to adhere too as often requiring more than 50 peers indicates a design issue in the first place.
You cannot create a vpc peering connection between vpcs in different regions. Amazon always assigns your vpc a unique ipv6 cidr block. This may change in future releases.
You cannot create a vpc peering connection between vpcs in different regions. You cannot have more than one vpc peering connection between the same two vpcs at the same time. Vpc peering allows you to deploy cloud resources in a virtual network that you have defined.
If the vpcs have multiple ipv4 cidr blocks you cannot create a vpc peering connection if any of the cidr blocks overlap regardless of whether you intend to use the vpc peering connection for communication between the non overlapping cidr blocks only. You cannot create a vpc peering connection between vpcs that have matching or overlapping ipv4 or ipv6 cidr blocks. Vpc peering limitations to create a vpc peering connection with another vpc be aware of the following limitations and rules.