A SysOps Administrator is troubleshooting a connectivity issue where external users cannot access a web application running on an Amazon EC2 instance. The instance is located in a subnet that is intended to be public. The administrator verifies that the web server is active and listening locally on TCP port . However, when reviewing the VPC Flow Logs for the instance's elastic network interface (ENI), the administrator finds that there are no flow log records (either `ACCEPT` or `REJECT`) corresponding to external client IP addresses on port .
What is the most likely cause of this issue?
- AThe Network ACL associated with the subnet does not allow inbound TCP traffic on port .
- The subnet's route table does not contain a route pointing to the Internet Gateway.Answer
- CThe security group associated with the EC2 instance does not allow inbound TCP traffic on port .
- DThe Application Load Balancer target group health check path is misconfigured.
Answer
The subnet's route table does not contain a route pointing to the Internet Gateway.
The correct answer is that the subnet's route table does not contain a route pointing to the Internet Gateway. VPC Flow Logs capture traffic at the network interface (ENI) level. If traffic from the internet cannot be routed to the subnet because of a missing route to the Internet Gateway, the packets never reach the ENI. Consequently, no flow log entries (neither ACCEPT nor REJECT) are generated for the client IPs. For a subnet to be public and accessible from the internet, its route table must have a route for pointing to the Internet Gateway.
Step-by-Step Solution
Key Concept
VPC routing requirements for public subnets and the behavior of VPC Flow Logs at the ENI level.