Network and platform engineers
Load Balancer: How to Configure an HTTPS Load Balancer with Health Checks
Create a managed load balancer, terminate TLS, and route traffic only to healthy backends.
12 min read · Updated 2026-04-01
Prerequisites
- • At least two backend instances in a private subnet
- • TLS certificate and private key material
- • Security group permissions for frontend and backend ports
Implementation workflow
This runbook focuses on a reliable sequence for provisioning and validating the service through the cloud console.
- Open Network > Load Balancers and create a new load balancer on the target subnet.
- Create an HTTPS listener and upload or select the TLS certificate.
- Add a backend pool and register member instances on the service port.
- Configure an HTTP or TCP health monitor with interval and timeout settings.
- Associate a floating IP or DNS record and validate traffic distribution.
Validation and operator checks
After deployment, verify connectivity, security boundaries, and backup posture before promoting workloads to production.
Operator tips
- • Use dedicated health endpoints that test application dependencies.
- • Tune monitor thresholds to avoid flapping during brief spikes.
- • Perform rolling backend updates through pool member drain workflows.