AWS Cloudfront and X-Real-IP header

[nachor22]

Hi,

I'm testing this solution deployed to AWS CloudFront. It's working but geo-location properties are not set correctly.
Is X-Real-IP the only header supported by Mixpanel? It's not allowed to modify that header from CloudFront.

Thanks

[mark-x-omgene]

We are also testing deployment with proxy while the CloudFront used as web-server. Seems like either use case for CloudFront functions or nano instance with nginx. But having alternative header that Cloudfront Itself can modify will be very helpful.

[elninopl]

Same problem here. Is there any chance to check another custom header to get IP by Mixpanel?

[tdumitrescu]

Have you tried X-Forwarded-For?

[Enase]

I use this solution:

        set $real_ip $realip_remote_addr;

        if ($http_x_forwarded_for ~* "^(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})") {
            set $real_ip $1;
        }

        location /health-check {
            return 200 'Healthy\n';
            add_header Content-Type text/plain;
        }

        location /lib.min.js {
            proxy_set_header X-Real-IP $real_ip;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Host $server_name;
            proxy_pass https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js;
        }

      and so on...

full terraform setup here