# Why does discovery-gce need write permissions

**URL:** <https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972>\
**Category:** Elasticsearch\
**Created:** [July 6, 2018, 6:12pm UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972 "2018-07-06T18:12:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vangap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vangap/32/44927_2.png) [@vangap](https://discuss.elastic.co/u/vangap)\
**Post date:** [July 6, 2018, 6:12pm UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/1 "2018-07-06T18:12:24Z")

</div>

According to this [https://www.elastic.co/guide/en/elasticsearch/plugins/6.3/discovery-gce-usage-long.html](https://www.elastic.co/guide/en/elasticsearch/plugins/6.3/discovery-gce-usage-long.html)  
we need to give write permissions to the instance.

Can someone tell me why it needs write permissions?

AWS counterpart plugin just requires ListInstances permission. I would like to know what is different w.r.t GCP

Thanks.

---

<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:** [July 6, 2018, 7:12pm UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/2 "2018-07-06T19:12:01Z")

</div>

I don't remember TBH. May be read is enough but I think that last time I tried it did not work. Did you try it?

---

<div class="post-metadata">

**Author:** ![vangap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vangap/32/44927_2.png) [@vangap](https://discuss.elastic.co/u/vangap)\
**Post date:** [July 7, 2018, 3:19am UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/3 "2018-07-07T03:19:55Z")

</div>

I took it for granted since the documentation says it, but I just tested it now. It works with read only permissions also.  
Maybe, the documentation needs an update.

Thanks.

---

<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:** [July 7, 2018, 3:51am UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/4 "2018-07-07T03:51:53Z")

</div>

Great! Wanna contribute to the project and propose a PR for this?

---

<div class="post-metadata">

**Author:** ![vangap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vangap/32/44927_2.png) [@vangap](https://discuss.elastic.co/u/vangap)\
**Post date:** [July 7, 2018, 1:19pm UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/5 "2018-07-07T13:19:24Z")

</div>

I am just getting started with GCP, I am not sure if my knowledge would be sufficient to update the docs.  
But, I will take a look at it and see, I guess this is the place to contribute?

> <https://github.com/elastic/elasticsearch/blob/6.3/docs/plugins/discovery-gce.asciidoc>

Thans.

---

<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:** [July 7, 2018, 1:42pm UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/6 "2018-07-07T13:42:22Z")

</div>

It is!

Thanks!

---

<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:** [August 4, 2018, 1:42pm UTC](https://discuss.elastic.co/t/why-does-discovery-gce-need-write-permissions/138972/7 "2018-08-04T13:42:23Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.