February 22, 2023, Accelerate innovation with big data and AI/ML

AWS Innovate is back and you are invited to join us for the first edition of the year! With 60+ business and technical sessions to choose from, don’t miss the opportunity to take your big data and AI/ML skills to the next level and learn the latest from AWS experts and cloud technologists
 Register now 
 Register now and dive deeper into these topics with us.How today’s organizations are innovating with AI & MLGetting started with AI/ML and deployment best practicesHow to easily prepare, build, train, and deploy ML models at scaleA builder’s path to developing, architecting & running ML workloadsBuilding a solid data infrastructure to help you deliver high performance AI & ML models trained by data 
 Learn more and register now 
 We look forward to engage with you on February 22, 2023. Don’t forget to prepare your questions and get them answered by AWS experts.Best regards,
Amazon Web Services

when ipv4 not detected aws hosted website not working

Short description

To troubleshoot why your Amazon EC2 can’t access the internet, do the following:

  • Verify that the EC2 instance meets all prerequisites.
  • Verify that the instance has a public IP address.
  • Verify that a firewall isn’t blocking the access.

Resolution

Verify that the instance meets all prerequisites

The instance must meet the following conditions:

  • The route table that’s associated with your instance’s subnet has a default route to an internet gateway (0.0.0.0/0).
  • The internet gateway that’s associated with the route isn’t deleted.
  • The security group that’s attached to the instance’s elastic network interface has rules allowing outbound internet traffic (0.0.0.0/0) for your ports and protocols.
  • The network access control list (network ACL) that is associated with the instance’s subnet has rules allowing both outbound and inbound traffic to the internet.

Verify that the instance has a public IP address

If the instance in a public subnet doesn’t have a public IP address, then the instance isn’t accessible outside the virtual private cloud (VPC) where it resides in. This is true even if the instance has an internet gateway.

To allow the instance connectivity to the internet, allocate an Elastic IP address, and then associate this Elastic IP address with the instance.

Verify that a firewall isn’t blocking access

If the instance meets the preceding conditions and internet connectivity issues persist, then you might have a local firewall running in the operating system. It’s a best practice to use security groups instead of having a local firewall in the operating system. Be sure that disabling the local firewall doesn’t impact your workload.

# For Uncomplicated Firewall
sudo ufw disable

# For firewalld
sudo systemctl disable firewalld --now

If you must use a firewall, then the internet connectivity issues are usually related to the OUTPUT chain. You can allow outgoing traffic by running the following commands:

sudo iptables -P OUTPUT ACCEPT
sudo iptables -I OUTPUT 1 -j ACCEPT

Windows Server:

For Windows Server default firewalls, run the following command:

netsh advfirewall firewall show rule name=all

source