You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same thing to what it's doing now, but instead of sending the zip directly to AWS lambda, it first uploads it to a predefined bucket/key(prefix) and deploys from s3.
Advantage: size limits seem to be much higher when deploying from s3, 250meg zips, vs direct zip upload which is limited to 50megs.
The text was updated successfully, but these errors were encountered:
I think that it is useful to upload it to S3 and deploy it.
However, I think that the upper limit of the zip file size does not change even if uploading to S3.
250 MB seems to be the size of the code before compression.
Same thing to what it's doing now, but instead of sending the zip directly to AWS lambda, it first uploads it to a predefined bucket/key(prefix) and deploys from s3.
Advantage: size limits seem to be much higher when deploying from s3, 250meg zips, vs direct zip upload which is limited to 50megs.
The text was updated successfully, but these errors were encountered: