elb

Automate AWS Elastic Load Balancer and target group management via AWS CLI.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/david-2814/claw-aws --skill elb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elb
Source: https://github.com/david-2814/claw-aws/tree/main/skills/elb
Command: npx skills add https://github.com/david-2814/claw-aws --skill elb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplify the complex and error-prone process of creating, configuring, and maintaining Elastic Load Balancers (ALB, NLB, and CLB), their target groups, listeners, and health checks using the AWS CLI.

Core Features & Use Cases

  • Create and configure Application, Network, and Classic Load Balancers.
  • Manage target groups and listeners, including health checks, routing rules, and health status across environments.
  • Inspect, modify, and troubleshoot existing load balancers and their attributes in multi-account or multi-region setups.

Quick Start

Run the elb skill in your OpenClaw workspace to list and manage your AWS load balancers using the AWS CLI.

Frequently Asked Questions about elb

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

FAQPage Schema
How do I manage AWS Elastic Load Balancers using the AWS CLI?

You can manage AWS Elastic Load Balancers using the AWS CLI by automating provisioning, updating, and auditing of ALB, NLB, and CLB configurations, target groups, listeners, and health checks across VPCs while enforcing safe guardrails.

What is the best way to configure ALB target groups and listeners across multiple VPCs?

Configuring ALB target groups and listeners across VPCs is achieved by applying automated AWS CLI commands to provision routing rules and health checks, ensuring consistent setup across multi-account or multi-region environments.

Do I need specific IAM permissions to configure Network Load Balancers with the AWS CLI?

Yes, configuring Network Load Balancers with the AWS CLI requires appropriate IAM permissions and AWS CLI presence to execute commands, while built-in safe guardrails prevent destructive actions during management.

Why does my Classic Load Balancer configuration fail when updating via AWS CLI?

Updating a Classic Load Balancer configuration via AWS CLI can fail if appropriate IAM permissions are missing or if safe guardrails restrict the action, though the process is designed to troubleshoot and modify existing attributes securely.

Can I inspect and troubleshoot existing load balancer health checks in a multi-region setup?

Yes, you can inspect and troubleshoot existing load balancer health checks in a multi-region setup by running AWS CLI commands to audit health status and modify attributes across environments.

When should I not use the AWS CLI for Elastic Load Balancer management?

You should not use the AWS CLI for Elastic Load Balancer management if you lack appropriate IAM permissions or AWS CLI presence, as safe guardrails may restrict automated provisioning and updating actions.