configuring-load-balancers

Generate load balancer configurations for ALB, NLB, Nginx, and HAProxy.

2.6k|379|Updated Oct 10, 2025

Search Tags:#DevOps #traffic management #Nginx #NLB #HAProxy #load balancer #ALB

Ready to run

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus --skill configuring-load-balancers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: configuring-load-balancers
Source: https://github.com/jeremylongshore/claude-code-plugins-plus/tree/main/plugins/devops/load-balancer-configurator/skills/load-balancer-configurator
Command: npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus --skill configuring-load-balancers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill enables Claude to generate complete and production-ready configurations for various load balancers. It supports ALB, NLB, Nginx, and HAProxy, providing a streamlined approach to infrastructure automation and DevOps tasks, ensuring optimal traffic distribution and high availability.

Core Features & Use Cases

Multi-Type Configuration: Generate configs for ALB, NLB, Nginx, and HAProxy.
Traffic Distribution: Configure rules, listeners, and target groups for efficient load balancing.
Health Checks: Implement robust health checks to ensure traffic is routed to healthy instances.
Use Case: Configure an Nginx load balancer to distribute traffic between two backend servers, ensuring high availability and performance.

Quick Start

User request: "Configure an Nginx load balancer to distribute traffic between two backend servers on ports 8080 and 8081."

The skill will:

Generate an Nginx configuration file that includes upstream definitions for the two backend servers.
Present the complete Nginx configuration file to the user.

Frequently Asked Questions about configuring-load-balancers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure a load balancer to distribute traffic across backend servers?▼

Load balancer configuration distributes incoming traffic across multiple backend servers using listeners, target groups, and routing rules. ALB, NLB, Nginx, and HAProxy each support this through upstream definitions, health checks, and port/protocol specifications to ensure high availability and optimal performance.

What's the difference between ALB, NLB, Nginx, and HAProxy for load balancing?▼

ALB and NLB are AWS managed services; ALB routes on Layer 7 (application), NLB on Layer 4 (transport). Nginx and HAProxy are open-source software load balancers offering fine-grained control and multi-environment flexibility. Choose based on cloud provider, routing complexity, and infrastructure automation requirements.

Can I generate load balancer configurations compatible with Terraform or CloudFormation?▼

Yes. Production-ready configurations for ALB, NLB, Nginx, and HAProxy can be generated with explicit Terraform and CloudFormation compatibility, enabling infrastructure-as-code workflows for consistent deployment, modification, and version control across environments.

How do health checks work in load balancer configuration?▼

Health checks monitor backend server status by testing endpoints at regular intervals. Load balancers route traffic only to healthy instances, automatically removing failed servers and restoring them when they recover, ensuring requests reach only responsive targets.

Do I need to configure load balancing differently for changing traffic patterns?▼

Load balancer configurations adapt to traffic pattern changes through adjustable routing rules, listener policies, target group settings, and health check parameters. Regenerating or modifying configurations handles new deployment environments and evolving traffic distribution requirements.

What security considerations apply when configuring a load balancer?▼

Load balancer security includes protocol selection (HTTP/HTTPS), listener rules restricting access, health check endpoint protection, and backend target isolation. Generated configurations include security review guidance and testing considerations for production deployment.