# Can not get client real ip in kubernetes on AWS ELB

**URL:** <https://discuss.konghq.com/t/can-not-get-client-real-ip-in-kubernetes-on-aws-elb/4925>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [November 15, 2019, 12:59pm UTC](https://discuss.konghq.com/t/can-not-get-client-real-ip-in-kubernetes-on-aws-elb/4925 "2019-11-15T12:59:38Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![abenitovsc](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/abenitovsc/32/1521_2.png) [@abenitovsc](https://discuss.konghq.com/u/abenitovsc)\
**Post date:** [November 23, 2019, 3:17pm UTC](https://discuss.konghq.com/t/can-not-get-client-real-ip-in-kubernetes-on-aws-elb/4925/6 "2019-11-23T15:17:20Z")

</div>

Hi @Mju, i have just realized that trusted\_ips content was escaped with \<  
I have updated my last comment. Tell us with the feedback. You can deploy this app to check the headers.  
[https://hub.docker.com/r/brndnmtthws/nginx-echo-headers/](https://hub.docker.com/r/brndnmtthws/nginx-echo-headers/)

You will see that the X-Real-IP set by kong from the remote\_addr is the first IP in the forwarded-for header (clientIP) instead of the last one(IP from the ELB CIDR).

---

_[View the full topic](https://discuss.konghq.com/t/can-not-get-client-real-ip-in-kubernetes-on-aws-elb/4925)._