copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2018-11-12 |
ssl offload, cipher |
loadbalancer-service |
{{site.data.keyword.attribute-definition-list}}
{: #ssl-offload-with-ibm-cloud-load-balancer}
For all incoming HTTPS connections, the load balancer service ends the SSL connection and establishes a plain text HTTP communication with the back-end server. CPU-intensive SSL handshakes and encryption or decryption tasks are shifted away from the back-end servers, allowing them to use all their CPU cycles for processing application traffic.
An SSL certificate is required for the load balancer to perform SSL offload tasks. You can use a pre-existing SSL certificate or purchase a new one, and manage it through the SSL Certificates page{: external}.
{: #ssl-cipher-suites}
The load balancer service supports TLS version 1.2 with SSL offload.
The following SSL ciphers are supported by your load balancer:
- ECDHE-RSA-AES256-GCM-SHA384
- ECDHE-RSA-AES256-SHA384
- AES256-GCM-SHA384
- AES256-SHA256
- ECDHE-RSA-AES128-GCM-SHA256
- ECDHE-RSA-AES128-SHA256
- AES128-GCM-SHA256
- AES128-SHA256
If your load balancer has one or more HTTPS front-end application ports (protocols) configured, by default, all these predefined SSL ciphers are enabled for your load balancer.
You can choose to enable different SSL ciphers for your load balancer if needed. For more information, see Choosing a preferred cipher suite for your HTTPS application. {: note}