Security group or NACL, when which
Security groups are stateful and per-resource. NACLs are stateless and per-subnet.
support/cloud-platforms/security-groups-vs-naclsteps: 4
Try this first
- Default workflow: everything via security groups, NACLs as extra layer only
- NACLs help to block entire IP ranges at subnet level
- Remember: NACL is stateless, allow inbound and outbound separately
- Don't test changes in production, NACL deny is hard to debug
When to bring us in
For strict segmentation, look at AWS Network Firewall or Security Groups for Pods (EKS).
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.