aws-elb

List all Classic Load Balancers

$ aws elb describe-load-balancers

$ aws elb describe-load-balancers --load-balancer-names [lb_name]

$ aws elb describe-instance-health --load-balancer-name [lb_name]

$ aws elb register-instances-with-load-balancer --load-balancer-name [lb_name] --instances [i-xxxxxxxx]

$ aws elb deregister-instances-from-load-balancer --load-balancer-name [lb_name] --instances [i-xxxxxxxx]

$ aws elb create-load-balancer --load-balancer-name [lb_name] --listeners Protocol=HTTP,LoadBalancerPort=80,InstanceProtocol=HTTP,InstancePort=80 --subnets [subnet-id] --security-groups [sg-id]

$ aws elb delete-load-balancer --load-balancer-name [lb_name]

aws elb subcommand [options]

aws elb is a subcommand of the AWS CLI that manages Classic Load Balancers (CLB), the original Elastic Load Balancing service. Classic Load Balancers distribute incoming traffic across multiple EC2 instances in one or more Availability Zones.
CLB operates at both Layer 4 (TCP) and Layer 7 (HTTP/HTTPS), routing traffic based on application or network level information. It performs health checks on registered instances and only routes traffic to healthy targets.
Classic Load Balancers support sticky sessions, SSL termination, and integration with Auto Scaling groups for dynamic instance management.

describe-load-balancers

List load balancers and their configuration.

Create a new Classic Load Balancer.

Remove a load balancer.

Check health status of registered instances.

Add instances to a load balancer.

Remove instances from a load balancer.

Set health check parameters.

Add listener configurations.

Remove listeners.

Name of the load balancer.

List of load balancer names.

EC2 instance IDs.

Listener protocol and port mappings.

VPC subnets for the load balancer.

Security groups to assign.

Classic Load Balancers are a previous generation service. AWS recommends using Application Load Balancers (ALB) for HTTP/HTTPS or Network Load Balancers (NLB) for TCP/UDP workloads. CLB does not support path-based routing, host-based routing, or WebSocket natively. New features are not being added to CLB.

Elastic Load Balancing launched in 2009 as one of AWS's earliest services. The Classic Load Balancer was the only load balancer type until August 2016 when Application Load Balancer was introduced. Network Load Balancer followed in 2017. Classic Load Balancers remain supported but are considered legacy, with AWS encouraging migration to newer types.

aws(1), aws-elbv2(1), aws-ec2(1), aws-autoscaling(1)