AWS - Security Groups and Network ACLs
You created a security group rule to allow inbound SSH (port 22) from your office IP, but you still cannot connect. What is the most likely mistake?
You created a security group rule to allow inbound SSH (port 22) from your office IP, but you still cannot connect. What is the most likely mistake?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check rule direction and protocol
Inbound SSH requires TCP on port 22 inbound; if rule is correct, this is fine.Step 2: Verify security group attachment
If the security group is not attached to the resource (like EC2 instance), rules won't apply.Final Answer:
The security group is attached to the wrong resource -> Option DQuick Check:
Security group must be attached to resource [OK]
Quick Trick: Check if security group is attached to your resource [OK]
Common Mistakes:
- Ignoring security group attachment
- Confusing inbound and outbound rules
- Using wrong protocol for SSH
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