- Newest
- Most votes
- Most comments
I would start by investigating the connection from on-prem to AWS. Below are two guides that can help to troubleshoot the packet loss. How do I troubleshoot packet loss on my VPN connection? https://repost.aws/knowledge-center/troubleshoot-vpn-packet-loss How can I troubleshoot packet loss for my Direct Connect connection? https://repost.aws/knowledge-center/direct-connect-packet-loss
Hi, this very probably comes from the fact that your different EC2 instances are protected by different security groups: one allowing ICMP (ping) and the other not. So, please, identify those 2 sec groups and align them for ICMP.
See details to allow ping (specifically): https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html#sg-rules-ping.
If groups are same, the second possible cause is absence of public IP for the failing one. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#concepts-public-addresses to check if you have one for your instance and how to add it if not.
Thanks, but my security group is okay because I can ping normally but I just concern because there is a packet loss sometime not 100% packet loss nor Request time out.
Relevant content
- asked 8 months ago
- asked 10 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thanks, but I didn't use VPN connection nor Direct Connect connection because I ping to my EC2 instance Public IP