Vpc Peering Failed

Local vpc is down forwarding via vpc peer link vpc domain id.

Vpc peering failed. Review the following settings as you create your vpc peering connection with a vpc in another aws account. During this state the request cannot be accepted. To find your lightsail vpc in the aws management console go to your amazon vpc dashboard.

If the peering connection fails try to enable vpc peering again. If the vpcs have overlapping ipv4 cidr blocks or if the account id and vpc id are incorrect or do not correspond with each other the status of the vpc peering connection immediately goes to failed. But when i do so i get the error.

Peer link is down vpc keep alive status. The connection failed due to incorrect vpc id account id or overlapping cidr range. In the future we plan to add the ability for users to select from existing vpcs but i don t have a delivery date for that feature addition.

The rejected vpc peering connection remains visible to the owner of the requester vpc for 2 days and visible to the owner of the accepter vpc for 2 hours. Consistency check not performed. To request a vpc peering connection with a vpc in another account in the same region.

The failed vpc peering connection remains visible to the requester for 2 hours. The vpc consistency check cannot be performed when the peer link is lost. If you re creating a vpc peering connection between vpcs in different accounts then use the peerrolearn property to pass your cross account iam role from your accepter account in your aws cloudformation template.

Hello i ve created an internal ticket to investigate why you re not able to create the default vpc. When you disable vpcs on a secondary vpc switch because of a peer link failure and then the primary vpc switch fails the secondary switch reenables the vpcs. Failed per vlan consistency status.