Elastic Load Balancing distributes client traffic to registered targets. These sections cover protocol choices, listener rules, health-based routing, target lifecycle settings, and request troubleshooting.
Elastic Load Balancing basics
Elastic Load Balancing puts one entry point in front of many targets and spreads the traffic among the healthy ones.
How it works
- Clients connect to the load balancer.
- It checks the health of the registered targets.
- It sends each request to a healthy target, across Availability Zones.
Exam cues
- If the question says distribute traffic across instances or Availability Zones, think Elastic Load Balancing.
Remember
- Routes only to healthy targets.
Trap: A load balancer spreads traffic; Auto Scaling changes how many instances there are. They are often used together.
From the AWS docs (8)
- Elastic Load Balancing spreads incoming traffic across targets such as EC2 instances, containers and IP addresses in one or more Availability Zones, and sends traffic only to healthy targets.
- Application Load Balancers route HTTP and HTTPS requests using request content.
- Network Load Balancers support TCP, TLS, UDP, TCP_UDP, QUIC, and TCP_QUIC listeners.
- A Network Load Balancer has a static IP address per enabled Availability Zone; an Elastic IP address can optionally be associated when it is created.
- Gateway Load Balancers distribute IP traffic to virtual appliances and exchange traffic with them using GENEVE on port 6081.
- Elastic Load Balancing scales its load balancer capacity as incoming traffic changes, distributes traffic across targets in multiple Availability Zones, and monitors target health to select healthy targets.
- Application Load Balancers natively support WebSockets: an HTTP/1.1 connection can be upgraded to a persistent ws or wss connection.
- An ALB can forward a request to a target group whose target is a Lambda function, invoking the function with the request content.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 5 cards as a list
A web app runs on EC2 instances in two Availability Zones. Which service spreads requests across them and skips unhealthy instances?
Elastic Load Balancing.
When should an application use an ALB, NLB, or GWLB?
ALB for HTTP request routing; NLB for transport protocols and static zonal addresses; GWLB for virtual inspection appliances using GENEVE on port 6081.
How does Elastic Load Balancing improve the availability of an application on EC2 instances in two Availability Zones?
It spreads traffic across the instances in both AZs and sends requests only to healthy ones.
Which load balancer supports path-based and host-based routing, WebSockets, and Lambda functions as targets?
The Application Load Balancer. It routes on HTTP content, upgrades connections to WebSockets, and can invoke a Lambda function from a target group.
When incoming application traffic grows, how does Elastic Load Balancing adjust the capacity of the load balancer itself?
Elastic Load Balancing scales load balancer capacity automatically as traffic changes.