SSL and TLS termination
TLS (Transport Layer Security, the newer name for SSL) is an encryption standard: it is what puts the s in https:// and the padlock in the browser. TLS termination means the load balancer decrypts the traffic and needs a certificate for your site. TLS passthrough means the load balancer forwards the encrypted traffic unopened, and your own server decrypts it with its own certificate.
When to use each mode
Only Terminate lets the load balancer read requests, so path and header rules work only with HTTP and HTTPS.
How it works
Terminate (L7 HTTPS):
- The client opens
https://to the load balancer’s hostname, or to your own domain. - The load balancer presents a certificate that IBEE manages, and decrypts the request.
- It forwards the request to a backend without encryption, over plain HTTP to the backend’s port.
- It encrypts the backend’s answer and sends it to the client.
Passthrough (L4 TLS passthrough):
- The client connects to the load balancer’s hostname on port
8443and starts a TLS handshake. - The load balancer reads only the hostname the client asks for in the handshake (called SNI, Server Name Indication) and forwards the encrypted connection to a backend.
- The backend presents its own certificate and decrypts the traffic. The load balancer never sees the content.
Traffic between the load balancer and your backends is not encrypted. The Encrypt traffic from the load balancer to this backend option is saved, but not applied yet. If that hop must be encrypted, use TLS passthrough, so that only your backend decrypts the traffic.
Before you begin
- A verified organization and room in your plan for another load balancer. See Create a load balancer.
- Backends that serve plain HTTP on their port, for Terminate. For Passthrough, backends that serve TLS and hold a certificate.
- For your own domain: access to your domain’s DNS settings, and an API token with
load-balancer.write. The portal has no custom domain field yet.
Create an HTTPS load balancer in the portal
Choose the protocol
Set Layer to Layer 7 and Protocol to HTTPS (“Terminate TLS with a managed certificate.”). These are the defaults.
For passthrough instead, set Layer to Layer 4 and Protocol to TLS passthrough (“Preserve end-to-end TLS without termination.”).
Verify
Open the Public host URL in a browser and check for the padlock, or run:
You should see the certificate’s subject and issuer, then your app’s HTTP status.
For TLS passthrough, check that your backend’s certificate is presented:
Use your own domain
An L7 HTTPS load balancer can also answer on one domain of yours, such as shop.example.com, with a certificate IBEE issues for that domain automatically. This is available through the API only.
Create the CNAME record first
At your DNS provider, create a CNAME record for your domain that points directly to cname.lb.ibee.ai:
IBEE checks this record when you send the request, so it must exist and resolve first. Check it with dig +short CNAME shop.example.com, which should print cname.lb.ibee.ai.
A domain can belong to only one load balancer. A root domain such as example.com usually can’t have a CNAME record at most DNS providers, so use a subdomain such as www or shop.
Certificates
- IBEE manages every certificate. You don’t upload or renew it.
- You can’t upload your own certificate yet. The API’s
"certificate_source": "custom"withcert_pemandkey_pemis refused. - TLS passthrough needs your certificate on every backend. The load balancer picks the backend by the hostname the client sends (SNI), and it matches only the load balancer’s own hostname. Clients must connect to that hostname, so the backends’ certificate must be valid for it, or the clients must be set up to trust it.
Limits
Security tips
- Don’t send passwords or personal data over the HTTP protocol. Use HTTPS so traffic is encrypted between the client and the load balancer.
- The hop from the load balancer to your backends is unencrypted, and it reaches them at their public addresses. When data must stay encrypted all the way to your server, use passthrough.
