When attempting to configure a VPC peering connection between a Virtual Private Cloud (VPC) and a VPC associated with another AWS account, I receive an error message that says the connection "failed due to incorrect VPC-ID, Account ID, or overlapping CIDR range."

This error is encountered when the VPC ID or the account ID of the peering VPC is incorrect or if the Classless Inter-Domain Routing (CIDR) ranges overlap. The message can also appear if the VPCs are not in the same region.

To resolve peering connection errors between VPCs, follow these steps:

  1. Verify that the VPC ID and the account ID of the peering VPC are correct.
  2. Verify that the CIDR ranges of the two VPCs do not overlap.
  3. Ensure that the VPCs you are attempting to establish a peering connection between are in the same region. VPC peering connections cannot be established between VPCs in different regions.

VPC, peering connection, failed, VPC ID, account ID, overlapping, CIDR range


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.