Load Balancer SSL Certificate Redirect for AIQ

Use this guidance when AIQ traffic is routed through a load balancer that terminates SSL/TLS or redirects HTTP traffic to HTTPS. Keep the certificate, redirect, and application URL configuration aligned so users and test nodes reach the correct endpoint.

Configuration checks

Install the current certificate chain on the load balancer and confirm it includes intermediate certificates.
Redirect HTTP to HTTPS only when the target AIQ URL and ports are correct.
Confirm AIQ base URL, proxy headers, and forwarded protocol settings match the load balancer configuration.
Verify that test nodes, integrations, and CI/CD jobs use the same externally reachable URL.
Review certificate expiration, DNS, firewall, and health-check behavior.

Validation workflow

Open the AIQ URL from a user network and from any test-node network that must reach it.
Confirm there are no redirect loops or mixed-content warnings.
Run a login smoke test and a small execution through the load-balanced URL.
Document certificate owner, renewal date, DNS name, and load balancer rule.

Last updated: October 8, 2026