Why Can't My EC2 Instance Reach the Internet? A Five-Point Checklist

FE
FigigExams Team
Senior Network & Security Engineers · 6+ years designing and securing enterprise networks. We build the FigigExams AWS SAA exam. This guide maps to task 1.2 and 3.4 of AWS's SAA-C03 exam guide.
Aligned to the AWS SAA-C03 exam guide · Nov 2026
Try it · free · no credit card

Know the answer? Fix it in a free advanced lab

A complete SAA-C03 practice exam: 65 questions in 130 minutes, an explanation on every item and an Exam Coach report that ranks your weakest domains.

Already have an account? Log in to redeem

An EC2 instance reaches the internet through a route, a gateway and permission to send the traffic. In a public subnet it needs a route to an internet gateway and a public IP. In a private subnet it needs a route to a NAT gateway, and the NAT gateway must sit in a public subnet.Checked against AWS's published exam guide on 9 November 2026.

How traffic leaves a VPC

Public subnetPrivate subnet
Default routeTo an internet gatewayTo a NAT gateway
Instance addressNeeds a public IPv4 or Elastic IPPrivate IP only
Inbound from internetPossible, if allowedNo

The five usual causes

  1. No default route. The subnet's route table has no 0.0.0.0/0 entry, or it points to the wrong target.
  2. No public IP. An instance in a public subnet was launched without one.
  3. NAT gateway in the wrong place. It must sit in a public subnet, and that subnet needs its own route to the internet gateway.
  4. Security group blocks outbound. The default allows all outbound, but someone may have removed that.
  5. Network ACL blocks the return. NACLs are stateless, so return traffic on ephemeral ports needs its own rule.

A two-minute checklist

CheckHealthy looks like
Subnet route table0.0.0.0/0 to an internet gateway, or to a NAT gateway
NAT gateway stateAvailable, in a public subnet
Instance addressingPublic IP, if the subnet is public
Security group outboundAllows the traffic
Network ACLAllows outbound and the return on ephemeral ports

How SAA-C03 words this

If the question saysThink
Private instances need outbound updatesNAT gateway
Must not be reachable from the internetPrivate subnet
Reach S3 without internet accessGateway VPC endpoint
NAT gateway must survive an AZ failureOne NAT gateway per AZ
IPv6 outbound onlyEgress-only internet gateway

Why Can't EC2 Reach the Internet?: practice questions

Five original questions. Each explanation says why the other options fail.

Try it · free · no credit card

Your free AWS SAA exam code is ready

Sit the full SAA-C03 paper against the real 130-minute clock. AWS SAA is $39 once, lifetime, future versions included.

AWS-SAA-FULL Redeem the code

Already have an account? Log in to redeem

Frequently asked questions

Why can't my EC2 instance reach the internet?

Usually a missing default route, no public IP in a public subnet, a NAT gateway in the wrong subnet, or a security group or network ACL blocking the traffic.

Does a NAT gateway go in a public or private subnet?

A public subnet. Private subnets then route their internet traffic to it.

Do instances in private subnets need a public IP?

No. They reach the internet through a NAT gateway.

Study guides Free exam