You created a security group with this ingress rule: Protocol: TCP, Port Range: 443, Source: 0.0.0.0/0. However, HTTPS traffic is still blocked. What is the most likely reason?

medium📝 Debug Q14 of 15

AWS - Security Groups and Network ACLs

You created a security group with this ingress rule: Protocol: TCP, Port Range: 443, Source: 0.0.0.0/0. However, HTTPS traffic is still blocked. What is the most likely reason?

AThe instance's network ACL blocks port 443

BSecurity groups do not control HTTPS traffic

CThe source IP range 0.0.0.0/0 is invalid

DPort 443 is only for HTTP, not HTTPS

Step-by-Step Solution

Solution:

Step 1: Confirm security group rule allows HTTPS
Protocol TCP, port 443, source 0.0.0.0/0 allows HTTPS traffic from anywhere.
Step 2: Identify other network controls
Network ACLs can block traffic even if security group allows it.
Final Answer:
The instance's network ACL blocks port 443 -> Option A
Quick Check:
Network ACL can override security group [OK]

Quick Trick: Check network ACL if security group allows but traffic blocked [OK]

Common Mistakes:

Thinking security groups don't control HTTPS
Believing 0.0.0.0/0 is invalid
Confusing port 443 with HTTP port 80

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 this ingress rule: Protocol: TCP, Port Range: 443, Source: 0.0.0.0/0. However, HTTPS traffic is still blocked. What is the most likely reason?

Step 1: Confirm security group rule allows HTTPS

Step 2: Identify other network controls

Final Answer:

Quick Check:

Want More Practice?