Features of Load Balancers in AWS

Sticky sessions

Sticky sessions, also known as session affinity, are a load-balancing feature that forces the load balancer to forward all requests from a client to the same EC2 instance as long as the session is active. Sticky sessions are only supported by ALBs and CLBs.

In the example below, all requests from User 1 are forwarded to the first EC2 instance, requests from Users 3 and 4 to the second EC2 instance, and requests from User 2 to the third EC2 instance. This isn’t how the ELBs would normally direct our traffic. If sticky sessions aren’t enabled, ELB will simply choose any of the EC2 instances and try to balance the overall requests per instance.

• Use case: This type of architecture is required when we don’t want our clients to lose their session data.

• Con: Using sticky sessions might imbalance the load on the EC2 instances if users don’t end their sessions for a long time.

Sticky sessions are controlled by using cookies. ELBs support two kinds of cookies:

• Application-based cookies are generated by our application on EC2 instances (custom cookies) or load balancers. The custom cookies generated by our application can have all the custom information required by our application.

• Duration-based cookies are generated by the load balancers.

We can enable stickiness on the “Edit attributes” page by clicking the checkbox. Next, we need to choose the type of cookie, either load-balancer ...