Study guide

1.5 AWS WAF, Shield, and Network Firewall

AWS Solutions Architect Associate SAA-C03

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework

2 Domain 1: Design Secure Architectures (30%)

1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services

3 Domain 2: Design Resilient Architectures (26%)

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration

4 Domain 3: Design High-Performing Architectures (24%)

3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR

5 Domain 4: Design Cost-Optimized Architectures (20%)

4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools

6 VPC and Networking Deep Dive

5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services

7 Migration, Transfer, and Hybrid Services

6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family

8 Serverless Architecture and Application Services

7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR

9 Advanced Topics and Exam Scenarios

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together

1.5 AWS WAF, Shield, and Network Firewall

Key Takeaways Explain This Topic AI

AWS WAF inspects Layer-7 HTTP/HTTPS traffic and blocks SQL injection, cross-site scripting, bots, and rate-based floods.

WAF attaches to CloudFront, Application Load Balancer, API Gateway, AppSync, and Cognito — never to NLB or EC2 directly.

AWS Shield Standard gives free, automatic Layer-3/4 DDoS protection; Shield Advanced adds Layer-7 defense, cost protection, and 24/7 SRT access for about $3,000/month.

AWS Network Firewall provides stateful and stateless packet inspection, intrusion prevention, and domain filtering for VPC traffic.

AWS Firewall Manager centrally enforces WAF, Shield Advanced, security groups, and Network Firewall policies across an Organization.

Last updated: June 2026

Quick Answer: WAF blocks Layer-7 web exploits and attaches to CloudFront/ALB/API Gateway. Shield defends against DDoS — Standard is free, Advanced is ~$3,000/month with cost protection and a Shield Response Team. Network Firewall inspects packets inside the VPC. Firewall Manager governs all three across accounts.

AWS WAF (Web Application Firewall)

AWS WAF filters HTTP(S) requests at the application layer (Layer 7) using rules organized in a Web ACL (Access Control List) .

  • Threat WAF Rule
  • SQL injection SQLi match statement / SQL Database managed group
  • Cross-site scripting (XSS) XSS match statement
  • Malicious IPs IP set rule (allow/block)
  • Geographic blocking Geo-match statement
  • HTTP floods Rate-based rule (e.g., 2,000 requests / 5 min per IP)
  • Bots Bot Control managed rule group
  • Known bad inputs AWS Managed Rules (threat intel)
  • Integration Targets (memorize the list)
  • Service Scope
  • Amazon CloudFront Global edge
  • Application Load Balancer Regional
  • Amazon API Gateway Regional
  • AWS AppSync Regional (GraphQL)
  • Amazon Cognito user pools / App Runner Regional

On the Exam: WAF does NOT attach to a Network Load Balancer (NLB) or to EC2 directly — both are Layer-4 / instance-level. If a scenario uses an NLB and needs Layer-7 filtering, the design must put a WAF-capable layer (ALB or CloudFront) in front.

A Web ACL holds rules and rule groups and a default action (Allow or Block) for unmatched requests. AWS Managed Rules include the Core Rule Set (OWASP Top 10), Known Bad Inputs , SQL Database , IP Reputation , and Bot Control — using them avoids hand-writing common protections.

AWS Shield

AWS Shield is the managed Distributed Denial of Service (DDoS) protection service.

  • Feature Shield Standard Shield Advanced
  • Cost Free , always on ~$3,000/month (1-year commit) + data transfer
  • Layers 3/4 3/4/ 7
  • Protected resources All AWS edge/network EC2, ELB, CloudFront, Global Accelerator, Route 53
  • Response team No 24/7 Shield Response Team (SRT)
  • Cost protection No Yes — credits for DDoS-driven scaling charges
  • WAF Separate cost WAF included at no extra charge

On the Exam: "Protect against DDoS and get billing credits for Auto Scaling spikes during an attack" → Shield Advanced . "Basic, no-cost DDoS protection" → Shield Standard (already enabled).

AWS Network Firewall

AWS Network Firewall is a managed, stateful VPC firewall for Layer-3/4 and some Layer-7 inspection.

  • Capability Detail
  • Inspection Stateful and stateless packet filtering
  • Rules Protocol, port, IP, domain-name allow/deny lists
  • IPS/IDS Suricata-compatible signatures (intrusion prevention/detection)
  • TLS inspection Optional decrypt-and-inspect
  • Deployment Dedicated firewall subnet, often with a Transit Gateway hub
  • Scaling Fully managed, auto-scaling

Use it to stop data exfiltration , block egress to known-bad domains, or inspect east-west traffic between VPCs — things SGs and NACLs cannot do because they filter only by IP/port, not by content or domain.

AWS Firewall Manager

AWS Firewall Manager centrally applies and audits protections across an entire AWS Organization (which is a prerequisite ).

  • Manages Example Policy
  • WAF Deploy one Web ACL to every ALB org-wide
  • Shield Advanced Enforce Advanced on all in-scope resources
  • Security groups Audit and remediate overly permissive rules
  • Network Firewall Standardize VPC firewall rules
  • Route 53 Resolver DNS Firewall Org-wide DNS filtering

On the Exam: "Enforce the same WAF rules automatically on every new account/ALB across the organization" → Firewall Manager , not per-account WAF.

Where Each Layer Lives in the Request Path

Understanding the order of inspection clarifies which service answers a question. A request to a global web app typically flows: client → Shield (edge, automatic) → CloudFront → WAF (Web ACL evaluated here) → origin (ALB) → security groups → instance . WAF inspects HTTP content; Shield absorbs volumetric floods before they reach your origin; security groups and NACLs filter at the network layers; and Network Firewall sits inside the VPC inspecting east-west and egress traffic that the edge services never see.

Mapping a threat to the correct layer is the recurring skill: SQL injection is Layer 7 → WAF , a 100-Gbps UDP flood is Layer 3/4 → Shield , and outbound traffic to a malicious domain is VPC egress → Network Firewall .

WAF Rule Priority and Actions

Within a Web ACL, rules run in priority order (lowest number first), and the first terminating action — Allow or Block — stops evaluation. A Count action is non-terminating and is used to test a new rule's impact safely before switching it to Block. A common design mistake is placing a broad Allow rule above a specific Block rule, so the malicious request matches Allow first and is never blocked — order rate-based and managed protection rules above permissive rules.

Rate-Based Rules and Bot Control

A rate-based rule tracks requests per source IP over a rolling 5-minute window and blocks IPs that exceed the threshold (for example, 2,000 requests), automatically releasing them when the rate subsides. This is the standard answer for mitigating an HTTP flood / Layer-7 DDoS at the application tier, complementing Shield's network-layer defense. For automated and targeted bots (scrapers, credential stuffing), the Bot Control managed rule group adds detection beyond simple rate limiting.

Service Selection Cheat Sheet

  • Threat / Need Service
  • SQL injection, XSS, bad inputs AWS WAF
  • Volumetric Layer 3/4 DDoS, free Shield Standard
  • Layer 7 DDoS + cost protection + SRT Shield Advanced
  • Inspect/block VPC egress by domain Network Firewall
  • Org-wide enforcement of the above Firewall Manager
  • Filter DNS queries to bad domains Route 53 Resolver DNS Firewall

Common Trap: WAF and Shield are complementary, not interchangeable. A question that asks to stop SQL injection is never solved by Shield, and one asking for DDoS cost protection is never solved by WAF alone.