# EC2 discovery (AWS-Cloud) not working for one account, working for the other one

**URL:** <https://discuss.elastic.co/t/ec2-discovery-aws-cloud-not-working-for-one-account-working-for-the-other-one/13682>\
**Category:** Elasticsearch\
**Created:** [September 18, 2013, 8:47pm UTC](https://discuss.elastic.co/t/ec2-discovery-aws-cloud-not-working-for-one-account-working-for-the-other-one/13682 "2013-09-18T20:47:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ralph\_Trickey\_2](https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/32.png) [@Ralph\_Trickey\_2](https://discuss.elastic.co/u/Ralph_Trickey_2)\
**Post date:** [September 18, 2013, 8:47pm UTC](https://discuss.elastic.co/t/ec2-discovery-aws-cloud-not-working-for-one-account-working-for-the-other-one/13682/1 "2013-09-18T20:47:42Z")

</div>

ES 0.90.3, aws-cloud 1.15

I'm using security groups for discovery. Everything works just fine when  
running under my dev account and deploying using Cloudformation and a role  
with ec2:Describe\* permission.  
It doesn't work and I had to fall back to unicast discovery in Production.

Any ideas on what to check to try to figure out what's different?

Errors...

[2013-09-18 16:05:46,597][TRACE][discovery] [Perun] waiting  
for 30s for the initial state to be set by the discovery  
[2013-09-18 16:06:16,597][WARN][discovery] [Perun] waited  
for 30s and no initial state was set by the discovery  
[2013-09-18 16:06:16,597][INFO][discovery] [Perun]  
Cabin/yaxw464asdfgZSvrtYJg  
[2013-09-18 16:06:16,632][INFO][http] [Perun]  
bound\_address {inet[/0.0.0.0:9200]}, publish\_address  
{inet[/xxx.xxx.xxx.xxx:9200]}  
[2013-09-18 16:06:16,632][INFO][node] [Perun] started  
[2013-09-18 16:09:11,102][INFO][discovery.ec2] [Perun]  
Exception while retrieving instance list from AWS API: Unable to execute  
HTTP request: Connect to  
[ec2.us-west-1.amazonaws.com/ec2.us-west-1.amazonaws.com/204.246.160.140](http://ec2.us-west-1.amazonaws.com/ec2.us-west-1.amazonaws.com/204.246.160.140)  
timed out  
[2013-09-18 16:09:11,103][DEBUG][discovery.ec2] [Perun] Full  
exception:  
com.amazonaws.AmazonClientException: Unable to execute HTTP request:  
Connect to  
[ec2.us-west-1.amazonaws.com/ec2.us-west-1.amazonaws.com/204.246.160.140](http://ec2.us-west-1.amazonaws.com/ec2.us-west-1.amazonaws.com/204.246.160.140)  
timed out  
at  
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:328)  
at  
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:165)  
at  
com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:6047)

--  
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).

---

<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 6, 2017, 2:15am UTC](https://discuss.elastic.co/t/ec2-discovery-aws-cloud-not-working-for-one-account-working-for-the-other-one/13682/2 "2017-07-06T02:15:42Z")

</div>