# \[Solved\] Discovery\_ec2 with ES 6.3.2 not finding other nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [August 10, 2018, 11:57pm UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949 "2018-08-10T23:57:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![kd5dbl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kd5dbl/32/10450_2.png) [@kd5dbl](https://discuss.elastic.co/u/kd5dbl)\ **Post date:** [August 10, 2018, 11:57pm UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949/1 "2018-08-10T23:57:08Z")
I'm doing my first 6.x install and trying to get the new discovery\_ec2 plugin to work and it isn't finding any of my other nodes: I have 1 master node and 2 data only nodes. The master node comes up and votes itself master. The two data nodes during master discovery don't appear to be able to find the master node: ``` [2018-08-10T23:43:31,480][DEBUG][o.e.a.a.c.h.TransportClusterHealthAction] [es_ip-10-174-0-164] no known master node, scheduling a retry [2018-08-10T23:43:38,617][WARN][o.e.d.z.ZenDiscovery] [es_ip-10-174-0-164] not enough master nodes discovered during pinging (found [[]], but needed [-1]), pinging again [2018-08-10T23:44:01,481][DEBUG][o.e.a.a.c.h.TransportClusterHealthAction] [es_ip-10-174-0-164] timed out while retrying [cluster:monitor/health] after failure (timeout [30s]) ``` My understanding is that as of 6.x the discovery\_ec2 plugin uses the IAM profile credentials of the EC2 to do the discovery. I have verified that my IAM role the EC2 is running under has permissions to do the discovery. I look for other members of the cluster by searching EC2's by tags: ``` # discovery discovery.zen.hosts_provider: ec2 discovery.ec2.host_type: private_ip discovery.zen.ping_timeout: 120s discovery.ec2.groups: sg-064eba472ffef646d discovery.ec2.tag.Owner: devops discovery.ec2.tag.Mode: user discovery.ec2.tag.Carrier: XX discovery.ec2.tag.Group: user ``` Do I need to set up anything special on the EC2? Does the user account need an ~/.aws folder with valid creditials/secret key? Or should it be able to determine all of that from the IAM profile? Also, we're running these EC2 behind a web proxy and have also set the discovery proxy: ``` discovery.ec2.protocol: https discovery.ec2.proxy.host: foo.proxy.int discovery.ec2.proxy.port: 1234 ``` Any suggestions would be really appreciated... trying to migrate off of a really old 5.1 install ... Thanks! ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 11, 2018, 11:31am UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949/2 "2018-08-11T11:31:02Z")
In which region are running your nodes? ---
**Author:** ![kd5dbl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kd5dbl/32/10450_2.png) [@kd5dbl](https://discuss.elastic.co/u/kd5dbl)\ **Post date:** [August 13, 2018, 11:58am UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949/3 "2018-08-13T11:58:35Z")
us-west-2 ---
**Author:** ![kd5dbl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kd5dbl/32/10450_2.png) [@kd5dbl](https://discuss.elastic.co/u/kd5dbl)\ **Post date:** [August 13, 2018, 8:47pm UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949/4 "2018-08-13T20:47:50Z")
Looks like you have to supply an endpoint and the availability zones in order for it to work properly... would be nice to update the 6.x documentation to make this obvious... Solution found here: > [@Cannot Discover Master Node after upgrade to ES 6.0.0](https://discuss.elastic.co/t/cannot-discover-master-node-after-upgrade-to-es-6-0-0/108029/3): > > Yes I did. It was a fresh docker image for 6.0.0 on top of which ran bin/elasticsearch-plugin install --batch discovery-ec2 to get the latest discovery plugin. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 13, 2018, 9:16pm UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949/5 "2018-08-13T21:16:26Z")
Yeah. There is a pending PR to fix the doc but this has not been merged yet. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 10, 2018, 9:16pm UTC](https://discuss.elastic.co/t/solved-discovery-ec2-with-es-6-3-2-not-finding-other-nodes/143949/6 "2018-09-10T21:16:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.