AWS is rolling out updates to AWS Lambda execution environment

[dmateos]

Hey,

Not sure if this exactly belongs here but just want to flag it for discussion.

Is there anything we need to worry about with this notification from AWS?

https://aws.amazon.com/blogs/compute/upcoming-updates-to-the-aws-lambda-execution-environment/

[dansayo]

posted on the Zappa Slack AWS channel

[kikeh]

@dansayo I am not able to see the Zappa Slack, is there any way for me to access or could you share what has been posted? Thanks!

[dmateos]

so to test this now all we need to do in the AWS console is apply the layer arn:aws:lambda:::awslayer:AmazonLinux1803 to current zappa deployed lambdas if im reading the docs right?

[xoelop]

posted on the Zappa Slack AWS channel

I can't also get sign in, how can I request access? Thanks!

[gricey432]

The lambda-packages repo used by zappa is probably where most of the concern would be Miserlou/lambda-packages#102

[gricey432]

@kikeh @xoelop there's a link on the repo homepage to the slack join tool; https://slack.zappa.io/

[kikeh]

@gricey432 Great! Thanks!

[dmateos]

Have done some basic tests on our dev with the new layer and there doesn't seem to really be any dramas so far.

[wagmiwiz]

We tested and this breaks our app as things currently stand. This is due to our reliance on crypography from lambda-packages, which is compiled against current version of Amazon Linux for Lambda. I think we will either have to start including a custom compile, upgrade lambda-packages, or work on this particular enhancement #1861

[suriya]

Could we accept pull request #1842 so that we can have layers support in Zappa. I was able to use the feature in the pull request and configure

"layers": ["arn:aws:lambda:::awslayer:AmazonLinux1703"],

in my Zappa settings file so that we could defer the OS upgrade.

[dmateos]

You can also just manually set it via the AWS UI from what ive seen, a function update doesnt seem to be getting rid of that.

[wagmiwiz]

FYI, we also found out that if you use Python 3.7 (which means there are no lambda-packages to fall back to, which does happen with python 2.7/3.6 - it will use an older lambda-package of your binary and warn you about it), AND deploy Zappa from Linux, then cryptography works just fine. This is because Zappa in that case doesn't use manylinux, nor lambda packages, and relies on loc virtual env version, which includes the correct abi3 binary. Perhaps lambda-packages should now be made optional in Zappa, PRs welcome.

[suriya]

@nikbora What about older version of python 2.7 / 3.6, etc.? If we do not use lambda-packages, will the manylinux versions run on the old and new AWS environment?