1 Answer
- Newest
- Most votes
- Most comments
1
Verify that the route table is configured correctly for both VPCs.
Also, make sure that the security group configured on the EC2 allows communication from the connection source.
As per the following document, VPCs that are VPC peering can refer to each other's security groups.
https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-security-groups.html
Relevant content
- Accepted Answerasked 5 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
To add check NACLs allow traffic between the 2 subnets also