Course contentsShow
← Cloud and Infrastructure
Lesson 2368 of 2,98951. Network SecurityFree lesson

AWS WAF Fundamentals

Overview of AWS WAF architecture, integration with CloudFront and ALB, and basic concepts.

AWS WAF Fundamentals

What you'll learn: How AWS WAF is architected, where it sits in your infrastructure, and the basic building blocks you use to configure web application protection.

Architecture Overview

AWS WAF is a managed service that inspects HTTP/HTTPS requests before they reach your application. Think of it as a security checkpoint at the entrance of your building—it examines every visitor (request) before allowing them inside.

Where AWS WAF Lives

AWS WAF integrates directly with two critical AWS services:

  • CloudFront (CDN): WAF rules execute at AWS edge locations globally, filtering malicious traffic before it crosses the internet to your origin servers
  • Application Load Balancer (ALB): WAF rules run regionally, protecting applications behind your load balancer

This integration is transparent—your application code doesn't change. WAF simply sits in the request path, inspecting and allowing or blocking traffic based on your rules.

Basic Concepts

AWS WAF uses a hierarchical structure:

  1. Web ACLs (Access Control Lists): The top-level container that defines your entire filtering logic
  2. Rules: Individual conditions that inspect request attributes (IP addresses, headers, URI paths, etc.)
  3. Rule Groups: Collections of related rules you can manage together

When a request arrives, AWS WAF evaluates it against your Web ACL's rules in priority order. Each rule produces an action: Allow, Block, or Count (monitor-only mode).

Regional vs. Global

  • CloudFront WAFs are global resources
  • ALB WAFs are regional resources tied to a specific AWS region

Key Takeaway: AWS WAF acts as a transparent inspection layer between the internet and your application, integrating natively with CloudFront and ALB to filter malicious requests using Web ACLs composed of ordered rules.