About load-balancer-setup
A skill for deploying and configuring load balancers that distribute traffic across backend servers. Its references cover HAProxy, AWS Application Load Balancer, health checks, and monitoring.
Key features
- 01HAProxy 配置参考
- 02AWS Application Load Balancer CloudFormation 指南
- 03健康检查与监控参考
- 04会话保持、限流和 TLS 建议
Use cases
- 01将流量分配到多台后端服务器
- 02为服务配置健康检查和故障切换
- 03在负载均衡器上终止 SSL/TLS
- 04监控负载均衡器指标
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ aj-geddes/ useful-ai-prompts --skill load-balancer-setupAfter installing, type/load-balancer-setupin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/aws-application-load-balancer-cloudformation.mdhaproxy-configuration.mdload-balancer-health-check-script.mdload-balancer-monitoring.mdscripts/validate-api.shtemplates/api-scaffold.yamlDetails
From the project READMELoad Balancer Setup
Table of Contents
Overview
Deploy and configure load balancers to distribute traffic across multiple backend servers, ensuring high availability, fault tolerance, and optimal resource utilization across your infrastructure.
When to Use
- Multi-server traffic distribution
- High availability and failover
- Session persistence and sticky sessions
- Health checking and auto-recovery
- SSL/TLS termination
- Cross-region load balancing
- API rate limiting at load balancer
- DDoS mitigation
Quick Start
Minimal working example:
# /etc/haproxy/haproxy.cfg
global
log stdout local0
log stdout local1 notice
maxconn 4096
daemon
# Security
tune.ssl.default-dh-param 2048
ssl-default-bind-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256
ssl-default-bind-options ssl-min-ver TLSv1.2
defaults
log global
mode http
option httplog
option denylogin
option forwardfor
option http-server-close
# Timeouts
timeout connect 5000
timeout client 50000
timeout server 50000
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| HAProxy Configuration | HAProxy Configuration |
| AWS Application Load Balancer (CloudFormation) | AWS Application Load Balancer (CloudFormation) |
| Load Balancer Health Check Script | Load Balancer Health Check Script |
| Load Balancer Monitoring | Load Balancer Monitoring |
Best Practices
✅ DO
- Implement health checks
- Use connection pooling
- Enable session persistence when needed
- Monitor load balancer metrics
- Implement rate limiting
- Use multiple availability zones
- Enable SSL/TLS termination
- Implement graceful connection draining
❌ DON'T
- Allow single point of failure
- Skip health check configuration
- Mix HTTP and HTTPS without redirect
- Ignore backend server limits
- Over-provision without monitoring
- Cache sensitive responses
- Use default security groups
- Neglect backup load balancers
Comments
Markdown supported