fix(autoscaling): ssmSessionPermissions does not add managed policy to role specified in launch template#27220
Conversation
…o role specified in launch template
lpizzinidev
left a comment
There was a problem hiding this comment.
Looks good to me 💪 Thanks!
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
When we set ssmSessionPermissions to true, CDK adds
AmazonSSMManagedInstanceCoremanaged policy to role specified in AutoScalingGroup construct. However, if the role specified in not AutoScalingGroup construct's prop but launch template, ssmSessionPermissions has no effect.This PR solves the issue by adding the managed policy even when role is specified in launch template.
Closes #25904
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license