-
Hi, Nikee, thanks for replying so quick.
I agree with your reasons that health check interval may not be an answer here but my main point is that session stickiness can not be a valid solution either. I do understand how session stickiness works, I used it before, but the thing is that if your application keeps the state (the session data) and expects requests from the same user/session to end up on the same EC2 instance – you can NOT disable session stickiness as it will break the user experience completely – users will be treated as authenticated by one instance and unauthenticated by another. You can only disable session stickiness if you know your application is ok with it – that is it is stateless. But the question does not mention that so it is just not safe to make a change like that knowing it may make a situation worse and replace one overloaded instance with equally distributed load but users being unable to use the app.
Cheers
