Use more restrictive IAM policy #95
Merged
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
|
I created #96 to fix the issue with |
|
#sre |
|
For Qonto's review: The policy is successfully deployed in our different AWS accounts. |
|
#sre |
vmercierfr
force-pushed
the
fix-iam-policy
branch
from
bdd7f72
to
05dbd44
Compare
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.
Objective
Use more restrictive IAM policy
Why
Help AWS users to audit and adjust IAM permissions to enable features.
For instance, it will be easier for users who don't collect log information (
collect-logs-size=false) to remove unnecessary IAM permissions.Today, we don't specify parameters to collect AWS RDS maintenances, so we can't limit
resourceforrds:DescribePendingMaintenanceActionsaction, but we may support in the future.How
Release plan