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.
This moves us away from using the AWS managed
IAMFullAccess
andSecretsManagerReadWrite
policies, and uses our own custom policy instead, giving the limited permscloud-key-rotator
requires for IAM and SSM.I've tested this in a nonprod AWS account and looks good from that perspective.
A new variable
enable_ssm_location
has been introduced, as users won't always require the extra perm required to use SSM as an output location ofcloud-key-rotator
.I bumped the module version from
0.0.6
to0.1.0
.