Skip to content

feat: add KMS encryption policy for EKS cluster roles - #99

Open
kav wants to merge 1 commit into
mainfrom
feat/kms-encryption-policy
Open

feat: add KMS encryption policy for EKS cluster roles#99
kav wants to merge 1 commit into
mainfrom
feat/kms-encryption-policy

Conversation

@kav

@kav kav commented Feb 26, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds kms_key_arns variable (list(string), default [])
  • When KMS key ARNs are provided, creates an IAM policy granting kms:Encrypt, kms:Decrypt, kms:GenerateDataKey*, kms:DescribeKey, kms:ReEncrypt*, and kms:CreateGrant permissions
  • Attaches the policy to the EKS cluster IAM role
  • No resources created when kms_key_arns is empty (backward compatible)

Test plan

  • Run tofu validate to verify syntax
  • Run tofu plan with default (empty list) — no new resources expected
  • Run tofu plan with KMS ARNs — policy and attachment should appear

🤖 Generated with Claude Code

@kav
kav force-pushed the feat/kms-encryption-policy branch from 3006f41 to 28e0acc Compare February 26, 2026 23:19
@josmo

josmo commented Mar 5, 2026

Copy link
Copy Markdown
Member

I'm pretty this should use kms_key_users

@emmanuel
emmanuel force-pushed the feat/kms-encryption-policy branch from 28e0acc to 2feae44 Compare May 27, 2026 23:38
@emmanuel
emmanuel requested a review from a team as a code owner May 27, 2026 23:38
# Conflicts:
#	variables.tf
@emmanuel
emmanuel force-pushed the feat/kms-encryption-policy branch from 2feae44 to 73f8b6d Compare May 27, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants