[Solved] A security group rule intended to allow HTTP traffic is written as: {"IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "IpRanges": [{"CidrIp": "0.0.0.0/0"}]}.... What is the most likely cause? | AWS

AWS - Security Groups and Network ACLs

A security group rule intended to allow HTTP traffic is written as: {"IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "IpRanges": [{"CidrIp": "0.0.0.0/0"}]}. However, HTTP traffic is still blocked. What is the most likely cause?

AThe protocol should be UDP instead of TCP

BThe CIDR block 0.0.0.0/0 is invalid

CThe port range is incorrect for HTTP

DThe security group is not attached to the resource

Step-by-Step Solution

Solution:

Step 1: Verify rule correctness
The rule correctly allows TCP port 80 from anywhere.
Step 2: Check resource association
If the security group is not attached to the resource, rules have no effect.
Final Answer:
The security group is not attached to the resource -> Option D
Quick Check:
Correct rule but no attachment = no effect [OK]

Quick Trick: Security group must be attached to resource to work [OK]

Common Mistakes:

Changing protocol to UDP incorrectly
Assuming port 80 is wrong
Thinking 0.0.0.0/0 is invalid

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

More AWS Quizzes

What is the most likely cause?

Step 1: Verify rule correctness

Step 2: Check resource association

Final Answer:

Quick Check:

Want More Practice?