Dev
Load Balancer Config Prompt Generator
A load balancer without health checks keeps sending requests to crashed backends until every user sees errors. Without graceful draining it drops in-flight requests every deploy. This tool generates a fill-in prompt that asks an AI assistant to configure your chosen balancer with both. Pick the tool — nginx upstream, HAProxy, AWS ALB, or Traefik — and the balancing method: Round robin, Least connections, or IP hash / sticky. The prompt asks for the backend pool, an explanation of when the algorithm fits, active health checks with automatic rotation removal, connection and retry timeouts, TLS termination with `X-Forwarded-*` headers, and a graceful drain procedure. Paste the prompt into your assistant and adapt the backend hostnames and ports.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick the load balancer tool.
- Choose the balancing method.
- Click Generate to build the prompt.
- Paste it into your AI assistant and adapt the backend list.
Use Cases
- •Getting a production-ready load balancer config from an AI assistant
- •Choosing between round-robin, least-connections, and sticky sessions
- •Adding health checks so dead backends leave rotation
- •Configuring graceful backend draining for deploys
- •Standardising load balancer setup across tools
Tips
- →Always add active health checks so dead backends drop out.
- →Use least connections for long-lived or uneven requests.
- →Forward X-Forwarded-* headers so backends see the real client.
- →Test graceful draining before relying on it for deploys.
FAQ
which balancing method should I pick
Round robin is fine for uniform, short-lived requests. Least connections suits uneven or long-lived requests by routing to the least busy backend. IP hash or sticky sessions keep a client on one backend when session affinity is required. The prompt asks the assistant to explain which fits.
why are health checks critical
Without active health checks the balancer continues sending traffic to a crashed backend, so users hit errors until you intervene manually. Health checks detect failure automatically and remove the backend from rotation — the core safety mechanism of any load balancer.
what does graceful draining do for deploys
Draining stops the balancer from sending new connections to a backend while letting existing requests complete before shutdown. Without it, a rolling deploy kills in-flight requests mid-response. The prompt makes draining a required part of the configuration.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.