The latest articles on DEV Community by Hermit (@hermit). https://dev.to/hermit https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F649100%2F87db56f4-a649-4d6b-8d3b-5bd66fc278e9.jpeg https://dev.to/hermit en Hermit Sun, 04 Jul 2021 15:17:44 +0000 https://dev.to/hermit/aws-elb-sticky-session-over-ip-php https://dev.to/hermit/aws-elb-sticky-session-over-ip-php <p>Hi all,</p> <p>I am facing a challenge in configuring sticky session on AWS ELB. The problem statement which I have is, I want sticky session over IP and not over application. What I mean by that is, if a request is coming from same IP of a particular user , like even though browser tab/window change, the sticky session should work. </p> <p>In my application (which runs on say <a href="https://app.in">https://app.in</a>), the authentication method uses third party app (which runs on say, <a href="https://auth.in">https://auth.in</a>). So when the login page loads, the session gets created at the server (say box1 - one of EC2 boxes). The user clicks on login button and a new window pops up (with domain <a href="https://auth.in">https://auth.in</a>). The user now has to enter credentials details in <a href="https://auth.in">https://auth.in</a> and the verification request should go to box1 only (backend for auth and app both are running on all the boxes). But what is happening is, as soon I setup ELB, the session gets created at box1 but the verification request goes to Box2. Due to which the user never gets verified. </p> <p>Can this scenario be solved using sticky session? </p> <p>TIA. </p> aws elb