# TLS Termination

TLS termination is the process of ending a client’s encrypted TLS connection at an intermediary, which decrypts traffic before forwarding it to a backend.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/tls-termination

> A load balancer, reverse proxy, or edge service can terminate TLS to centralize certificate management and inspect application traffic. The connection from that intermediary to the backend is a separate design decision: it can use plaintext or a new TLS connection, with different security and operational consequences.

Practice exams covering TLS Termination: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 7 key aspects of TLS Termination

TLS termination centralizes encrypted ingress while making backend encryption, identity verification, application visibility, and ingress resilience explicit design choices.

1. **Explicit encryption boundary**: The TLS endpoint can read the decrypted application data. Identify this trust boundary explicitly rather than assuming HTTPS at the public endpoint protects every subsequent network segment.
2. **Independent frontend and backend connections**: Client-facing TLS and backend transport are configured separately. Use plaintext only where permitted, or establish backend TLS when encryption is required on that segment.
3. **Centralized certificate and TLS policy management**: Termination consolidates certificate deployment, renewal, and supported TLS policies at ingress. Monitor expiration and test changes against actual client capabilities.
4. **Application-layer visibility**: Decryption enables supported intermediaries to inspect HTTP requests for routing, filtering, or authentication. A transport-layer TLS terminator does not automatically become an application-layer load balancer.
5. **Termination versus passthrough**: Termination ends the client’s TLS session at the intermediary; passthrough leaves that session to the backend. Choose passthrough when the backend must directly participate in the original handshake, accepting reduced routing visibility.
6. **Authentication is separate from encryption**: Backend TLS does not guarantee that the intermediary validates backend identity. Likewise, terminating mutual TLS at a proxy authenticates the client there, so any identity forwarded to applications needs a trusted, protected path.
7. **Resilient termination capacity**: Distribute termination across failure domains and account for TLS handshake load as well as request throughput. Healthy backends cannot compensate for an unavailable or misconfigured TLS ingress.

## Cloud services for TLS Termination

CloudFront can terminate viewer TLS at the edge and establish HTTPS connections to an Application Load Balancer origin. The ALB then terminates that connection, applies HTTP-aware routing, and connects to application targets using HTTP or HTTPS. ACM provides certificates for supported termination endpoints, subject to each service’s regional requirements. For transport-layer workloads, a Network Load Balancer offers either TLS termination or TCP passthrough. Choose these paths according to inspection and authentication requirements, and verify backend certificate-validation behavior rather than treating every encrypted connection as authenticated.

- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudFront terminates viewer TLS at its edge locations and uses separate connections to origins. Configure viewer and origin protocol policies independently; HTTPS connections to custom origins require certificates that satisfy CloudFront’s certificate validation requirements.

## TLS Termination exam questions

