# Limiting the scope of permissions for GCS backups

**URL:** <https://discuss.elastic.co/t/limiting-the-scope-of-permissions-for-gcs-backups/274166>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [May 27, 2021, 9:11am UTC](https://discuss.elastic.co/t/limiting-the-scope-of-permissions-for-gcs-backups/274166 "2021-05-27T09:11:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pkaramol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pkaramol/32/22610_2.png) [@pkaramol](https://discuss.elastic.co/u/pkaramol)\
**Post date:** [May 27, 2021, 9:11am UTC](https://discuss.elastic.co/t/limiting-the-scope-of-permissions-for-gcs-backups/274166/1 "2021-05-27T09:11:55Z")

</div>

According to the [docs](https://www.elastic.co/guide/en/cloud/current/ec-gcs-snapshotting.html#ec-gcs-service-account-key), the `storage.Admin` role needs to be granted to the GCP service account that will be used for GCS snapshotting.

However, (unless I am mistaken) this is a rather broad role giving full access to all GCS buckets of the corresponding GCP project.

Is there an option to just use a role with full permissions to the bucket where the snapshots will be stored in?

---

<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:** [June 24, 2021, 9:12am UTC](https://discuss.elastic.co/t/limiting-the-scope-of-permissions-for-gcs-backups/274166/2 "2021-06-24T09:12:49Z")

</div>

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