# Having a problem getting ec2\_discovery to work in us\_west **URL:** \ **Category:** Elasticsearch\ **Created:** [December 22, 2010, 9:47pm UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693 "2010-12-22T21:47:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Gary\_B](https://avatars.discourse-cdn.com/v4/letter/g/6de8d8/32.png) [@Gary\_B](https://discuss.elastic.co/u/Gary_B)\ **Post date:** [December 22, 2010, 9:47pm UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693/1 "2010-12-22T21:47:35Z")
I have been able to get everything up and running perfectly in the Amazon us-east region. The config I'm using is leveraging the groups for the two nodes two find each other. I have what I think is an identical setup in the us-west region and the two nodes are not seeing each other - they both startup as master. I've tried a number of other things like setting the availability zone (to us-west-1a), changing the host type, etc., but I can't seem to get it to work. Is there something I should be looking for and/or configuring differently for the two regions? Should this work in us-west? Is there any other information I can post to help you guys in helping me troubleshoot the issue? ---
**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:** [December 23, 2010, 4:38am UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693/2 "2010-12-23T04:38:24Z")
Can you set the logging for discovery.ec2 to TRACE? Lets see when if those nodes gets discovered. Do you see anything in the logs? On Wed, Dec 22, 2010 at 11:47 PM, Gary B. [garybenitt@gmail.com](mailto:garybenitt@gmail.com) wrote: > I have been able to get everything up and running perfectly in the > Amazon us-east region. The config I'm using is leveraging the groups > for the two nodes two find each other. > > I have what I think is an identical setup in the us-west region and > the two nodes are not seeing each other - they both startup as > master. I've tried a number of other things like setting the > availability zone (to us-west-1a), changing the host type, etc., but I > can't seem to get it to work. > > Is there something I should be looking for and/or configuring > differently for the two regions? Should this work in us-west? Is > there any other information I can post to help you guys in helping me > troubleshoot the issue? ---
**Author:** ![Gary\_B](https://avatars.discourse-cdn.com/v4/letter/g/6de8d8/32.png) [@Gary\_B](https://discuss.elastic.co/u/Gary_B)\ **Post date:** [December 23, 2010, 5:44am UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693/3 "2010-12-23T05:44:43Z")
Yeah, it's pretty much what I thought. It ends up pulling up my groups from us-east instead of us-west - so it's not surprise that there's no match... I'm guessing that this request isn't specifying the region: Sending Request: POST [http://ec2.amazonaws.com](http://ec2.amazonaws.com) ? I would think that you would probably need to know that I'm trying to access us-west with another param and then use the appropriate endpoint for that region ([ec2.us-west-1.amazonaws.com](http://ec2.us-west-1.amazonaws.com))? On Wed, Dec 22, 2010 at 8:38 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > Can you set the logging for discovery.ec2 to TRACE? Lets see when if those > nodes gets discovered. Do you see anything in the logs? > > On Wed, Dec 22, 2010 at 11:47 PM, Gary B. [garybenitt@gmail.com](mailto:garybenitt@gmail.com) wrote: > > > I have been able to get everything up and running perfectly in the > > Amazon us-east region. The config I'm using is leveraging the groups > > for the two nodes two find each other. > > > > I have what I think is an identical setup in the us-west region and > > the two nodes are not seeing each other - they both startup as > > master. I've tried a number of other things like setting the > > availability zone (to us-west-1a), changing the host type, etc., but I > > can't seem to get it to work. > > > > Is there something I should be looking for and/or configuring > > differently for the two regions? Should this work in us-west? Is > > there any other information I can post to help you guys in helping me > > troubleshoot the issue? ---
**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:** [December 23, 2010, 7:16am UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693/4 "2010-12-23T07:16:35Z")
Heya, You can set the endpoint using the cloud.aws.endpoint setting. But, after looking at this a bit more closely, this setting is also used for s3 gateway (not sure if you use it), so they clash. In 0.14, this setting will change to cloud.aws.ec2.endpoint (for the discovery part), but, there will also be a simplified setting called cloud.aws.region that will automatically set things correctly for s3 and ec2, as well as s3 region setting when creating a bucket. Here is the issue: [Cloud AWS: Change endpoint parameters to distinguish between ec2 and s3 · Issue #574 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/issue/574). -shay.banon On Thu, Dec 23, 2010 at 7:44 AM, Gary Benitt [garybenitt@gmail.com](mailto:garybenitt@gmail.com) wrote: > Yeah, it's pretty much what I thought. It ends up pulling up my groups > from us-east instead of us-west - so it's not surprise that there's no > match... > > I'm guessing that this request isn't specifying the region: Sending > Request: POST [http://ec2.amazonaws.com](http://ec2.amazonaws.com) ? I would think that you would > probably need to know that I'm trying to access us-west with another param > and then use the appropriate endpoint for that region ( > [ec2.us-west-1.amazonaws.com](http://ec2.us-west-1.amazonaws.com))? > > On Wed, Dec 22, 2010 at 8:38 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > > > Can you set the logging for discovery.ec2 to TRACE? Lets see when if those > > nodes gets discovered. Do you see anything in the logs? > > > > On Wed, Dec 22, 2010 at 11:47 PM, Gary B. [garybenitt@gmail.com](mailto:garybenitt@gmail.com) wrote: > > > > > I have been able to get everything up and running perfectly in the > > > Amazon us-east region. The config I'm using is leveraging the groups > > > for the two nodes two find each other. > > > > > > I have what I think is an identical setup in the us-west region and > > > the two nodes are not seeing each other - they both startup as > > > master. I've tried a number of other things like setting the > > > availability zone (to us-west-1a), changing the host type, etc., but I > > > can't seem to get it to work. > > > > > > Is there something I should be looking for and/or configuring > > > differently for the two regions? Should this work in us-west? Is > > > there any other information I can post to help you guys in helping me > > > troubleshoot the issue? ---
**Author:** ![Gary\_B](https://avatars.discourse-cdn.com/v4/letter/g/6de8d8/32.png) [@Gary\_B](https://discuss.elastic.co/u/Gary_B)\ **Post date:** [December 23, 2010, 7:42am UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693/5 "2010-12-23T07:42:08Z")
I'm not currently using the s3 gateway functionality so this solution works just fine for me... thanks for pointing it out... And as you say, the simplified setting for region along with the specific endpoints makes a lot of sense... Thanks again for the help... On Wed, Dec 22, 2010 at 11:16 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > Heya, > > You can set the endpoint using the cloud.aws.endpoint setting. But, after > looking at this a bit more closely, this setting is also used for s3 gateway > (not sure if you use it), so they clash. In 0.14, this setting will change > to cloud.aws.ec2.endpoint (for the discovery part), but, there will also be > a simplified setting called cloud.aws.region that will automatically set > things correctly for s3 and ec2, as well as s3 region setting when creating > a bucket. Here is the issue: > [Cloud AWS: Change endpoint parameters to distinguish between ec2 and s3 · Issue #574 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/issue/574). > > -shay.banon > > On Thu, Dec 23, 2010 at 7:44 AM, Gary Benitt [garybenitt@gmail.com](mailto:garybenitt@gmail.com) wrote: > > > Yeah, it's pretty much what I thought. It ends up pulling up my groups > > from us-east instead of us-west - so it's not surprise that there's no > > match... > > > > I'm guessing that this request isn't specifying the region: Sending > > Request: POST [http://ec2.amazonaws.com](http://ec2.amazonaws.com) ? I would think that you would > > probably need to know that I'm trying to access us-west with another param > > and then use the appropriate endpoint for that region ( > > [ec2.us-west-1.amazonaws.com](http://ec2.us-west-1.amazonaws.com))? > > > > On Wed, Dec 22, 2010 at 8:38 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) > > > > > wrote: > > > > > Can you set the logging for discovery.ec2 to TRACE? Lets see when if > > > those nodes gets discovered. Do you see anything in the logs? > > > > > > On Wed, Dec 22, 2010 at 11:47 PM, Gary B. [garybenitt@gmail.com](mailto:garybenitt@gmail.com) wrote: > > > > > > > I have been able to get everything up and running perfectly in the > > > > Amazon us-east region. The config I'm using is leveraging the groups > > > > for the two nodes two find each other. > > > > > > > > I have what I think is an identical setup in the us-west region and > > > > the two nodes are not seeing each other - they both startup as > > > > master. I've tried a number of other things like setting the > > > > availability zone (to us-west-1a), changing the host type, etc., but I > > > > can't seem to get it to work. > > > > > > > > Is there something I should be looking for and/or configuring > > > > differently for the two regions? Should this work in us-west? Is > > > > there any other information I can post to help you guys in helping me > > > > troubleshoot the issue? ---
**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:14am UTC](https://discuss.elastic.co/t/having-a-problem-getting-ec2-discovery-to-work-in-us-west/3693/6 "2017-07-06T04:14:54Z")