Why Can't My EC2 Instance Reach the Internet? A Five-Point Checklist
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.
AWS-SAA-FULL
Try a free AWS SAA exam
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.
In this guide
How traffic leaves a VPC
| Public subnet | Private subnet | |
|---|---|---|
| Default route | To an internet gateway | To a NAT gateway |
| Instance address | Needs a public IPv4 or Elastic IP | Private IP only |
| Inbound from internet | Possible, if allowed | No |
The five usual causes
- No default route. The subnet's route table has no
0.0.0.0/0entry, or it points to the wrong target. - No public IP. An instance in a public subnet was launched without one.
- NAT gateway in the wrong place. It must sit in a public subnet, and that subnet needs its own route to the internet gateway.
- Security group blocks outbound. The default allows all outbound, but someone may have removed that.
- Network ACL blocks the return. NACLs are stateless, so return traffic on ephemeral ports needs its own rule.
A two-minute checklist
| Check | Healthy looks like |
|---|---|
| Subnet route table | 0.0.0.0/0 to an internet gateway, or to a NAT gateway |
| NAT gateway state | Available, in a public subnet |
| Instance addressing | Public IP, if the subnet is public |
| Security group outbound | Allows the traffic |
| Network ACL | Allows outbound and the return on ephemeral ports |
How SAA-C03 words this
| If the question says | Think |
|---|---|
| Private instances need outbound updates | NAT gateway |
| Must not be reachable from the internet | Private subnet |
| Reach S3 without internet access | Gateway VPC endpoint |
| NAT gateway must survive an AZ failure | One NAT gateway per AZ |
| IPv6 outbound only | Egress-only internet gateway |
Why Can't EC2 Reach the Internet?: practice questions
Five original questions. Each explanation says why the other options fail.
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.