feat: add KMS encryption policy for EKS cluster roles#99
Open
Conversation
kav
force-pushed
the
feat/kms-encryption-policy
branch
from
3006f41 to
28e0acc
Compare
Member
|
I'm pretty this should use kms_key_users |
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.
Summary
kms_key_arnsvariable (list(string), default[])kms:Encrypt,kms:Decrypt,kms:GenerateDataKey*,kms:DescribeKey,kms:ReEncrypt*, andkms:CreateGrantpermissionskms_key_arnsis empty (backward compatible)Test plan
tofu validateto verify syntaxtofu planwith default (empty list) — no new resources expectedtofu planwith KMS ARNs — policy and attachment should appear🤖 Generated with Claude Code