feat(codedeploy): change LambdaDeploymentGroup default managed policy to AWSCodeDeployRoleForLambdaLimited #10276
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.
The managed policy
AWSCodeDeployRoleForLambda
used for Lambda deployments has broad permissions, providing publish access to all SNS topics within the customer's accounts.This change replaces that with a new policy
AWSCodeDeployRoleForLambdaLimited
which removes those permissions.This should be safe, as the SNS publish permission is only ever used when setting up
triggers
,and we don't support that feature in
LambdaDeploymentGroup
.BREAKING CHANGE: the default policy for
LambdaDeploymentGroup
no longer containssns:Publish
on*
permissionsBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license