A SysOps Administrator is setting up an administrative logging server on an Amazon EC2 instance in a public subnet () to receive remote log streams over TCP port 514 from a legacy on-premises logging agent (). The public subnet is associated with a custom Network Access Control List (NACL), and the EC2 instance is associated with a custom Security Group. The custom Security Group has an inbound rule allowing TCP port 514 from and an outbound rule allowing all traffic. However, logs are not reaching the server, and connection attempts are timing out. Which two updates to the custom NACL rules must the administrator perform to resolve this connectivity issue?
- Inbound rule: Allow TCP traffic from on port 514Cevap
- Outbound rule: Allow TCP traffic to on ports 1024-65535Cevap
- COutbound rule: Allow TCP traffic to on port 514
- DInbound rule: Allow TCP traffic from on ports 1024-65535
- EOutbound rule: Allow TCP traffic to on ports 0-1023
Cevap
To resolve the connectivity issue, the administrator must add an inbound NACL rule allowing TCP traffic from on port 514, and an outbound NACL rule allowing TCP traffic to on ephemeral ports 1024-65535.
Network ACLs are stateless. To allow the TCP connection to succeed, the inbound NACL rule must permit the initial packet on the application's service port (TCP 514). Because NACLs do not track connection state, the response packet must also be explicitly allowed outbound. The response is sent back to the client's dynamically allocated ephemeral port, which lies within the 1024-65535 range. Thus, both the inbound rule for port 514 and the outbound rule for ports 1024-65535 are required.
Adım Adım Çözüm
Anahtar Kavram
Statelessness of Network ACLs and the requirement of ephemeral ports for return traffic.