AWS - Security Groups and Network ACLs
Given a security group with inbound rule allowing TCP port 443 from 0.0.0.0/0 and outbound rule allowing all traffic, what happens when a user tries to access HTTPS on an EC2 instance?
Given a security group with inbound rule allowing TCP port 443 from 0.0.0.0/0 and outbound rule allowing all traffic, what happens when a user tries to access HTTPS on an EC2 instance?
medium📝 service behavior Q4 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze inbound rule for HTTPS
Inbound allows TCP port 443 from anywhere, so HTTPS traffic is allowed in.Step 2: Analyze outbound rule
Outbound allows all traffic, so response can go back to user.Final Answer:
User can connect successfully to EC2 on port 443 -> Option AQuick Check:
Inbound allows HTTPS and outbound is open = The user can connect successfully to the EC2 instance on port 443 [OK]
Quick Trick: Inbound must allow port; outbound open allows response [OK]
Common Mistakes:
- Confusing port 80 with 443
- Thinking outbound rules block response
- Believing security groups ignore HTTPS
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