Configure use when configuring load balancers including ALB, NLB, Nginx, and HAProxy. Trigger with phrases like "configure load balancer", "create ALB", "setup nginx load balancing", or "haproxy configuration". Generates production-ready configurations with health checks, SSL termination, sticky sessions, and traffic distribution rules.
72
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/load-balancer-configurator/skills/configuring-load-balancers/SKILL.mdConfigure load balancers across AWS (ALB, NLB), GCP (HTTP(S) LB, TCP/UDP LB), Nginx, and HAProxy. Generate production-ready configurations with health checks, SSL/TLS termination, path-based and host-based routing, sticky sessions, rate limiting, and traffic distribution rules for high-availability deployments.
/health returning 200)aws, gcloud)/api -> API pool, /static -> CDN), host-based routing (api.example.com -> API)nginx -t, HAProxy config check), verify traffic distribution, and confirm failover behaviornginx.conf, site configs) with upstream blocks and server directiveshaproxy.cfg) with frontend/backend sections| Error | Cause | Solution |
|---|---|---|
502 Bad Gateway | Backend server unreachable or not responding | Verify backend IPs, ports, and firewall rules; check backend service health |
SSL certificate verify failed | Certificate expired, wrong chain, or key mismatch | Verify certificate validity and chain with openssl s_client; regenerate if needed |
Target is unhealthy | Health check endpoint returning non-200 or timing out | Verify health check path returns 200; increase timeout if backend is slow to respond |
nginx: configuration file test failed | Syntax error in Nginx configuration | Run nginx -t to identify the specific error line; fix syntax and test again |
Session persistence not working | Cookie-based stickiness misconfigured or client not sending cookies | Verify cookie name matches; use IP-based affinity as fallback for non-browser clients |
${CLAUDE_SKILL_DIR}/references/errors.md for additional error handling patterns3e83543
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.