-
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
[@aws-cdk/pipelines] have ability to use the same IAM role for multiple deploying assets #9066
Labels
Comments
seawatts
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
Jul 14, 2020
SomayaB
changed the title
[aws-cdk/pipelines] have ability to use the same KMS key for multiple deploying assets
[@aws-cdk/pipelines] have ability to use the same KMS key for multiple deploying assets
Jul 15, 2020
ericzbeard
added
p1
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Jul 15, 2020
I am seeing this issue as well with about 35 Lambdas and respective API Gateway routes. Nothing much else. |
2 tasks
@njlynch can you take a look at this? |
seawatts
changed the title
[@aws-cdk/pipelines] have ability to use the same KMS key for multiple deploying assets
[@aws-cdk/pipelines] have ability to use the same IAM role for multiple deploying assets
Jul 22, 2020
I dug a little deeper and it turns out it's not the KMS keys that are taking up too much space it's the Roles that get created for each asset. |
Similar issue that I created today: #9237 |
njlynch
added a commit
that referenced
this issue
Jul 24, 2020
This change combines the two roles (and policies) per pipeline asset into a single role + policy for all assets in a pipeline. In a small pipeline with only 3 assets, this reduced the overall template size by a third. With a pipeline stack with 30 assets, this change reduces the template size from 363111 bytes to 190223 bytes. Tested on a cross-account pipeline to verify permissions were retained. fixes #9066 mitigates #9225 mitigates #9237
mergify bot
pushed a commit
that referenced
this issue
Jul 28, 2020
…ies (#9243) This change combines the two roles (and policies) per pipeline asset into a single role + policy for all assets in a pipeline. In a small pipeline with only 3 assets, this reduced the overall template size by a third. With a pipeline stack with 30 assets, this change reduces the template size from 363111 bytes to 190223 bytes. Tested on a cross-account pipeline to verify permissions were retained. fixes #9066 mitigates #9225 mitigates #9237 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
curtiseppel
pushed a commit
to curtiseppel/aws-cdk
that referenced
this issue
Aug 11, 2020
…ies (aws#9243) This change combines the two roles (and policies) per pipeline asset into a single role + policy for all assets in a pipeline. In a small pipeline with only 3 assets, this reduced the overall template size by a third. With a pipeline stack with 30 assets, this change reduces the template size from 363111 bytes to 190223 bytes. Tested on a cross-account pipeline to verify permissions were retained. fixes aws#9066 mitigates aws#9225 mitigates aws#9237 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently a new role gets created for every asset being uploaded gets it's own Role. This causes a problem when you have a lot of assets being deployed. The template that gets created becomes too large for CF to deploy it correctly.
Use Case
To deploy a larger amount of assets with the new aws-cdk/pipelines
Proposed Solution
Be able to pass in a role, or have the construct reuse the same one under the hood.
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: