In addition to @Bard Lan's excellent answer, ensure the httpd service is running on the EC2 instance - if you're running Linux, you could try a
systemctl status httpd or even
ps -ef | grep httpd.
If you've rebooted the instance recently, it's possible the httpd service isn't configured to restart when the server does, in which case you can restart with a
systemctl start httpd and then
systemctl enable httpd to ensure the httpd service restarts on a reboot.
(The above assumes you're using the Apache web server, if not replace
httpd with your preferred web server service.)
It's might caused by many reasons, you can check following configurations:
- Check the IP you used is "Public IP": if the Public IP is not assigned by default, you can allocate an Elastic IP and then attach it to your EC2 instance
- Confirm your EC2 instance is running at Public Subnet: you can verify it by checking route table related to the Subnet which EC2 running on, and make sure the route rule "0.0.0.0/0 to IGW (Internet Gateway)" is existed.
- Verify Security Group and Network ACL configurations: confirm the required ports are opened and check your Client IP is included in the Range of Source CIDR.
- Clarify if there any firewalls (such as AWS Network Firewall) are provisioned to block the traffic between EC2 instance and your Client environment.
- Check the application you deployed on EC2 instance is workable (or you can try the network availability by ICMP - ping [EC2 Instance IP])
- Check your Client Network, does it behind a VPN? Sometimes the VPN will block some traffics, or please eliminate any hinders possibilities for client side network.
- asked 2 months ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- Why am I receiving a "no Spot capacity available" error when trying to launch an Amazon EC2 Spot Instance?AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a month ago
- EXPERTpublished 3 months ago