Enabling HTTPS

Enable HTTPS for Transformer to use secure communication.

When registered with Control Hub cloud, Transformer must use the HTTPS protocol because Control Hub cloud also uses the HTTPS protocol.

When registered with Control Hub on-premises, Transformer must use the same protocol as the Control Hub cloud on-premises installation. By default, Transformer and Control Hub on-premises use the HTTP protocol. You should use HTTPS in a production environment. HTTPS requires SSL/TLS certificates.

By default, the Control Hub web browser uses WebSocket tunneling to communicate with deployed Transformers. WebSocket tunneling ensures that your data is secure and does not require additional setup.

However, when you preview a pipeline or capture a snapshot of an active job, your source data does pass through encrypted connections beyond your corporate network into Control Hub, and then back to your web browser. If your data must remain behind a firewall due to corporate regulations, you can configure the browser to use direct engine REST APIs to directly communicate with the engines behind the firewall.

When using direct engine REST APIs, you must enable Transformer to use the HTTPS protocol. For information about enabling HTTPS for Transformer, see the Control Hub documentation.