The Hybrid Data Pipeline server certificate may need to be updated if a CA certificate expires or if you are introducing a new CA certificate for other reasons. The process for updating CA certificates varies, depending on your deployment scenario and the version of your Hybrid Data Pipeline server.

Load balancer or non-load balancer deployments on Linux with Hybrid Data Pipeline 4.6.1.2057 or later

If you are running Hybrid Data Pipeline 4.6.1.2057 or later, you should use the update_server_cert.sh script to update your SSL certificate for Linux deployments. This script may be used to update the certificate for load balancer and non-load balancer deployments. For details, see Updating SSL certificates with the update server cert script.

Docker deployments with 4.6.1 versions of Hybrid Data Pipeline

If you deployed Hybrid Data Pipeline with Docker, you must redeploy the server on Docker using the new SSL certificate. This applies to all 4.6.1 versions of the server. For details, see Updating SSL certificates for Docker deployments.

Load balancer deployment on Linux with Hybrid Data Pipeline 4.6.1.1930 or earlier

If you have a load balancer deployment of Hybrid Data Pipeline 4.6.1.1930 or earlier, then you may manually update the SSL certificate as described in Updating SSL certificates manually.

Non-load balancer deployment on Linux with Hybrid Data Pipeline 4.6.1.1930 or earlier

If you have a deployment of Hybrid Data Pipeline 4.6.1.1930 or earlier on Linux that does not use a load balancer (also referred to as a non-load balancer deployment), then you must run an upgrade installation of Hybrid Data Pipeline to update the SSL certificate. For details, see Updating SSL certificates with an upgrade installation.