Michael Brewer

@yuth What is the benefit of this? Why not just use AWS Sam to handle the bundling of the lambda? even CDK does not inflate the lambda by 2.6mb with...

@edwardfoyle - amplify console does not support Python 3.8 https://github.com/aws-amplify/amplify-console/issues/595 Most lambdas don't need many dependencies (and some have none at all outside of AWS SDK) So in most cases...

@edwardfoyle i don't quite understand why the actual deployed lambda needs to be 2.6mb, these are not runtime dependencies but build time dependencies? Here is the example lambda for python...

Note how AWS-CDK does this without bloating the lambda with unused libraries : https://github.com/aws/aws-cdk/tree/master/packages/%40aws-cdk/aws-lambda-python As a develop you just need to have Docker installed.

@edwardfoyle @yuth - will anyone look into fixing this? I can see that AWS does care about the cost of cold starts (https://aws.amazon.com/blogs/developer/modular-aws-sdk-for-javascript-release-candidate/), and this seems to be inconsistent.

Maybe @heitorlessa has some input on how to support Python lambdas in a clean way. It would be nice to support SAM or do what CDK does when building Lambda...

Hopefully the tools improves soon. As we are planing to build all of our lambdas in Python

Thanks @heitorlessa for offering an ear for this. I do like how sam can bootstrap a lambda with the build tools and sample code: ```script sam init --location https://github.com/aws-samples/cookiecutter-aws-sam-python ```...

@kaustavghosh06 what is the timeline on this? Otherwise `amplify function build` does not seem to work, it just hangs without completing.

RE: `amplify function build` failing Oh i see that this is a separate issue (which is NOT being fixed): * https://github.com/aws-amplify/amplify-cli/issues/6159