VPC Flow Logs not enabled
VPC Flow Logs capture metadata about traffic going to and from network interfaces — source, destination, port, bytes, accept/reject. They're off by default.
Why it matters
After an incident, flow logs answer 'what did this host talk to' — exfiltration destinations, scanning, lateral movement. Without them, that's unknowable.
They also feed GuardDuty and help debug connectivity, so the value goes beyond security.
How to check for it
- aws ec2 describe-flow-logs per region, and check that your main VPCs appear.
- Confirm the logs go somewhere retained (CloudWatch Logs or S3) with a sensible retention period.
How to fix it
- Enable flow logs at the VPC level, delivering to S3 (cheap, long retention) or CloudWatch Logs (queryable).
- Set retention to meet your compliance window and restrict who can disable them.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- VPC, subnet or ENI level?
- Enable at the VPC level to cover everything in it; you can still add finer logs for specific subnets or interfaces if needed.