# Deploy Dockerized ES to AWS BeansTalk. How to make ES ignore internal Docker IP's from other nodes?

**URL:** <https://discuss.elastic.co/t/deploy-dockerized-es-to-aws-beanstalk-how-to-make-es-ignore-internal-docker-ips-from-other-nodes/34567>\
**Category:** Elasticsearch\
**Created:** [November 13, 2015, 10:13pm UTC](https://discuss.elastic.co/t/deploy-dockerized-es-to-aws-beanstalk-how-to-make-es-ignore-internal-docker-ips-from-other-nodes/34567 "2015-11-13T22:13:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vladmiller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vladmiller/32/5909_2.png) [@vladmiller](https://discuss.elastic.co/u/vladmiller)\
**Post date:** [November 13, 2015, 10:13pm UTC](https://discuss.elastic.co/t/deploy-dockerized-es-to-aws-beanstalk-how-to-make-es-ignore-internal-docker-ips-from-other-nodes/34567/1 "2015-11-13T22:13:29Z")

</div>

Hello everyone,

So I'm trying to deploy ES to EBT Docker service.

The problem is that Docker container has it's own private ip, something like **172.17.0.3** , therefore when ES starts it will pickup this first IP. However the container's host has different private IP **10.165.71.177**

From the log beneath you can see that one ES node will try to communicate with another ES node _10.165.71.177_\*, which however returns local Docker IP **172.17.0.3** , thus first ES node tries to connect to wrong IP.

The question is the following, is it somehow possible to map host IP to docker container IP? Maybe somebody else had successful experience deploying ES on EBT?

Thanks

> [2015-11-13 21:50:58,537][TRACE][discovery.zen.ping.unicast] [86ac0ad55d5b] [2] connected to {#cloud-i-8c317a3b-0}{10.165.71.177}{ip-10-165-71-177.ec2.internal/10.165.71.177:9300}  
> [2015-11-13 21:50:58,538][TRACE][discovery.zen.ping.unicast] [86ac0ad55d5b] [2] sending to {#zen\_unicast\_21\_#cloud-i-8c317a3b-0#}{10.165.71.177}{ip-10-165-71-177.ec2.internal/10.165.71.177:9300}  
> [2015-11-13 21:50:58,542][TRACE][discovery.zen.ping.unicast] [86ac0ad55d5b] [2] received response from {#zen\_unicast\_21\_#cloud-i-8c317a3b-0#}{10.165.71.177}{ip-10-165-71-177.ec2.internal/10.165.71.177:9300}: [ping\_response{node [{86ac0ad55d5b}{U3PF5qOaQCucpK3JfZ3ARA}{172.17.0.3}{172.17.0.3:9300}], id[5], master [null], hasJoinedOnce [false], cluster\_name[es-staging]}, ping\_response{node [{86ac0ad55d5b}{U3PF5qOaQCucpK3JfZ3ARA}{172.17.0.3}{172.17.0.3:9300}], id[7], master [null], hasJoinedOnce [false], cluster\_name[es-staging]}, ping\_response{node [{86ac0ad55d5b}{U3PF5qOaQCucpK3JfZ3ARA}{172.17.0.3}{172.17.0.3:9300}], id[9], master [null], hasJoinedOnce [false], cluster\_name[es-staging]}, ping\_response{node [{86ac0ad55d5b}{U3PF5qOaQCucpK3JfZ3ARA}{172.17.0.3}{172.17.0.3:9300}], id[11], master [null], hasJoinedOnce [false], cluster\_name[es-staging]}, ping\_response{node [{89764d1bb185}{yVRC-HmIQoayIuWfi6a09g}{172.17.0.3}{172.17.0.3:9300}], id[30], master [{89764d1bb185}{yVRC-HmIQoayIuWfi6a09g}{172.17.0.3}{172.17.0.3:9300}], hasJoinedOnce [true], cluster\_name[es-staging]}]  
> [2015-11-13 21:51:00,036][TRACE][discovery.zen.ping.unicast] [86ac0ad55d5b] [2] disconnecting from {#zen\_unicast\_19\_#cloud-i-8c317a3b-0#}{10.165.71.177}{ip-10-165-71-177.ec2.internal/10.165.71.177:9300}  
> [2015-11-13 21:51:00,037][TRACE][discovery.ec2] [86ac0ad55d5b] full ping responses:  
> --\> ping\_response{node [{89764d1bb185}{yVRC-HmIQoayIuWfi6a09g}{172.17.0.3}{172.17.0.3:9300}], id[30], master [{89764d1bb185}{yVRC-HmIQoayIuWfi6a09g}{172.17.0.3}{172.17.0.3:9300}], hasJoinedOnce [true], cluster\_name[es-staging]}  
> [2015-11-13 21:51:00,041][DEBUG][discovery.ec2] [86ac0ad55d5b] filtered ping responses: (filter\_client[true], filter\_data[false])  
> --\> ping\_response{node [{89764d1bb185}{yVRC-HmIQoayIuWfi6a09g}{172.17.0.3}{172.17.0.3:9300}], id[30], master [{89764d1bb185}{yVRC-HmIQoayIuWfi6a09g}{172.17.0.3}{172.17.0.3:9300}], hasJoinedOnce [true], cluster\_name[es-staging]}

---

<div class="post-metadata">

**Author:** ![vladmiller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vladmiller/32/5909_2.png) [@vladmiller](https://discuss.elastic.co/u/vladmiller)\
**Post date:** [November 19, 2015, 9:05am UTC](https://discuss.elastic.co/t/deploy-dockerized-es-to-aws-beanstalk-how-to-make-es-ignore-internal-docker-ips-from-other-nodes/34567/2 "2015-11-19T09:05:47Z")

</div>

This can be achieved by using public\_host property. However I decided to take another path and avoid docker

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:37pm UTC](https://discuss.elastic.co/t/deploy-dockerized-es-to-aws-beanstalk-how-to-make-es-ignore-internal-docker-ips-from-other-nodes/34567/3 "2017-07-05T23:37:21Z")

</div>


