aws-elbv2

List all Application and Network Load Balancers

$ aws elbv2 describe-load-balancers

$ aws elbv2 describe-target-groups

$ aws elbv2 describe-target-health --target-group-arn [arn:aws:elasticloadbalancing:region:account:targetgroup/name/id]

$ aws elbv2 register-targets --target-group-arn [target_group_arn] --targets Id=[i-xxxxxxxx],Port=[80]

$ aws elbv2 deregister-targets --target-group-arn [target_group_arn] --targets Id=[i-xxxxxxxx]

$ aws elbv2 create-load-balancer --name [lb_name] --type application --subnets [subnet-1] [subnet-2] --security-groups [sg-xxxxxxxx]

$ aws elbv2 describe-listeners --load-balancer-arn [load_balancer_arn]

$ aws elbv2 delete-load-balancer --load-balancer-arn [load_balancer_arn]

aws elbv2 subcommand [options]

aws elbv2 is a subcommand of the AWS CLI that manages Application Load Balancers (ALB) and Network Load Balancers (NLB), the second generation of Elastic Load Balancing services.
Application Load Balancers operate at Layer 7 and support advanced routing based on URL path, hostname, HTTP headers, and query strings. They integrate with WAF, support WebSocket, and can route to Lambda functions.
Network Load Balancers operate at Layer 4 with ultra-low latency and can handle millions of requests per second. They preserve client IP addresses and support static IPs and PrivateLink.
Both types use target groups to route requests to registered targets like EC2 instances, containers, IP addresses, or Lambda functions.

describe-load-balancers

List load balancers and their details.

Create a new ALB or NLB.

Remove a load balancer.

List target groups.

Create a new target group.

Remove a target group.

Check health of targets in a group.

Add targets to a group.

Remove targets from a group.

List listeners on a load balancer.

Add a listener to a load balancer.

List routing rules for a listener.

ARN of the load balancer.

ARN of the target group.

Load balancer type: application, network, or gateway.

Target specifications (Id, Port, AvailabilityZone).

Subnets for the load balancer.

Target groups are bound to a specific load balancer type and cannot be shared between ALB and NLB. Deleting a load balancer does not delete associated target groups. ALB requires at least two subnets in different Availability Zones. Cross-zone load balancing behavior differs between ALB (always enabled) and NLB (configurable).

Application Load Balancer launched in August 2016 as AWS's Layer 7 load balancer with content-based routing. Network Load Balancer followed in September 2017 for high-performance Layer 4 workloads. Gateway Load Balancer was added in November 2020 for third-party virtual appliances. Features like weighted target groups, Lambda targets, and gRPC support have been added over time.

aws(1), aws-elb(1), aws-ec2(1), aws-wafv2(1)