Network Access Control List (NACL) (NACL)
Perimeter firewall protecting VPC subnets. Unlike stateful Security Groups, NACLs are stateless: return traffic MUST be explicitly permitted via outbound rules specifying ephemeral port ranges (1024-65535). Evaluates rules strictly by rule number (1-32766) in ascending order, where the first matching rule dictates ALLOW or DENY. Provides subnet-level protection and explicit CIDR blacklisting.
AWS Container Placement
VPC
Summary
Stateless subnet-boundary firewall operating at the network layer (Layer 4) evaluating numbered rules in ascending order.
When to Use (SAA-C03)
Use to explicitly block malicious IPs/CIDRs at the subnet boundary; always allow ephemeral ports 1024-65535 on return traffic!
Allowed Ingress Connections & Ports
| Source Service | Protocol | Port | Architectural Rationale |
|---|---|---|---|
| WEBCLIENT | HTTP, HTTPS | 80, 443 | Public internet web clients arriving at public subnet perimeter |
| IGW | TCP, UDP, ICMP | 80, 443, Ephemeral 1024-65535 | Packets routed through Internet Gateway into public subnets |
| NAT | TCP | Ephemeral 1024-65535 | Outbound NAT translation return responses entering private subnets |
| SUBNET | TCP, UDP | 5432, 3306, 8080, 443 | Inter-subnet traffic between public, app, and database tiers |
Allowed Egress Targets & Ports
| Target Service | Protocol | Port | Data Flow Rationale |
|---|---|---|---|
| IGW | TCP, UDP | 80, 443, Ephemeral 1024-65535 | Outbound traffic routed to public internet via Internet Gateway |
| NAT | TCP | 80, 443 | Private instances sending outbound API calls through NAT Gateway |
| SUBNET | TCP, UDP | Any port | Internal packet forwarding to adjacent subnet CIDR ranges |
| EC2 | TCP, UDP | 80, 443, Ephemeral 1024-65535 | Final packet delivery to compute endpoints within the subnet |
Key Configuration Parameters & AWS Best Practices
| Parameter | Format / Example | Purpose & Rationale |
|---|---|---|
| VPC ID (vpcId) (Required) | vpc-0a1b2c3d4e5f67890 | Identifies the VPC boundary that owns this Network Access Control List. Why: Every NACL belongs to exactly one VPC and can only be associated with subnets in that VPC. |
| Subnet Associations (subnetIds) (Required) | subnet-0123456789abcdef0, subnet-0987654321fedcba0 | One or more Subnet IDs associated with this NACL. Each subnet is associated with exactly one NACL at a time. Why: A NACL has no effect until attached to one or more subnets. |
| Inbound Rules (inboundRules) (Required) | Rule 100: TCP 443 from 0.0.0.0/0 ALLOW | Numbered list of ingress rules evaluated in ascending order. First matching rule wins. Why: Controls which packets are permitted to cross into the subnet from outside. |
| Outbound Rules (outboundRules) (Required) | Rule 100: TCP 1024-65535 to 0.0.0.0/0 ALLOW | Numbered list of egress rules evaluated in ascending order. Because NACLs are stateless, return traffic must match an outbound rule. Why: Controls which packets are permitted to depart the subnet boundary. |
| Default NACL (isDefaultNacl) | false | Indicates whether this is the default VPC NACL created automatically by AWS. Why: Default NACLs allow all traffic by default, whereas custom NACLs deny all traffic until rules are added. |
| Tags (tags) | Tier: Public-Perimeter, Environment: Production | Metadata tags for cost tracking, ownership tagging, and automation. Why: Ensures compliance with enterprise tagging standards. |
Practice Labs Using Network Access Control List (NACL)
Frequently Asked Questions
Where does Network Access Control List (NACL) live inside an AWS VPC architecture?
Valid container placement: VPC. Perimeter firewall protecting VPC subnets. Unlike stateful Security Groups, NACLs are stateless: return traffic MUST be explicitly permitted via outbound rules specifying ephemeral port ranges (1024-65535). Evaluates rules strictly by rule number (1-32766) in ascending order, where the first matching rule dictates ALLOW or DENY. Provides subnet-level protection and explicit CIDR blacklisting.
When should I use Network Access Control List (NACL) on the AWS SAA-C03 exam?
Use to explicitly block malicious IPs/CIDRs at the subnet boundary; always allow ephemeral ports 1024-65535 on return traffic!
Can I simulate Network Access Control List (NACL) packet routing without an AWS account?
Yes. CloudTracer simulates Network Access Control List (NACL) along with 53 AWS services directly in your browser and exports production Terraform HCL.