ec2 instance unreachable after reboot

Question

I rebooted my ec2 instance i-0b64fcd5175de4a40 and after the reboot, http and https are unreachable. I could get into it via ssh. I have listeners on 80 and 443  
  
New-Pom # netstat -an | grep -i listen  
tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN       
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN       
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN       
tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN       
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN       
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN       
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN       
tcp6       0      0 :::111                  :::*                    LISTEN       
tcp6       0      0 :::22                   :::*                    LISTEN   
  
My elastic IP is 52.24.24.107 eipalloc-38bc045d  
  
I have rules (sg-8e6eefeb) which allow the following:   
HTTP	TCP	80	0.0.0.0/0  
HTTPS	TCP	443	0.0.0.0/0  
  
I don't have a local firewall blocking 80 and 443. I can telnet to those ports on the machine.   
  
I would really appreciate some help.

Answer

I'm running AWS Linux and I had done an upgrade. The upgrade either installed or reconfigured firewalld and that was blocking HTTP and HTTPS. In my original post, I said a firewall wasn't blocking those ports. I meant iptables - I checked and it had no rules for those ports.

Answer

Let the necro commence!

Basically check: https://aws.amazon.com/premiumsupport/knowledge-center/connect-http-https-ec2/
I had exactly same issue and it was iptables rules after major yum update. Dropped iptables config / allowed everything on the instance, worked like a charm.

ec2 instance unreachable after reboot

Relevant content