# Elasticsearch 5.3 EC2 Discovery Issue

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-3-ec2-discovery-issue/84097>\
**Category:** Elasticsearch\
**Created:** [April 29, 2017, 8:43pm UTC](https://discuss.elastic.co/t/elasticsearch-5-3-ec2-discovery-issue/84097 "2017-04-29T20:43:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [April 29, 2017, 8:56pm UTC](https://discuss.elastic.co/t/elasticsearch-5-3-ec2-discovery-issue/84097/2 "2017-04-29T20:56:44Z")

</div>

Don't duplicate questions please.

> [@Elasticsearch 5.3 Discovery Issue](https://discuss.elastic.co/t/elasticsearch-5-3-discovery-issue/83934):
>
> I have build an ES5.3 cluster with Kibana5.3 (No Logstash). I have my nodes in place and curl works just fine on all the nodes. But the problem is, the nodes are not discovering each other. I have tried several options but nothing worked. I am deploying this on EC2 instances. My elasticsearch.yml file looks like this: plugin.mandatory: cloud-aws [cluster.name](http://cluster.name): CC-ES-5.3-Cluster network.host: discovery.type: ec2 discovery.zen.ping.multicast.enabled: false discovery.ec2.groups: cloud.aws.…

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-5-3-ec2-discovery-issue/84097)._