AWS - VPC Fundamentals
You created a NAT Gateway in a public subnet but instances in the private subnet cannot access the internet. What is the most likely cause?
You created a NAT Gateway in a public subnet but instances in the private subnet cannot access the internet. What is the most likely cause?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check route table configuration
Instances in private subnets need a route directing internet traffic (0.0.0.0/0) to the NAT Gateway.Step 2: Identify missing route issue
If this route is missing, traffic won't reach the NAT Gateway, causing no internet access.Final Answer:
The private subnet route table does not have a route to the NAT Gateway -> Option BQuick Check:
Missing route to NAT Gateway = no internet [OK]
Quick Trick: Check private subnet route table for NAT Gateway route [OK]
Common Mistakes:
- Ignoring route table routes
- Assuming Elastic IP is optional
- Confusing Internet Gateway attachment with NAT Gateway routing
Master "VPC Fundamentals" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes