AWS VPC Troubleshooting Cheat Sheet: Symptom, Check, Command
Know the checks? Try them 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
When something on AWS cannot connect, check in this order: routing, then security groups, then network ACLs, then the service's own policy. VPC Reachability Analyzer tests a path without sending traffic, and VPC Flow Logs show whether traffic was accepted or rejected.Checked against AWS's published exam guide on 9 November 2026.
In this guide
Symptom to cause: the quick reference
| Symptom | Check first | Usual fix |
|---|---|---|
| Private instance cannot reach the internet | Route to a NAT gateway | Add 0.0.0.0/0 to the NAT gateway |
| Public instance is unreachable | Public IP, route to an internet gateway, security group | Attach the missing piece |
| ALB shows all targets unhealthy | Health check path and the instance security group | Allow the ALB, correct the path |
| Application cannot reach RDS | Database security group | Allow the app's security group on the database port |
| S3 access denied | Bucket policy, IAM policy, explicit denies | Remove the deny, or add the allow |
| Lambda cannot reach the internet | VPC attachment and a route to NAT | Use private subnets with a NAT route |
| Peered VPCs cannot talk | Routes on both sides | Add return routes |
A routine that works
- State the path: source, destination, port and protocol.
- Check routing, in both directions.
- Check security groups, which are stateful.
- Check network ACLs, which are stateless and need return rules.
- Check identity and resource policies where the service uses them.
- Confirm with evidence: Flow Logs or Reachability Analyzer.
AWS CLI commands for each layer
| Layer | Command |
|---|---|
| Identity in use | aws sts get-caller-identity |
| Routes | aws ec2 describe-route-tables |
| Security groups | aws ec2 describe-security-groups |
| Network ACLs | aws ec2 describe-network-acls |
| NAT gateways | aws ec2 describe-nat-gateways |
| VPC endpoints | aws ec2 describe-vpc-endpoints |
| Load balancer target health | aws elbv2 describe-target-health |
| Bucket policy | aws s3api get-bucket-policy |
| Test an IAM permission | aws iam simulate-principal-policy |
You will not be asked to type commands on SAA-C03. They are here so that you can practise in a real account and see what each layer holds.
AWS tools that find the fault
| Tool | What it answers |
|---|---|
| VPC Reachability Analyzer | Is this path configured to work, and if not, what blocks it? |
| VPC Flow Logs | Was traffic accepted or rejected? |
| IAM Policy Simulator | Would this identity be allowed? |
| CloudTrail | Who changed this, and when? |
| AWS Config | What did this resource look like before? |
VPC Troubleshooting Cheat Sheet: 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
How do you troubleshoot AWS VPC connectivity?
Check routing, then security groups, then network ACLs, then identity and resource policies. Confirm with Flow Logs or Reachability Analyzer.
What is the difference between Flow Logs and Reachability Analyzer?
Flow Logs record real traffic as accepted or rejected. Reachability Analyzer tests whether a path is configured to work, without sending traffic.
Are AWS CLI commands on SAA-C03?
No. The exam does not ask you to type commands. They help when you practise in a real account.