SSL/TLS Termination at ALB
You'll learn how Application Load Balancers decrypt HTTPS traffic for you, simplifying security management and reducing backend server workload.
What Is SSL/TLS Termination?
SSL/TLS termination means the load balancer handles all the encryption/decryption work for HTTPS connections—it's like a security checkpoint at a building entrance. Visitors (clients) use secure badges (SSL/TLS) to enter, but once inside the building, employees can communicate freely. The ALB decrypts incoming encrypted traffic, inspects it, makes routing decisions, then forwards requests to backend targets (often over plain HTTP internally).
Why Terminate SSL at the ALB?
Instead of managing certificates on every backend server, you centralize them at the load balancer. This means:
- One place to update certificates when they expire
- Reduced CPU load on your application servers (no encryption overhead)
- Centralized security policy management
- Simpler compliance and auditing
How It Works
You attach an SSL/TLS certificate (from AWS Certificate Manager or uploaded) to your ALB listener on port 443 (HTTPS). You configure a security policy that defines which TLS versions and cipher suites are acceptable—think of this as setting the "strength requirement" for secure connections.
The ALB then:
- Accepts HTTPS connections from clients
- Decrypts the traffic using the certificate
- Routes requests based on HTTP headers/paths (concepts you learned earlier)
- Forwards to targets (often over HTTP internally, though re-encryption is possible)
Key Takeaway: SSL/TLS termination at ALB offloads encryption work from your servers, centralizes certificate management, and lets you enforce consistent security policies—all while still enabling the layer 7 routing features you've learned.