Build Server Load Balancer configurations with listeners, health checks, backend servers, and session persistence.
Last verified: May 2026
Build SLB configurations with listeners, health checks, backend server groups, session persistence, and HTTPS certificates.
Required Fields
loadBalancerNamelistenersOutput will appear here...Alibaba Cloud Server Load Balancer (SLB) handles TCP, UDP, HTTP, and HTTPS load balancing with health checks, session persistence, and certificate management. The Alibaba SLB Config Builder produces complete configurations, listeners, backend server groups, health checks, certificate bindings, output as `alicloud_slb` and related Terraform resources.
Classic SLB is the original layer-4/layer-7 load balancer; ALB (Application Load Balancer) is the newer layer-7-only product with richer routing rules, host-based and path-based forwarding, and improved HTTP/2 support. For pure layer-4 (TCP/UDP), use Classic SLB. For modern HTTP workloads with routing requirements, use ALB. Classic SLB also exists as a layer-7 option, but ALB has more capabilities for new deployments.
With persistence enabled, requests from the same client go to the same backend. This is useful for legacy stateful apps but reduces effective load distribution, a hot client lands on one backend. For new workloads, prefer stateless backends with shared session store; for legacy, accept the trade-off.
Your team launches a new public API behind a fresh SLB. During the first deploy, 502 errors briefly spike, health checks running every 2 seconds with a 1-retry threshold remove backends faster than the rolling deploy can replace them. You regenerate the SLB config with a 10-second interval and 3-retry threshold, deploy the change, and subsequent deploys no longer trigger user-visible errors.
The builder collects SLB type, name, region, internet/intranet flag, and a list of listeners (port, protocol, certificate, backend server group). Each backend server group has members, weights, and health check parameters. Output is `alicloud_slb`, `alicloud_slb_listener`, `alicloud_slb_server_group`, and `alicloud_slb_server_group_server_attachment` Terraform resources with correct dependencies.
Set idle timeout to 60+ seconds for WebSocket and long-polling workloads. The default 30s cuts long-lived connections and looks like a flapping backend from the client's view.
Use HTTP/HTTPS health checks (not TCP) when possible, they verify the application is actually responding, not just that the port is open. A web server returning 502 for every request still has an open port; HTTP checks catch this.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.