feat: Allow setting KMS key rotation period #3546
Merged
+8
−0
Conversation
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
ranimbal
changed the title
bryantbiggs
changed the title
bryantbiggs
approved these changes
Oct 14, 2025
bryantbiggs
merged commit fd490ea
into
terraform-aws-modules:master
21 of 22 checks passed
antonbabenko
pushed a commit
that referenced
this pull request
Oct 14, 2025
## [21.4.0](v21.3.2...v21.4.0) (2025-10-14) ### Features * Allow setting KMS key rotation period ([#3546](#3546)) ([fd490ea](fd490ea))
|
This PR is included in version 21.4.0 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
If creating a KMS key for cluster encryption, make it's key rotation period configurable.
Motivation and Context
The current AWS default KMS key rotation period is 365 days. The setting to make this period configurable is currently not exposed by the
terraform-aws-eksmodule. We have security requirements to configure this period to be 90 days.Breaking Changes
No breaking changes.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request