Course contentsShow
← Cloud and Infrastructure
Lesson 269 of 2,9895. Load Balancing and Traffic ManagementFree lesson

TLS Termination on NLB

Implement TLS termination at the network load balancer with certificate management and SSL offloading strategies.

TLS Termination on NLB

What you'll learn: How Network Load Balancers can decrypt TLS traffic, offloading encryption work from your backend servers.

What is TLS Termination?

TLS termination means the load balancer handles the encryption/decryption of secure traffic instead of your backend servers. Think of it like a translator at a border crossing: encrypted traffic arrives, the NLB "translates" (decrypts) it, then forwards plain HTTP to your servers. This saves your servers from doing computationally expensive cryptographic work.

How NLB Handles TLS

Even though NLBs operate at Layer 4 (transport layer), they can still terminate TLS connections. You configure a TLS listener on the NLB and attach an SSL/TLS certificate (typically from AWS Certificate Manager). When a client connects via HTTPS, the NLB:

  1. Accepts the encrypted connection
  2. Decrypts the traffic using the certificate's private key
  3. Forwards unencrypted traffic to your target instances
  4. Re-encrypts responses before sending them back to clients

SSL Offloading Strategy

SSL offloading means removing the encryption burden from backend servers. Your servers receive plain HTTP traffic, process it faster, and use less CPU. The NLB handles all certificate management, renewal, and cryptographic operations. This centralizes security and simplifies server configuration—your backends don't need certificates at all.

Certificate Management

You manage certificates through AWS Certificate Manager or import your own. The NLB uses these certificates to establish secure connections with clients while maintaining the high performance and static IP benefits you learned about in previous NLB lessons.

Key Takeaway: TLS termination on NLB lets you centralize SSL/TLS decryption at the load balancer level, offloading encryption overhead from backend servers while maintaining Layer 4 performance benefits.