-
Notifications
You must be signed in to change notification settings - Fork 2
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
question about limits #1
Comments
Going to close this, sorry. I was scatter brained yesterday and was grasping at straws here. We are going to look into the I asked about the RFC in the aws-cdk gitter channel, hopefully I'll get a response there. |
Hey @polothy , thanks for opening the issue. I think your questions make a lot of sense :). Let me try to address them in turn.
|
Thanks for taking the time to answer my questions, I really appreciate it! # 1
This was me confused on how lambdas are actually deployed. I thought that you needed to make a dedicated S3 bucket for it to constantly serve the code from. Apparently you just need it for deployment then that's it. So my bad. # 2Thanks for confirming. With the RFC, it looks like this could be handled for us so we wouldn't have to do something per lambda. # 3Thanks. # 4Awesome! Really happy to see this and also to get an idea of what to expect so we can plan around it a little. I 100% realize nothing it set in stone and it'll change over time. |
Hello - thanks for the example! I had a few questions though:
Using this method to deploy lambdas, do you run into the 50MB zip limit? From what I can tell, the code is uploaded to lambda vs served via S3 on each lambda invoke.
In addition, if you wanted to deploy multiple lambdas (think of a microservice that uses API Gateway and a lambda per endpoint), would you need to make a secondary artifact for each lambda? Otherwise, I think the artifact would group all the lambdas into a single zip?
From what I can gather, right now, the best lambda deploy experience is using
from_asset
on the lambda definitions and then usingcdk deploy
. We need to target multiple accounts and regions, so I'm guessing I would make a CodeBuild with a role that assumes different accounts then runAWS_REGION=region cdk deploy
. This is likely fine, but the UX is not quite a nice as using CodePipeline with Cloudformation Create ChangeSet > manual approve > Cloudformation Apply ChangeSet.Lastly, RFC: 0049 Continuous Delivery for CDK Apps aws/aws-cdk#3437 might be the answer we need, but having trouble finding status on it.
Feel free to say "don't ask this here" and point me somewhere else 😄
The text was updated successfully, but these errors were encountered: