You created a security group with only an outbound rule allowing all traffic, but no inbound rules. You cannot connect to your instance via SSH. What is the likely problem?

medium📝 Debug Q14 of 15

AWS - Security Groups and Network ACLs

AInbound SSH traffic is blocked because no inbound rule allows port 22

BOutbound rules block SSH response traffic

CSecurity groups require both inbound and outbound rules for SSH

DThe instance must have a public IP to allow SSH

Step-by-Step Solution

Solution:

Step 1: Analyze the security group rules
Only outbound rules exist; no inbound rules allow SSH (port 22).
Step 2: Understand inbound rules control incoming connections
Without inbound port 22 allowed, SSH connection attempts are blocked.
Final Answer:
Inbound SSH traffic is blocked because no inbound rule allows port 22 -> Option A
Quick Check:
No inbound port 22 = no SSH access [OK]

Quick Trick: Inbound rules must allow SSH for connection [OK]

Common Mistakes:

MISTAKES

Assuming outbound rules control incoming SSH
Thinking both inbound and outbound rules are mandatory for SSH
Ignoring instance public IP requirement

Master "Security Groups and Network ACLs" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You created a security group with only an outbound rule allowing all traffic, but no inbound rules. You cannot connect to your instance via SSH. What is the likely problem?

Step 1: Analyze the security group rules

Step 2: Understand inbound rules control incoming connections

Final Answer:

Quick Check:

Want More Practice?