# Dremio was not able to connect with Elasticsearch hosted in Ec2

**URL:** <https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584>\
**Category:** Uncategorized\
**Created:** [January 21, 2019, 10:58pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584 "2019-01-21T22:58:03Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 21, 2019, 10:58pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/1 "2019-01-21T22:58:03Z")

</div>

I have installed Elasticsearch in AWS EC2 from the following link :-

[https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.5.4.rpm and modified my /etc/elasticsearch/elasticsearch.yml](https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.5.4.rpm%20and%20midified%20my%20/etc/elasticsearch/elasticsearch.yml) file to point to my Ec2 private IP address

and I could see that Elasticsearch is installed and up and running and working fine by running curl as below :-

curl myec2instance\_private\_ip-adress:9200/\_cluster/health?pretty . its returning the expected result .

. But when I am trying to connect my EC2 hosted Elasticsearch from dremio elasticsearch **by typing private IP address** into Dremio elastic search source **host** and choosing no authentication in authentication option and while I tried to save it I am getting the following error :-

**Encountered a problem while executing [com.dremio.plugins.elastic.ElasticActions$NodesInfo@27c0cb30](mailto:com.dremio.plugins.elastic.ElasticActions%24NodesInfo@27c0cb30).**

**Cannot gather Elasticsearch nodes information. Please make sure that the user has [cluster:monitor/nodes/info] privilege.**

.

Please note I wide opened all the port and connection from any ip and any source in my ec2 security group and NACL and subnet to make sure there is no blocking but still no luck . Please advise .

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 22, 2019, 1:19am UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/2 "2019-01-22T01:19:53Z")

</div>

Hi @Sayed_Rahman

What version of Dremio are you using? We have support for Elasticsearch on AWS only from Dremio version 3.0.5.

If you are already on 3.0.5 and still getting the error, then kindly check the below things

1. AWS on Elasticsearch is a separate source, see attached image  
[AWS on elasticsearch](https://docs.dremio.com/data-sources/elasticsearch.html#dremio-and-elasticsearch)
2. When adding the hostname, do not give the http

 ![aws-es-source-form](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/1/16aee34c14f7f4062bcbd3fe3c038ed8601358d0.png) ![aws-es-source-type](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/e/e90b693843e91408820ef7e13c53913d1ee1d683.png)

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 22, 2019, 12:05pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/3 "2019-01-22T12:05:40Z")

</div>

I am not using aws managed elastic search .As I see in your snapshot you are showing managed aws ES .I am using EC2 hosted elastic search .Yes ,I am using latest version of dremio .

Thanks,

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 22, 2019, 1:53pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/4 "2019-01-22T13:53:08Z")

</div>

Thanks @Sayed_Rahman

Kindly send us the server.log from the Dremio coordinator

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 22, 2019, 5:14pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/5 "2019-01-22T17:14:34Z")

</div>

[sayed\_personal\_account\_personal\_dremio\_server\_log.zip](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/4/407d593af7c490d68cad03153b8fa6990944716f.zip) (57.2 KB)

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 22, 2019, 5:17pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/6 "2019-01-22T17:17:31Z")

</div>

I recreated the same environment (EC2 hosted elastic search 6.5.4 with latest version of Dremio) today and tried again to connect and got the same error message and sharing the server log with you .Thanks

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 22, 2019, 5:21pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/7 "2019-01-22T17:21:31Z")

</div>

Hi @Sayed_Rahman

Can you please share your elastic source settings on Dremio? the General and advanced tab?, you can mark “XXX” for the values. More interested in the check boxes. attached screenshots

 ![managed-es-advanced](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/9/92d94c7aebfa643fe8780997b1c30bf5d672252f.png) ![managed-es-general](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/0/09191411291625529b7dd1a039620742f6efb599.png)

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 22, 2019, 7:25pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/8 "2019-01-22T19:25:42Z")

</div>

![screen_two_my_personal-account_dremio](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/3/337742124890c0ae0d9b835326013a38d73ea9ab.jpeg)

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 22, 2019, 7:26pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/9 "2019-01-22T19:26:17Z")

</div>

![screen_one_my_personal-account_dremio](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/c/cdb3d7101f39892c111ad133397bd728a59e79be.jpeg)

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 23, 2019, 8:28pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/10 "2019-01-23T20:28:37Z")

</div>

Hi balaji, Any update on my error ?  
Thanks,  
Sayed Rahman

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 23, 2019, 8:46pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/11 "2019-01-23T20:46:54Z")

</div>

Hi @Sayed_Rahman

Can you please check the box for “Managed Elasticsearch service” and try again ?

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 23, 2019, 8:48pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/12 "2019-01-23T20:48:51Z")

</div>

Hi @Sayed_Rahman

I just got to know that your Dremio and ES are on the same box and problem is resolved

Thanks  
@balaji.ramaswamy

---

<div class="post-metadata">

**Author:** ![Sayed\_Rahman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@Sayed\_Rahman](https://community.dremio.com/u/Sayed_Rahman)\
**Post date:** [January 23, 2019, 8:50pm UTC](https://community.dremio.com/t/dremio-was-not-able-to-connect-with-elasticsearch-hosted-in-ec2/2584/13 "2019-01-23T20:50:18Z")

</div>

Luckily Naren sankar (solution architect) from Dremio came to our office yesterday and today we connected and he helped me to figure it out . The issue is in host field I need to type “localhost” not the private IP of EC2 instance and it worked fine . Thank you for your help though .
