AWS - VPC Fundamentals
After deploying a NAT Gateway in a public subnet, instances in the private subnet still cannot access the internet. Which of the following is the most probable misconfiguration?
After deploying a NAT Gateway in a public subnet, instances in the private subnet still cannot access the internet. Which of the following is the most probable misconfiguration?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Verify Route Table Configuration
Instances in private subnets require a route directing0.0.0.0/0traffic to the NAT Gateway to access the internet.Step 2: Check NAT Gateway Placement
NAT Gateways must be in public subnets with an Elastic IP; if deployed correctly, the route table is often the missing link.Final Answer:
The private subnet's route table does not have a route directing internet traffic to the NAT Gateway. -> Option BQuick Check:
Missing route to NAT Gateway [OK]
Quick Trick: Private subnet needs route to NAT Gateway [OK]
Common Mistakes:
- Assuming NAT Gateway can be in private subnet
- Forgetting to add route to NAT Gateway in private subnet route table
- Confusing Elastic IP association as a misconfiguration when it is required
Master "VPC Fundamentals" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes