doc: Add permissions that IAM roles for Loki need #961
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
Currently, it's difficult to determine what permissions Loki needs to operate against S3 and DynamoDB from the provided documentation. This commit adds the permissions necessary to operator Loki, to provide admins guidance on how they can run Loki with the least possible privilege.
|
|
worr
changed the title
cyriltovena
approved these changes
Sep 3, 2019
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.
What this PR does / why we need it:
Currently, it's difficult to determine what permissions Loki needs to operate against S3 and DynamoDB from the provided documentation. This commit adds the permissions necessary to operator Loki, to provide admins guidance on how they can run Loki with the least possible privilege.