Study guide

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB

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

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB

Key Takeaways Explain This Topic AI

Application Load Balancer (ALB) operates at Layer 7 (HTTP/HTTPS) and supports path-based, host-based, header, query-string, and source-IP routing plus WebSocket and HTTP/2.

Network Load Balancer (NLB) operates at Layer 4 (TCP/UDP/TLS), gives one static IP per Availability Zone, preserves the client source IP, and scales to millions of requests per second.

Gateway Load Balancer (GWLB) operates at Layer 3, uses GENEVE encapsulation on port 6081, and transparently inserts third-party firewall/IDS/IPS appliances.

Cross-zone load balancing is on by default and free on ALB but off by default on NLB, where it incurs inter-AZ data charges when enabled.

Connection draining (deregistration delay, default 300s) lets in-flight requests finish before a target is removed.

Last updated: June 2026

Quick Answer: ALB = Layer 7 HTTP/HTTPS with content-based routing. NLB = Layer 4 TCP/UDP/TLS with static IPs and source-IP preservation. GWLB = Layer 3 transparent insertion of third-party security appliances. The SAA-C03 (Solutions Architect Associate) exam tests which load balancer fits a scenario more than how to configure one.

Why Resilient Architects Care About ELB

Elastic Load Balancing (ELB) is the front door for nearly every resilient design in Domain 2. It distributes incoming traffic across multiple targets — EC2 (Elastic Compute Cloud) instances, IP addresses, AWS Lambda functions, or ECS (Elastic Container Service) tasks — spread across two or more Availability Zones (AZs). When a target or an entire AZ fails, the load balancer stops routing to it within a few health-check intervals, so users never see the failure. ELB is a regional, managed, auto-scaling service: you address it by DNS name (or static IP for NLB), never by a single instance IP.

Application Load Balancer (ALB)

The ALB terminates and inspects HTTP/HTTPS, so it can route on request content . Listener rules are evaluated in priority order and route matching requests to a target group .

  • Routing condition Example rule Use case
  • Path-based /api/* → API target group Microservice splitting
  • Host-based shop.example.com → Shop group Multiple sites, one ALB
  • HTTP header X-Platform: mobile → Mobile group A/B testing
  • Query string ?lang=de → DE group Localization
  • Source IP 10.0.0.0/8 → Internal group Split internal vs. public

ALB extras tested on the exam: native WebSocket and HTTP/2 , SSL/TLS termination using ACM (AWS Certificate Manager) certs, SNI (Server Name Indication) for multiple certs on one listener, built-in Cognito/OIDC authentication , sticky sessions via the AWSALB cookie, and integration with AWS WAF (Web Application Firewall) . ALB uses dynamic private IPs, so a client cannot whitelist a fixed IP — a frequent exam trap.

Network Load Balancer (NLB)

The NLB works at Layer 4. It does not read HTTP content; it forwards TCP, UDP, TLS, or TCP_UDP flows with ultra-low latency. Three properties drive exam answers:

Static IP per AZ — one per enabled subnet, and you can attach an Elastic IP . This is the only ELB that gives a fixed IP clients can whitelist.

Source-IP preservation — targets see the real client IP (ALB rewrites it; targets see the ALB's IP unless they read X-Forwarded-For ).

Scale and latency — millions of requests per second with single-digit-millisecond latency, ideal for gaming, IoT, and custom TCP protocols.

A common pattern is NLB in front of an ALB : the NLB provides the static/Elastic IP an enterprise firewall whitelist requires, and the ALB does Layer 7 routing behind it.

Gateway Load Balancer (GWLB)

The GWLB is for inserting third-party virtual appliances (next-gen firewalls, IDS/IPS, deep-packet inspection) transparently into the traffic path. It pairs a Layer 3 gateway with a load-balancer fleet, using GENEVE encapsulation on UDP port 6081 . Traffic flows in → GWLB → appliance → back to GWLB → original destination, all invisible to the application. Memorize "third-party security appliance + GENEVE + port 6081 → GWLB."

Side-by-Side

  • Capability ALB NLB GWLB
  • OSI layer 7 4 3
  • Static IP / EIP No (DNS only) Yes Via endpoints
  • Lambda target Yes No No
  • AWS WAF Yes No No
  • Preserves client IP No (header) Yes Yes
  • Typical use Web apps, APIs Extreme perf, static IP Inline appliances
  • Cross-Zone Load Balancing and Health Checks

With cross-zone load balancing , every node spreads traffic across all registered targets in all enabled AZs, not just its own AZ. ALB has it on by default and free ; NLB has it off by default and charges for inter-AZ data when enabled. Health checks (healthy/unhealthy thresholds, interval, timeout) decide which targets receive traffic; an unhealthy target is drained and gets no traffic until it passes again. Connection draining (deregistration delay, default 300 seconds) lets in-flight requests complete before a target is removed during a deploy or scale-in.

On the exam, "clients dropped mid-request during deployment" points to tuning the deregistration delay.

Target Groups, Listeners, and Common Exam Traps

ELB routing is built from three objects you should be able to name. A listener checks for connections on a protocol and port (e.g., HTTPS:443). Listener rules (ALB only) evaluate conditions in priority order and forward to a target group . A target group holds the registered targets, the target type (instance, IP, Lambda, or ALB), and the health-check settings. One ALB can host many listeners, each with many rules, fanning out to many target groups — that is what makes a single ALB able to front an entire microservice estate.

Health-Check Tuning

  • Setting Default Effect
  • Healthy threshold 5 (NLB 3) Consecutive passes to mark a target in service
  • Unhealthy threshold 2 Consecutive failures to mark it out of service
  • Interval 30s (NLB 30s) Time between checks
  • Timeout 5s How long a single check may take
  • Success codes 200 Which HTTP codes count as healthy (ALB)

Fast detection wants a low interval and low unhealthy threshold; stability wants the opposite — the exam often asks which to change so a flapping instance is removed faster.

Frequently Tested Distinctions

Static IP needed → NLB (never ALB). Lambda or WAF needed → ALB (never NLB).

Preserve client IP at the target without parsing headers → NLB; with ALB the target must read the X-Forwarded-For header.

TLS offload to free target CPU → terminate TLS at the ALB/NLB with an ACM certificate; end-to-end encryption → re-encrypt to targets or use NLB TCP pass-through.

One static entry point + Layer 7 routing → NLB in front of ALB.

Sticky sessions keep a user pinned to one target via the AWSALB cookie (duration-based) or an application cookie — useful for stateful sessions, but it can unbalance a fleet, so prefer externalizing session state to ElastiCache or DynamoDB where possible.

Keeping these mappings crisp lets you answer most ELB scenarios in seconds: read the hard constraint (static IP, Lambda, WAF, source-IP, GENEVE appliance), and the correct load balancer falls out immediately.