A SysOps Administrator is configuring VPC Traffic Mirroring to capture a copy of inbound HTTPS traffic from a production application server's network interface (10.0.1.10) in a VPC. The mirrored traffic must be sent to an intrusion detection system (IDS) instance (10.0.2.20) in a different subnet of the same VPC. The administrator has successfully configured the Traffic Mirror Source, the Traffic Mirror Target, and a Traffic Mirror Filter to capture inbound TCP port 443 traffic. However, the IDS instance is not receiving any mirrored packets. Which configuration change should the administrator make to allow the mirrored traffic to reach the IDS instance?
- Add a rule to the security group of the IDS instance to allow inbound UDP traffic on port 4789 from the source network interface.Cevap
- BAdd a rule to the Network ACL of the target subnet to allow inbound TCP traffic on ports 1024-65535 from the source subnet.
- CAdd a route to the route table of the source subnet targeting the Internet Gateway for the IDS instance's IP address.
- DAssign an IAM role with the iam:PassRole permission to the source EC2 instance to allow the Traffic Mirror session to write to the target.
Cevap
Add a rule to the security group of the IDS instance to allow inbound UDP traffic on port 4789 from the source network interface.
The correct answer is to allow inbound UDP traffic on port 4789 from the source network interface. VPC Traffic Mirroring encapsulates mirrored network packets in a VXLAN header, which uses UDP destination port 4789. Because security groups are stateful and block unsolicited traffic by default, the security group of the target IDS instance must be configured to allow this inbound UDP traffic to receive the mirrored packets.
Adım Adım Çözüm
Anahtar Kavram
VPC Traffic Mirroring relies on VXLAN encapsulation (UDP port 4789) to copy and send packets to the target ENI, requiring target security groups to permit this inbound traffic.