Q: What is the difference between a Security Group and a Network ACL (NACL)?
Architectural comparison between AWS Security Groups (stateful, instance-level firewall) and Network ACLs (stateless, subnet-level packet filter).
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."
Production Solution & Architecture
Security Groups and Network Access Control Lists (NACLs) form AWS's defense-in-depth perimeter. Security Groups act as stateful firewalls at the virtual network interface (ENI) level, whereas NACLs act as stateless packet filters at the subnet boundary.
- Security Groups Best Practice: Apply granular, least-privilege security between microservices and databases within your VPC.
- NACLs Best Practice: Apply coarse subnet-level shields (such as dropping known malicious IP/CIDR ranges or blocking specific external protocols).
- Security Group: Instance/ENI level, stateful connection tracking, allow-only rules.
- Network ACL: Subnet boundary level, stateless packet inspection, ordered allow and deny rules.
- Defense-in-Depth Pattern: Pair coarse NACL CIDR blocks at the subnet edge with fine-grained Security Groups per service tier.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when addressing difference Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
- Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
- Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
- Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.