ELB Flashcards
Automatically distributes incoming application traffic across multiple targets.
Elastic Load Balancing
Load balancer best suited for balancing HTTP and HTTPS traffic
Application Load Balancer
Load Balancer that operates at layer 7 (application level), and is application aware
Application Load Balancer
Load balancer that is capable of handling millions of requests per second, while maintaining ultra-low latencies (high performance)
Network Load Balancer
Load Balancer that operates at layer 4
Network Load Balancer
Load balancer used when deploying inline virtual appliances where network traffic is not destined for the gateway load balancer itself
Gateway Load Balancer
Load Balancer that operates at layer 3
Gateway Load Balancer
Legacy load balancers that balance HTTP and HTTPS applications
Classic Load Balancer
Load balancers used for testing and dev work
Classic Load Balancer
Periodically send requests to load balancer’s registered instances to test their status
Health Checks
Do load balancers send requests to unhealthy instances?
No
Status of any instances that are unhealthy at the time of the health check
OutOfService
Checks for connection requests from clients using the protocol and port you configure
Listeners
When conditions are met then its defined actions are performed
Rules
Route requests to one or more registered targets using the port and number specified
Target Groups
Routing that looks at the pathway and can make routing decisions based on the path
Path-Based Routing
When traffic is sent from a load balancer the server access log contain the IP address of the load balancer only, this is used to see the original IP of the client
X-Forwarded-For
When application stop responding and the Loak Balancer responds with a 504 error.
Gateway Timeouts
Allows you to bind a user’s session to a specific EC2 instance
Sticky Sessions
Allows Load balancers to keep existing connections open if the EC2 instances are de-registered or become unhealthy
Deregistration Delay
