SSL/TLS
In one line
SSL/TLS is a security protocol that encrypts data between a client and server, enabling HTTPS.
In simple words
SSL (Secure Sockets Layer) and its successor TLS (Transport Layer Security) are protocols that encrypt communication between a client and a server. When you see the padlock icon in your browser, that means SSL/TLS is protecting your connection.
SSL is the older protocol and has been deprecated due to security vulnerabilities. TLS is the modern, secure version. However, people still commonly say "SSL certificate" when they mean "TLS certificate."
In DevOps, you obtain a certificate from a Certificate Authority (like Let's Encrypt, DigiCert) and configure your web server or Ingress to use it. The certificate contains a public key and proves the server's identity. TLS termination means the proxy handles HTTPS and forwards plain HTTP to the backend.
Example
# Get a free certificate from Let's Encrypt
certbot --nginx -d example.com
# Or configure TLS in nginx manually
# server {
# listen 443 ssl;
# ssl_certificate /path/to/cert.pem;
# ssl_certificate_key /path/to/key.pem;
# }Certbot automatically obtains and installs a Let's Encrypt TLS certificate for nginx.
How it works
- The client connects to the server and requests a secure connection.
- The server sends its TLS certificate (containing its public key).
- The client verifies the certificate with a Certificate Authority.
- Both sides agree on encryption keys and communicate securely.
Common confusions
Confused with: HTTPS
The difference: SSL/TLS is the encryption protocol; HTTPS is HTTP over SSL/TLS. HTTPS uses TLS to encrypt HTTP traffic.
Related terms
Decode error messages
Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.