A SysOps Administrator is troubleshooting a connectivity issue for a web server hosted on an Amazon EC2 instance with private IP address 10.0.1.100. Clients are unable to load pages from the web server. The administrator enables VPC Flow Logs on the instance's elastic network interface (ENI) and observes the following log records:
2 123456789012 eni-1234567890abcdef 203.0.113.10 10.0.1.100 50001 80 6 10 520 1620000000 1620000060 ACCEPT OK
2 123456789012 eni-1234567890abcdef 10.0.1.100 203.0.113.10 80 50001 6 5 260 1620000000 1620000060 REJECT OK
Which action should the administrator take to resolve this issue?
- Add an outbound rule to the Network ACL associated with the subnet to allow TCP traffic to destination ports 1024-65535.Answer
- BAdd an outbound rule to the Security Group associated with the EC2 instance to allow TCP traffic to destination port 50001.
- CAdd a route targeting the Internet Gateway (IGW) in the subnet's route table for the destination 203.0.113.10/32.
- DRecreate the VPC Flow Log using an IAM role that has the iam:PassRole permission.
Answer
Add an outbound rule to the Network ACL associated with the subnet to allow TCP traffic to destination ports 1024-65535.
The correct answer is to add an outbound rule to the Network ACL associated with the subnet to allow TCP traffic to destination ports 1024-65535. Network ACLs are stateless, meaning return traffic must be explicitly allowed. Since the client's request on port 80 uses an ephemeral source port (50001), the outbound response from the web server is destined for port 50001. Outbound rules in the Network ACL must permit this ephemeral range.
Step-by-Step Solution
Key Concept
Stateless nature of Network ACLs requiring explicit outbound rules for ephemeral ports
Estimated Time:1m 30s