Instances are not seeing user's real IP but LoadBalancer's.

Open gmansilla opened this issue 5 years ago • 1 comments

I have already deployed this stack and then realized the web server is registering LoadBalancer's IP instead of user's IP.

This might be a problem when reading logs or for security plugins that try to ban offending IPs.

I know how to fix this in my instance but since this in autoscaling group new instances launched won't see my changes.

If we were using Launch Templates it'd be easier, I just generate a new version, but this stack uses Launch Configuration and it cannot be changed.

Another option I'm thinking is just creating an image from my current instance and then setup a new Launch Template and use the new AMI.

I'm open to suggestions.

Mar 04 '20 14:03 gmansilla

Sorry for the very late response.

We weren't correctly tracking the issues/PRs from this repository in our support workflow.

It is likely that this issue is no longer applicable. Are you still affected? Please do not hesitate to let us know if that is the case, and one of our agents would help you with it.

Mar 23 '21 18:03 juan131