Q: What is VPC Flow Logs and how do you use it for security investigations?
VPC Flow Logs captures IP traffic information for network interfaces in your VPC. Logged to CloudWatch Logs or S3.
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In our AWS cloud environment, we managed high-traffic microservices where this exact scenario occurred. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
VPC Flow Logs captures IP traffic information for network interfaces in your VPC. Logged to CloudWatch Logs or S3.
- Security investigation — "Where did this attack come from?" Filter logs for a suspicious IP.
- Detecting port scans — many REJECT records from same source IP across many ports.
- Troubleshooting connectivity — if traffic shows REJECT, a security group or NACL is blocking it.
Remediation & Permanent Safeguards
Each record includes: source IP, destination IP, source port, destination port, protocol, bytes, action (ACCEPT/REJECT), etc. Use cases: Query with Athena for large-scale analysis. Set up CloudWatch Logs Insights for real-time querying.
- Billing anomalies — high data transfer costs. Flow logs show which IP is generating the traffic.
- Security investigation — "Where did this attack come from?" Filter logs for a suspicious IP.
- Detecting port scans — many REJECT records from same source IP across many ports.
- Troubleshooting connectivity — if traffic shows REJECT, a security group or NACL is blocking it.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring Flow Logs security AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
-
Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring Flow Logs security
Accessing SSE-KMS encrypted objects requires both
s3:GetObjectandkms:Decryptpermissions; neglecting KMS key policies causes silent 403 Forbidden errors. - Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring Flow Logs security Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
- Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring Flow Logs security Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.