-
Notifications
You must be signed in to change notification settings - Fork 113
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
Issues with remote (backend) function building & size constraints ("Unzipped size must be smaller than..") #3908
Comments
This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you! |
Some additional info, |
Ok.. not sure what's going on here. I have just built a new test:
I downloaded the remote package via the lambda portal and it is showing Not sure why the 2. test from my first post failed, as the local build unzipped is larger in this test. |
If you are still experiencing this can you open an AWS support case? |
This issue is now closed. Comments on closed issues are hard for our team to see. |
This issue has been automatically locked. |
Before opening, please confirm:
Amplify Hosting feature
Backend builds, Deployments
Is your feature request related to a problem? Please describe:
I am having issues packaging my
python-based amplify function
, due to its size being very close to what seems to be the maximum size. The maximum for a lambda as stated in the amplify backend build logs seems to be262144000 bytes
. Although from the following it seems to be around150 MB
(unzipped)?I have attempted:
43MB zipped, 148.1 MB unzipped
local amplify push
builds and hosts
remote amplify build
builds and hosts
39.5MB zipped, 154MB unzipped
local amplify push:
locally builds and hosts
remote amplify build:
build fails with size error "Unzipped size must be smaller than...".
In 2., after the local amplify push, the built function/lambda is visible in the lambda portal list, and I can download and unzip it to see the correct deps are there. However, any future Amplify builds will fail due to it not being able to package this lambda. I am wondering if this discrepancy is related to:
I have
pipenv clean
'd my function folder. Unfortunately, these dependencies are as minimal that I can get them (for the use case). Will have to write around this for now.Describe how you'd like this feature to work
I think there should be:
Not really sure how easy this would be or if there is anyway to accomplish this currently. Appreciate any information on this.
The text was updated successfully, but these errors were encountered: