fix: add kms:Encrypt permission, as needed since f25a86b5 #1008
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
Since the addition of KeyId to the SSM parameter used to store the registration token, the replacement of the parameter following a failed token verification fails. This is due to a missing Encrypt permission on the customer managed KMS key.
The initial put-parameter presumably passes due to a shortcut on the encryption when the value is null, but the subsequent overwrite attempt fails.
Migrations required
NO
Verification
Manual addition of the kms:Encrypt permission has been proved to resolve the runner start-up failure