-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(codepipeline): CloudFormation deployment role always gets pipeline bucket and key permissions #5190
fix(codepipeline): CloudFormation deployment role always gets pipeline bucket and key permissions #5190
Conversation
…e bucket and key permissions Previously, we only explicitly granted the CloudFormation CodePipeline action deployment role access to the pipeline bucket (and, by extension, its KMS key) when the action was deploying into a different account. However, that meant in the single account case, if the pipeline had a key defined, the role would never be added to the key's policy, and any deployment requiring access to the artifacts bucket (like a Lambda function) would fail. This fixes the bug by always granting the deployment role permissions to the pipeline bucket (and thus the key as well). Fixes aws#5183
Thanks so much for taking the time to contribute to the AWS CDK ❤️ We will shortly assign someone to review this pull request and help get it
|
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request is now being automatically merged. |
Hey @skinny85 - I just ran into this bug and found the issue/PR here. When do you think this fix will land in a release? I am wondering whether to put in a workaround or wait for the next version to include this. Thanks |
@lukehedger it will be part of CDK version |
Thanks @skinny85, that's good to know. I've used the workaround described here #5183 (comment) for now and will watch out for the release. |
Previously, we only explicitly granted the CloudFormation CodePipeline action deployment role access to the pipeline bucket
(and, by extension, its KMS key)
when the action was deploying into a different account.
However, that meant in the single account case,
if the pipeline had a key defined,
the role would never be added to the key's policy,
and any deployment requiring access to the artifacts bucket
(like a Lambda function) would fail.
This fixes the bug by always granting the deployment role permissions to the pipeline bucket (and thus the key as well).
Fixes #5183
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license