AWS - Security Groups and Network ACLs
You created an inbound rule allowing TCP port 22 from 0.0.0.0/0 but cannot SSH into your EC2 instance. What is a likely cause?
You created an inbound rule allowing TCP port 22 from 0.0.0.0/0 but cannot SSH into your EC2 instance. What is a likely cause?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check security group attachment
Even if rules are correct, if the security group is not attached to the instance, rules won't apply.Step 2: Consider other causes
Outbound rules usually allow return traffic by default; OS firewall or protocol mismatch would cause different symptoms.Final Answer:
Security group is not attached to the instance -> Option AQuick Check:
Security group must be attached to instance [OK]
Quick Trick: Check if security group is attached to instance [OK]
Common Mistakes:
- Ignoring security group attachment
- Assuming outbound rules block SSH
- Not checking OS firewall settings
Master "Security Groups and Network ACLs" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes