feat: Allow removing KMS and SSM permissions from EKS IRSA external secrets policy #550
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
brycelowe
changed the title
brycelowe
changed the title
|
This PR has been automatically marked as stale because it has been open 30 days |
brycelowe
force-pushed
the
bjl/fix/resource-error-without-kms-arns
branch
from
be40269 to
549ea31
Compare
|
Proposed fix for #557 |
1 task
I'd like the option to remove access to KMS and SSM permissions on my IRSA roles while still providing the ability to use this module with the default encryption key provided by AWS. When I attempt to provide an empty list, the IAM policy is invalid because a resource definition is required.
brycelowe
force-pushed
the
bjl/fix/resource-error-without-kms-arns
branch
from
549ea31 to
82eab62
Compare
bryantbiggs
changed the title
bryantbiggs
approved these changes
Apr 14, 2025
antonbabenko
pushed a commit
that referenced
this pull request
Apr 14, 2025
## [5.55.0](v5.54.1...v5.55.0) (2025-04-14) ### Features * Allow removing KMS and SSM permissions from EKS IRSA external secrets policy ([#550](#550)) ([bfaa70d](bfaa70d))
|
This PR is included in version 5.55.0 🎉 |
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.
Description
I'd like the option to remove access to KMS and SSM permissions on my IRSA roles while still providing the ability to use this module with the default encryption key provided by AWS. When I attempt to provide an empty list, the IAM policy is invalid because a resource definition is required.
Motivation and Context
Most of the secrets in my environment have been created with the default encryption key, so they don't need any special access to KMS or SSM. When attempting to remove this permission I ran into an error applying the configuration because the policy document was malformed.
Resolves #557
Breaking Changes
No, this is not a breaking change as the existing default remains intact.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request