An IoT company deploys telemetry collection servers on Amazon EC2 instances within a custom subnet. The cloud practitioner configures a Network Access Control List (Network ACL) at the subnet level to allow inbound TCP traffic on port 8883 from the internet. Although the EC2 instances' Security Groups are configured to allow all outbound traffic, the external sensors are unable to receive acknowledgment responses from the servers. Which of the following configuration changes is required to resolve this issue and allow the acknowledgment traffic back to the sensors?
- Add an outbound rule to the subnet's Network ACL that allows traffic to the ephemeral port range of the external sensors.Answer
- BAdd an outbound rule to the EC2 instances' Security Group to allow return traffic on the ephemeral port range.
- CSubmit a ticket to AWS Support requesting that they open outbound ephemeral ports on the underlying physical switches of the VPC.
- DEnable Amazon GuardDuty at the subnet level to identify and automatically remediate the blocked ports on the virtual router.
Answer
Add an outbound rule to the subnet's Network ACL that allows traffic to the ephemeral port range of the external sensors.
The correct option is correct because Network ACLs are stateless firewalls operating at the subnet level. They evaluate inbound and outbound rules independently. When inbound traffic is allowed on port 8883, the return traffic destined for the client's ephemeral ports will be blocked unless an outbound rule explicitly allows it. Security Groups, on the other hand, are stateful and do not block this return traffic.
Step-by-Step Solution
Key Concept
Stateful vs. Stateless Firewalls in AWS (Security Groups vs. Network ACLs)
Estimated Time:1m 30s