# ElasticSearch and AWS **URL:** \ **Category:** Elasticsearch\ **Created:** [August 26, 2010, 4:24pm UTC](https://discuss.elastic.co/t/elasticsearch-and-aws/3264 "2010-08-26T16:24:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Pete\_Hunt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pete_hunt/32/3325_2.png) [@Pete\_Hunt](https://discuss.elastic.co/u/Pete_Hunt)\ **Post date:** [August 26, 2010, 4:24pm UTC](https://discuss.elastic.co/t/elasticsearch-and-aws/3264/1 "2010-08-26T16:24:30Z")
Hi - I've set up a 2-node cluster using AutoScaling and Elastic Load Balancing on Amazon EC2. I have installed the cloud-aws plugin and configured it as follows: cloud: aws: access\_key: [my access key] secret\_key: [my secret key] discovery: type: ec2 gateway: type: s3 s3: bucket: [my bucket name] I have created an AMI that starts ElasticSearch with no arguments on start-up. The problem that I am having is that though searching is working well, when I hit /\_cluster/health, it returns: { "status" : "yellow", "timed\_out" : false, "number\_of\_nodes" : 1, "active\_primary\_shards" : 15, "active\_shards" : 15, "relocating\_shards" : 0 } Which I believe means that the two nodes are not discovering each other properly. Am I missing something? The two nodes are identical AMIs, both running in the same, single security group and the same availability zone. Thanks, Pete ---
**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\ **Post date:** [August 27, 2010, 2:23am UTC](https://discuss.elastic.co/t/elasticsearch-and-aws/3264/2 "2010-08-27T02:23:28Z")
Just a guess (going to be setting up similar within a few days), but I'd try explicitly listing the groups and availability\_zones listed here: [http://www.elasticsearch.com/docs/elasticsearch/cloud/aws/ec2\_discovery/](http://www.elasticsearch.com/docs/elasticsearch/cloud/aws/ec2_discovery/) Not sure if it is possible to have sensible defaults for these. Hope this helps, Paul On Aug 26, 10:24 am, Pete Hunt [floydoph...@gmail.com](mailto:floydoph...@gmail.com) wrote: > Hi - > > I've set up a 2-node cluster using AutoScaling and Elastic Load > Balancing on Amazon EC2. I have installed the cloud-aws plugin and > configured it as follows: > > cloud: > aws: > access\_key: [my access key] > secret\_key: [my secret key] > > discovery: > type: ec2 > > gateway: > type: s3 > s3: > bucket: [my bucket name] > > I have created an AMI that starts Elasticsearch with no arguments on > start-up. The problem that I am having is that though searching is > working well, when I hit /\_cluster/health, it returns: > > { > "status" : "yellow", > "timed\_out" : false, > "number\_of\_nodes" : 1, > "active\_primary\_shards" : 15, > "active\_shards" : 15, > "relocating\_shards" : 0 > > } > > Which I believe means that the two nodes are not discovering each > other properly. Am I missing something? The two nodes are identical > AMIs, both running in the same, single security group and the same > availability zone. > > Thanks, > > Pete ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 27, 2010, 10:25am UTC](https://discuss.elastic.co/t/elasticsearch-and-aws/3264/3 "2010-08-27T10:25:07Z")
By default it won't filter by groups. When you execute the cluster state API, do you see the other nodes? On Fri, Aug 27, 2010 at 5:23 AM, Paul [ppearcy@gmail.com](mailto:ppearcy@gmail.com) wrote: > Just a guess (going to be setting up similar within a few days), but > I'd try explicitly listing the groups and availability\_zones listed > here: > [http://www.elasticsearch.com/docs/elasticsearch/cloud/aws/ec2\_discovery/](http://www.elasticsearch.com/docs/elasticsearch/cloud/aws/ec2_discovery/) > > Not sure if it is possible to have sensible defaults for these. > > Hope this helps, > Paul > > On Aug 26, 10:24 am, Pete Hunt [floydoph...@gmail.com](mailto:floydoph...@gmail.com) wrote: > > > Hi - > > > > I've set up a 2-node cluster using AutoScaling and Elastic Load > > Balancing on Amazon EC2. I have installed the cloud-aws plugin and > > configured it as follows: > > > > cloud: > > aws: > > access\_key: [my access key] > > secret\_key: [my secret key] > > > > discovery: > > type: ec2 > > > > gateway: > > type: s3 > > s3: > > bucket: [my bucket name] > > > > I have created an AMI that starts Elasticsearch with no arguments on > > start-up. The problem that I am having is that though searching is > > working well, when I hit /\_cluster/health, it returns: > > > > { > > "status" : "yellow", > > "timed\_out" : false, > > "number\_of\_nodes" : 1, > > "active\_primary\_shards" : 15, > > "active\_shards" : 15, > > "relocating\_shards" : 0 > > > > } > > > > Which I believe means that the two nodes are not discovering each > > other properly. Am I missing something? The two nodes are identical > > AMIs, both running in the same, single security group and the same > > availability zone. > > > > Thanks, > > > > Pete ---
**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, 4:20am UTC](https://discuss.elastic.co/t/elasticsearch-and-aws/3264/4 "2017-07-06T04:20:16Z")