Configure Sticky Sessions for your classic Load Balancer

Question 1

requirement

Answer 1

An HTTP/HTTPS load balancer.

At least one healthy instance in each Availability Zone.

Question 2

Duration-Based Session Stickiness

Answer 2

The load balancer uses a special cookie to track the instance for each request to each listener. When the load balancer receives a request, it first checks to see if this cookie is present in the request. If so, the request is sent to the instance specified in the cookie. If there is no cookie, the load balancer chooses an instance based on the existing load balancing algorithm.
create-lb-cookie-stickiness-policy

Question 3

Application-Controlled Session Stickiness

Answer 3

The load balancer uses a special cookie to associate the session with the instance that handled the initial request, but follows the lifetime of the application cookie specified in the policy configuration. The load balancer only inserts a new stickiness cookie if the application response includes a new application cookie. The load balancer stickiness cookie does not update with each request. If the application cookie is explicitly removed or expires, the session stops being sticky until a new application cookie is issued.
CLI: create-app-cookie-stickiness-policy
set-load-balancer-policies-of-listener
describe-load-balancers

Question 4

Tag restrictions

Answer 4

Maximum number of tags per resource—50
Maximum key length—127 Unicode characters
Maximum value length—255 Unicode characters
Tag keys and values are case sensitive. Allowed characters are letters, spaces, and numbers representable in UTF-8, plus the following special characters: + - = . _ : / @. Do not use leading or trailing spaces.
Do not use the aws: