# EC2 discovery issues **URL:** \ **Category:** Elasticsearch\ **Created:** [February 27, 2013, 4:45am UTC](https://discuss.elastic.co/t/ec2-discovery-issues/10918 "2013-02-27T04:45:09Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Marc\_Lennox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc_lennox/32/2634_2.png) [@Marc\_Lennox](https://discuss.elastic.co/u/Marc_Lennox)\ **Post date:** [February 27, 2013, 4:45am UTC](https://discuss.elastic.co/t/ec2-discovery-issues/10918/1 "2013-02-27T04:45:09Z")
Been trying for a while to get a simple 3 node configuration going on EC2 (1 master with no data, 2 slaves with data). I have trace logging setup and can see that the nodes discover each other correctly and connect, but then immediately disconnect. Looking at the master through the /head/ plugin I only see the master and no shards are allocated. Using 0.20.5 with the aws cloud plugin. Any ideas where to start? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Marc\_Lennox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc_lennox/32/2634_2.png) [@Marc\_Lennox](https://discuss.elastic.co/u/Marc_Lennox)\ **Post date:** [February 27, 2013, 4:49am UTC](https://discuss.elastic.co/t/ec2-discovery-issues/10918/2 "2013-02-27T04:49:52Z")
Funny, after banging my head for 4 hours and finally posting to this group, I figured out the issue immediately after the post. I had to open up port 9300 in the security group in EC2. Problem solved. On Tuesday, 26 February 2013 23:45:09 UTC-5, Marc Lennox wrote: > Been trying for a while to get a simple 3 node configuration going on EC2 > (1 master with no data, 2 slaves with data). I have trace logging setup > and can see that the nodes discover each other correctly and connect, but > then immediately disconnect. Looking at the master through the /head/ > plugin I only see the master and no shards are allocated. > > Using 0.20.5 with the aws cloud plugin. > > Any ideas where to start? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:49am UTC](https://discuss.elastic.co/t/ec2-discovery-issues/10918/3 "2017-07-06T02:49:22Z")
Closed on July 6, 2017, 2:49am UTC