# Discovery in gov-cloud?

**URL:** <https://discuss.elastic.co/t/discovery-in-gov-cloud/33308>\
**Category:** Elasticsearch\
**Created:** [October 29, 2015, 9:09pm UTC](https://discuss.elastic.co/t/discovery-in-gov-cloud/33308 "2015-10-29T21:09:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hibernal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hibernal/32/5581_2.png) [@hibernal](https://discuss.elastic.co/u/hibernal)\
**Post date:** [October 29, 2015, 9:09pm UTC](https://discuss.elastic.co/t/discovery-in-gov-cloud/33308/1 "2015-10-29T21:09:25Z")

</div>

Looking in elasticsearch-cloud-aws, it seems that discovery can't happen in gov-cloud. Is there an upstream version of the plugin that includes gov-cloud endpoints or is there another workaround? Going with a hacked version for now but...

---

<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:** [October 29, 2015, 9:58pm UTC](https://discuss.elastic.co/t/discovery-in-gov-cloud/33308/2 "2015-10-29T21:58:05Z")

</div>

Will be supported with [https://github.com/elastic/elasticsearch/pull/14358](https://github.com/elastic/elasticsearch/pull/14358)

In the meantime you can provide the endpoint you want IIRC.

---

<div class="post-metadata">

**Author:** ![hibernal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hibernal/32/5581_2.png) [@hibernal](https://discuss.elastic.co/u/hibernal)\
**Post date:** [November 1, 2015, 11:24pm UTC](https://discuss.elastic.co/t/discovery-in-gov-cloud/33308/3 "2015-11-01T23:24:48Z")

</div>

Good to know, thank you!

You can indeed set an endpoint, but I'd have to templatize gov cloud configs differently than non-gov cloud ( because the config variable name is different ). Plus wasn't sure if I'd later need to change the config ( e.g., if at some point the though might be gov-cloud is strictly part of ec2 so disallow from the compliant but non-ec2 group ). So it is an option but one I had hoped to avoid.

---

<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 5, 2017, 11:41pm UTC](https://discuss.elastic.co/t/discovery-in-gov-cloud/33308/4 "2017-07-05T23:41:24Z")

</div>


