docs: added documentation for minimal iam permissions #775
Conversation
This file contains 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
mjsterckx
force-pushed
the
minimal-permissions
branch
2 times, most recently
from
41a5579 to
856ce3f
Compare
|
Looks good so far. |
mjsterckx
force-pushed
the
minimal-permissions
branch
from
856ce3f to
aadebd9
Compare
ecpullen
approved these changes
Feb 28, 2023
stmcginnis
approved these changes
May 18, 2023
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.
Issue number:
Related: #417
Description of changes:
Added a
bottlerocket/docs/permissionsfolder that stores one or more JSON files for each agent. The files contain the minimal IAM permissions needed to create and run the test/resource. Added aMINIMAL-PERMISSIONS.mdfile that maps each sample test file inbottlerocket/samplesto the corresponding minimal IAM permissions.The JSON files were generated by running the sample test files with a different assume_role per test/resource. These assume_roles had
Administratorpermissions, and using CloudTrail, it was possible to see which permissions were actually used by that role from the time of creation to the time of deletion.Testing done:
N/A
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.