- 최신
- 최다 투표
- 가장 많은 댓글
Hi Arjun, the simplest way to check if it is an issue with your AWS configuration is using the Reachability Analyzer. It will simulate the packet flow and you can see if for example your security groups are wrongly configured.
Hey Luca Schumann, sorry I am not aware how to use the tool and I need to resolve this little urgently. I hope you understand what I mean. Can you help me in figuring out if I missed anything while doing configuration?
Agreed, Reachability Analyzer is recommended tool to fix such issue(s) probably related to routing tables or sec groups.
This video may help you if you want to use it: https://www.youtube.com/watch?v=T9k8PD3YXAw
Hey Luca Schumann, in case I have to check if one instance is pinging another instance or not, how to check it via VPC Reachability Analyzer as it only has two protocols option i.e.
TCP
andUDP
. Can you please help me in figuring out this?I would use the port and protocol that you will be using for communication between the two instances (e.g. TCP 80). Let me know what the result is.
This is what I got after I selected port 80 and protocol as
TCP
to check the ping from OpenVPN to private EC2 server. Attaching the screenshot for your reference:
Are you allowing port 80 TCP on the private-server security group inbound rules? Do it and try the path analysis again. Make sure you reference the openvpn security group as source. The path should then be green. Once the path is green, just add the same rules for ICMP to the security groups and you should be able to ping.
관련 콘텐츠
- 질문됨 6달 전
- AWS 공식업데이트됨 8달 전
Please share your security groups configurations.