nebari-dev / nebari-dev/nebari-docs
[DOC] - Document minimal GCP IAM permissions required for deploying and destroying Nebari
Open
@marcelovilla is already working on this.
Since Jun 9, 2025.
area: documentation 📖
area: user experience 👩🏻💻
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Preliminary Checks
- This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions
Summary
Currently, our docs suggest to use a service account with four predefined roles attached. However, these are very broad permissions and they're far from ideal from a security and principle-of-least-privilege standpoint.
We should define and document custom GCP IAM roles with just enough permissions to deploy and destroy Nebari. This will help users follow best practices and safely integrate Nebari into more restrictive cloud environments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.