1 Answer
- Newest
- Most votes
- Most comments
2
You have VPC Peering. All Subnets in both VPCs can talk to each other using their Private IP Addresses. Theres nothing that needs doing apart from ensuring theres no ACLs that block traffic, and the security groups allow traffic.
Other thing to check is if your using the AWS DNS Names, enable inbound DNS resolution on the VPC Peering connections otherwise they may resolve to Public IPs.
Relevant content
- AWS OFFICIALUpdated 2 years ago

I would add to this answer that you also need to make sure you added the correct routing entries for each VPC.
Having peering is enough to allow services in VPC A and VPC B to talk to each other as Gary said.
Thanks Gary & Mariano. It worked after I added a route through the peering connection and also allowed the traffic in the security group.
Agree MarianoRD.. I assumed the routing had been setup. Thanks for the Update Blacktulip