-
Notifications
You must be signed in to change notification settings - Fork 35
Add example IAM policies with minimum permissions to deploy and destoy Nebari in AWS #581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
marcelovilla
wants to merge
7
commits into
main
Choose a base branch
from
add-minimum-aws-permissions
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nimum permissions to deploy and destroy Nebari
✅ Deploy Preview for nebari-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viniciusdc
approved these changes
Jun 3, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
viniciusdc
reviewed
Jun 3, 2025
|
||
As a [best practice](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#lock-away-credentials), do not use the AWS account `root` user for any task where it's not | ||
required. Instead, create a new IAM user for each person that requires administrator access. Then make those users administrators by placing them into an "Administrators" user | ||
group, to which you attach the `AdministratorAccess` managed policy. | ||
required. Instead, create a new IAM user for each person that requires administrator access. Then make those users administrators by placing them into an "Administrators" (or any other name) user group, to which you attach the policies outlined above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If possible, include a link for this or an image
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds two example IAM policies with the minimium required permissions to deploy and destroy Nebari on the Deploy Nebari on AWS of the How-to Guides section.
Reference Issues or PRs
Closes #580
xref: #107, #231
What does this implement/fix?
Put a
x
in the boxes that applyTesting
Documentation
Access-centered content checklist
Text styling
H1
or#
in markdown).Non-text content
Any other comments?
The two policies added in this PR were initially written using https://github.com/iann0036/iamlive 1 when deploying and destroying Nebari. However, manual changes to the generated policies were needed as there were still some permissions missing.
I tested this PR by both deploying to AWS locally and triggering Nebari's deployment tests after changing our CI role's permissions. Here's a successful run for reference.
To test this PR yourself, you can:
If you succeed without running into
PermissionDenied
errors, you're good to go.Footnotes
To reproduce, run the following command in one window:
And then, export the following environment variables in the terminal where you will run the
↩nebari deploy
andnebari destroy
commands: