fix: Update kms policy for root user - #256
Open
shivawandb wants to merge 2 commits into
Open
Conversation
shivawandb
changed the title
Contributor
|
Nice, this should prevent orphaned keys. Any docs we should update to let users know that roles with kms perms in the same account will have access to manage these kms keys? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
KMS policies has its own permissions which allows specific users to take certain actions. These permissions override regular IAM permissions and therefore need to be configured correctly during creation. This change allows the root user of the aws account to modify kms keys. The root user should never be used in the first place but this serves as a break glass use case.