How do I troubleshoot problems establishing communication over VPC peering?

Short description

VPC peering network connectivity failures might occur due to incorrect or missing route tables, firewall rules, or DNS (if applicable). To route traffic between VPCs in a peering connection with private IP addresses, the VPCs must be able to communicate with each other. You must allow the VPCs to communicate as if they are in the same network.

Resolution

• Verify that the VPC peering connection is in the Active state.
• Update your route tables for your VPC peering connection. Verify that the correct routes exist for connections to the IP address range of your peered VPCs through the appropriate peering ID.
• Verify that an ALLOW rule exists in the network access control (network ACL) table for the required traffic.
• Verify that the security group rules allow network traffic between the peered VPCs.
• To use a domain name to reach a destination in the peer VPC, see Why can't I resolve domain names over my VPC peering connection?
• To verify that a source or destination doesn't reject the required traffic, use VPC Flow Logs. This rejection might occur due to the missing rules under security groups or network ACLs of the source or destination.

Related information

VPC peering basics