Real practice exam questions on TLS Termination, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A financial services company is deploying an HTTPS application across three Availability Zones. Partner networks must allowlist one fixed public IPv4 address per Availability Zone before they can access the application. All partners use the same application hostname, and requests to /payments/* and /reports/* must reach different groups of Amazon EC2 instances. The company requires centralized management of the client-facing TLS certificate and encryption on every network segment between clients and application instances. The ingress solution must tolerate replacement of load balancer nodes without changes to partner allowlists. The company does not want to operate proxy instances or maintain automation that reconciles load balancer IP addresses.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Deploy an internet-facing Network Load Balancer with an Elastic IP address in each Availability Zone and a TCP listener on port 443. Forward to an internal Application Load Balancer registered in an ALB-type target group on port 443. Configure the Application Load Balancer with an HTTPS listener, the client-facing certificate, and path-based rules that forward to HTTPS target groups.

**Explanation:** The Network Load Balancer supplies fixed public IPv4 addresses and passes the client TLS connection through its TCP listener to the Application Load Balancer. The Application Load Balancer terminates TLS using the centrally managed certificate, evaluates the URL path, and establishes separate HTTPS connections to application targets. Registering the Application Load Balancer as an ALB-type target avoids maintaining its changing node IP addresses.

### Question 2 (ANS-C01)

**Question:**

A financial services company is migrating a transaction API to Amazon EC2 instances in private subnets across three Availability Zones. Client applications use mutual TLS (mTLS) with certificates issued by the company's private certificate authority. Security policy requires each application instance to verify the client's possession of its private key during the TLS handshake. The application cannot accept client identity conveyed through HTTP headers, and decrypted transaction data must not be available to the load balancer. The company needs a managed load balancing solution that distributes connections across healthy instances and supports an Auto Scaling group. Which configuration meets these requirements?

**Correct answer:** Configure a Network Load Balancer with a TCP listener on port 443 and a TCP target group on the application's TLS port. Configure each application instance to terminate TLS and validate client certificates.

**Explanation:** The TCP listener and TCP target group forward the encrypted TLS traffic without terminating TLS at the NLB. Each application instance participates directly in the client's mTLS handshake and verifies proof of possession of the client private key. The NLB can distribute connections to healthy Auto Scaling group instances across Availability Zones.

## Practice TLS Termination in a full exam

Questions on TLS Termination in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 2 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 1 question

## What is TLS Termination

TLS termination defines where an encrypted connection ends and where its protected application data becomes available for processing. When a load balancer terminates TLS, it presents a server certificate, negotiates protocol versions and cryptographic parameters with the client, and decrypts incoming requests. It then forwards those requests over a separate backend connection. Responses travel through the intermediary and are encrypted on the client-facing connection.

This arrangement separates public-facing security configuration from application deployment. Engineers can manage certificates, private-key access, renewal, and TLS security policies at a smaller number of ingress points rather than on every application instance. Application-aware intermediaries can inspect decrypted HTTP requests for host-based or path-based routing, authentication, and web application firewall evaluation. TLS termination alone does not provide these capabilities; the intermediary must also support them.

The backend connection determines the remaining encryption boundary. With TLS offload to a plaintext backend, a browser might connect over HTTPS to a load balancer that forwards HTTP to private application instances. This reduces backend certificate administration, but traffic on that backend segment is unencrypted. A private subnet does not itself provide encryption, so this design must match the workload’s threat model and compliance requirements.

With re-encryption, the intermediary terminates the client connection and establishes a separate TLS connection to the backend. Both network segments are encrypted, but the intermediary can still read the application data. This is not one uninterrupted client-to-application TLS session. Also distinguish encryption from backend authentication: a proxy must validate the backend certificate and expected identity to authenticate that backend. Some managed load balancers encrypt backend traffic without performing that validation.

TLS passthrough is the contrasting design. A transport-layer load balancer forwards the encrypted connection without terminating it, leaving certificates and TLS processing on the backend. Passthrough preserves the client-to-backend TLS handshake and can be necessary when the application must directly authenticate client certificates. However, the forwarding load balancer cannot inspect encrypted HTTP paths or headers. Do not assume that every load balancer supports application routing simply because it accepts traffic on port 443.

For example, an AWS Application Load Balancer can terminate HTTPS and route requests to HTTP or HTTPS target groups. A Network Load Balancer can terminate TLS using a TLS listener, or pass TLS through using a TCP listener. Its TLS listener does not support mutual TLS; use TCP passthrough when backend applications must perform the mutual TLS handshake. Application Load Balancer mutual TLS features are different: its client-certificate passthrough mode still terminates TLS and forwards certificate information in HTTP headers rather than preserving the original encrypted connection.

Termination also changes identity and application context. A backend sees the proxy’s connection rather than the original TLS session. Configure trusted forwarding headers so applications correctly recognize the original scheme and client information, and prevent untrusted clients from bypassing the proxy or supplying authoritative identity headers. Otherwise, HTTPS redirects, secure-cookie handling, logging, or authorization can behave incorrectly.

For high availability, use redundant termination capacity across failure domains and distribute requests only to healthy targets. Test certificate renewal, hostname coverage, client compatibility, handshake capacity, and backend encryption independently. On an exam or in a design review, identify where TLS must end, who must authenticate whom, whether HTTP inspection is required, and which network segments must remain encrypted before selecting the listener and target protocols.

## Learn TLS Termination in lessons

1 short lesson on TLS Termination in 1 certification course.

- SAP-C03: TLS Termination: ingress encryption and trust boundaries (Premium), https://app.blowstack.com/lessons/tls-termination-ingress-encryption-and-trust-boundaries-sap-c03
