Instiq
Chapter 4 · Network Implementation·v2.1.0·Updated 6/14/2026·~11 min

What's changed: In-scope coverage: added compute/scaling/storage (EC2 Auto Scaling/AWS Auto Scaling/ECS/Fargate/Lambda/S3)

4.2Implementing and Choosing Load Balancers

Key points

Distribute traffic—understand ALB (L7), NLB (L4), GWLB, target groups/health checks, and cross-zone load balancing. Choose by layer and requirements.

Elastic Load Balancing offers ALB (application), NLB (network), and GWLB (gateway). Choose by the OSI layer they operate at and your requirements.

4.2.1Three load balancer types

Diagram of choosing a load balancer: ALB at layer 7 (HTTP/HTTPS) with path/host routing, WAF, TLS, redirects for web apps/microservices; NLB at layer 4 (TCP/UDP/TLS) with ultra-low latency, static IP, millions of connections, preserving source IP for non-HTTP/extreme scale; GWLB as a layer-3 gateway that transparently inserts virtual appliances (firewalls, IDS/IPS) for traffic inspection.
Choosing a load balancer
  • ALB (L7): HTTP/HTTPS. Path/host-based routing, WAF, TLS. For web apps/microservices.
  • NLB (L4): TCP/UDP/TLS. Ultra-low latency, static IP, massive connections, preserves source IP. For non-HTTP.
  • GWLB: transparently inserts virtual appliances (firewall/IDS/IPS) to inspect traffic.
  • Target groups/health checks: group targets and automatically remove unhealthy ones.
Exam point

Common on ANS-C01: route by path/host = ALB (L7), static IP / ultra-low latency / TCP·UDP = NLB (L4), and insert appliances like firewalls = GWLB. Choose NLB when static IP is required and ALB for content-based routing.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.