TLS termination
Ending an encrypted TLS connection at a proxy or gateway, which decrypts the traffic and forwards it on to the service.
In more detail
It centralises certificate handling, but the hop behind it must be trusted or encrypted again. The gateway can then inspect and route the decrypted requests.
Examples
tls:
- hosts:
- web.example.test
secretName: web-tlsFrom there on the traffic is plain HTTP unless it is encrypted again for the next hop. Termination points define where TLS protection ends, so locate them before claiming traffic is encrypted end to end.client=proxy tls=on onward=origin retls=on shows TLS ending at a proxy and being re-established to the origin.Related terms
- TLS — The encryption that protects data travelling over a network, the S in HTTPS.
- API gateway — A server that sits in front of one or more services and handles shared concerns such as routing, authentication, rate limits and TLS for every request.
- reverse proxy — A server that receives requests on behalf of other servers and forwards them, returning their responses as if they were its own.
- Ingress controller — The reverse proxy running in a Kubernetes cluster that reads Ingress rules and routes incoming traffic accordingly.
- cert-manager — A Kubernetes add-on that requests TLS certificates, stores them as secrets and renews them before they expire.
- network edge — The outermost layer of your system, where traffic from the internet first arrives.
- Kubernetes Secret — A Kubernetes object for small sensitive values such as passwords and tokens, which pods can use as files or environment variables.
- mutual TLS — TLS in which both sides present certificates, so the server also proves who the client is.
- load balancing — Spreading requests or connections across several backend servers so no single one is overloaded and failed ones can be avoided.
- encryption in transit — Protecting data while it moves across a network, so it cannot be read (confidentiality) or altered unnoticed (integrity) on the way.
- load balancer — A server that spreads incoming requests across several copies of a service so no single copy is overloaded.
- service mesh — A layer of proxies alongside every service that handles traffic between services: routing, retries, TLS and telemetry.
- encryption — Scrambling data with a key so only someone holding the right key can read it.
- application layer — The top layer, where protocols such as HTTP, DNS and SSH give the bytes meaning as requests, answers and commands.
Taught in
- API Gateways And Proxies — Modern API Architecture: REST, GraphQL & gRPC
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Pods, Init Containers And Sidecars — Kubernetes: Production-Grade Container Orchestration
- Ingress: Controllers, Hosts, Paths And TLS — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: OOMKilled, Throttling And Evictions — Kubernetes: Production-Grade Container Orchestration
- What HTTPS Adds, And What It Does Not — Linux Fundamentals & Systems Administration
- Certificates, Chains And What A Handshake Proves — Linux Fundamentals & Systems Administration
- Forward And Reverse Proxies — Linux Fundamentals & Systems Administration
- Secure Defaults — Application Security & Threat Modeling for Engineers
- TLS And The Handshake — Application Security & Threat Modeling for Engineers
- Load Balancing And The Failure Modes It Introduces — Scalable System Design & Distributed Architecture
References
- Amazon API Gateway: What is API Gateway?
- Kubernetes: Ingress (TLS)
- Azure Architecture Center: Gateway Offloading pattern
- NGINX: configuring HTTPS servers
- OWASP Transport Layer Security Cheat Sheet
- Elastic Load Balancing: what is a load balancer
- NGINX documentation: NGINX Reverse Proxy
- RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3