AWS ELB (Elastic Load Balancer), Sticky Session

262 단어·2 분·원문(.md)

Elastic Load Balancing automatically distributes incoming application traffic to multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions.

It can handle varying application loads in a single availability zone or across multiple availability zones.

All three load balancers provided by Elastic Load Balancing offer the high availability, automatic scaling, and robust security required for application fault tolerance.

Vertical Scale #

Horizontal Scale #

ELB Features #

IP changes continuously

  • IP addresses change continuously.
  • Therefore, it must be used based on a domain.

Health Check

  • It checks if an instance is alive by directly generating traffic.
  • It is divided into two states: InService and OutService.

Three types

  • Application Load Balancer
  • Network Load Balancer
  • Classic Load Balancer

Application Load Balancer #

It operates at the Application Level; you can think of it as the 'smart one'.

Network Load Balancer #

You can think of it as the 'fast one'. Elastic IP allocation is possible.

Classic Load Balancer #

You can think of it as the 'old one'. It's not commonly used nowadays.

Sticky Session #

When you have two or more instances, if you log in to the web server of Instance A, a session will be issued.

However, if you make another request, it might be directed to the web server of Instance B, which would then ask you to log in again without a session.

To prevent this, Sticky Session was introduced.

Sticky Session stores which instance each user accessed and ensures that subsequent requests are directed to that same instance.

DevOps/aws/elb.md