Struggling with Cloud Quest Networking Concepts Practice Lab

When you're unable to reach an EC2 web server instance via its public IP in the Cloud Quest lab, there are several key areas to check:

1. Security Group Configuration: Ensure the security group attached to your EC2 instance has an inbound rule that allows HTTP traffic (port 80) from anywhere (0.0.0.0/0). This is the most common issue when a web server is unreachable.

2. Network ACLs: Verify that the network ACLs for your subnet allow inbound and outbound traffic on port 80.

3. Route Table Configuration: Check that the route table associated with your subnet includes a route for internet-bound traffic (0.0.0.0/0) pointing to an internet gateway.

4. Web Server Status: Confirm that the web server (like Apache or Nginx) is actually running on your instance. You can SSH into the instance and use commands like systemctl status httpd to check.

5. Instance State: Verify your EC2 instance is in the "running" state and has passed all status checks.

6. Public IP Verification: Double-check you're using the correct public IP address, as it might change if you stop and start the instance.

Since the validation for the DB server security group was successful, the issue is likely with the web server configuration or its connectivity settings. In Cloud Quest labs, sometimes there are specific requirements that need to be followed exactly as instructed.

If you've verified all these settings and still can't access the instance, you might need to restart the lab and carefully follow each step, particularly those related to network configuration and security group settings.
Sources
Unable to access the EC2 instance with the Public IP | AWS re:Post
EC2 Instance not showing default 'Hello World' page at stated IP. | AWS re:Post