- Newest
- Most votes
- Most comments
Hello,
What you are seeing is expected behavior. It is explained in the VPC FAQ. When the Source and Destination endpoints are both on AWS network then the traffic stays on the AWS backbone network even if you are Pinging Public IP and does not traverse "Public internet" Therefore your ping results via VPC Peering Vs between the Public IPs is same.
** Q. Does traffic go over the internet when two instances communicate using public IP addresses, or when instances communicate with a public AWS service endpoint?**
No. When using public IP addresses, all communication between instances and services hosted in AWS use AWS's private network. Packets that originate from the AWS network with a destination on the AWS network stay on the AWS global network
Hope this helps clarify.
Relevant content
- Accepted Answerasked 7 months ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Just a side comment here: Public IP addressing implies Internet but does not equal it. So a private network (such as the Amazon backbone) can use public IP addressing yet still keep the traffic within private boundaries. Public IP addresses are necessary for communication across the Internet but on a private network they are just IP addresses like any other.