A company's security policy requires that all network communication from a database subnet be captured for audit purposes. A SysOps Administrator configures VPC Flow Logs at the subnet level to capture all traffic. During an audit, the compliance officer notices that queries sent from the database EC2 instances to the default Amazon Route 53 Resolver (at the VPC DNS server IP address) are not appearing in the flow logs. Which action should the SysOps Administrator take to log these DNS queries?
- ACreate a gateway VPC endpoint for Amazon Route 53 in the database subnet and associate it with the subnet's route table.
- BModify the retention period of the CloudWatch Logs log group containing the VPC Flow Logs to ensure ephemeral metadata is not expired.
- Configure Amazon Route 53 Resolver query logging for the VPC and specify a destination such as a CloudWatch Logs log group.Answer
- DEnable detailed monitoring on the EC2 instances to capture high-frequency system network calls, including default DNS queries.
Answer
Configure Amazon Route 53 Resolver query logging for the VPC and specify a destination such as a CloudWatch Logs log group.
VPC Flow Logs have built-in exclusions and do not capture traffic sent to the default Amazon DNS server (Route 53 Resolver). To capture and audit these DNS queries, Amazon Route 53 Resolver query logging must be configured for the target VPC.
Step-by-Step Solution
Key Concept
VPC Flow Logs exclude traffic sent to the Amazon Route 53 Resolver (VPC DNS server). To capture these logs, Route 53 Resolver query logging must be enabled.
Estimated Time:1m 30s