AWS::Lambda::Function - Code-ZipFile

[rclark]

2. Scope of request

Support for function code via ZipFile in Lambda functions with any node.js/python runtime

3. Expected behavior

I should be able to use the ZipFile attribute for any node.js/python runtime I choose

6. Category (required) - Will help with tagging and be easier to find by other users to +1

Compute

[kalrish]

Please consider Ruby as well.

[scliffo]

Node.js 8.10 reaches EOL on 31 Dec 2019.
What is the ETA for ZipFile support with Node.js 10.x runtime?

[benkehoe]

@oussemos, it's generally better GitHub etiquette to use reactions rather than "+1" comments, which create clutter and generate notifications. It's the "+😀" button on the header bar for a comment. You can also click an existing reaction to add to it.
See also: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/

[nija-at]

Can we know what the status of this issue is?

With NodeJS8 being deprecated, this feature is crucial for customers to upgrade their Lambda function to Node10 when they are using inline code in their CloudFormation template.

[benkehoe]

[nija-at]

Correcting myself - tried this out myself and it seems that CloudFormation now supports inline code for Nodejs10.

[arnulfojr]

I had faced this issue but for node12.x any updates on support for node12.x?
I think the node12.x support will be released next week in the CDK in version 1.18.0 aws/aws-cdk#5107

[monken]

Guess it's Groundhog Day. Both python3.8 and nodejs12.x are not supported by CloudFormation inline functions. How about a more fundamental fix? Why is this parameter even typed? Let the Lambda API return an error if the desired runtime is not available.

[luiseduardocolon]

Zipfile support for nodejs10.x is deployed and completed. Also, nodejs12.x work is completed and docs will be available soon.

[monken]

@luiseduardocolon Thank you!!

[direvus]

Still no support for inline code with python3.8.

[luiseduardocolon]

Moving from shipped to working on it, because of python 3.8 support not quite being there yet.

[laurelmay]

Will the Python 3.8 support result in a change to the cfnresponse module since the version of botocore in the Python 3.8 Lambda runtime no longer has the vendored requests module?

[ChrisPearce]

Another point to note is that the change is not yet included in https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/ReleaseHistory.html

[dotcypress]

Still currently failing to deploy to us-east-1 with Node 14:
Resource handler returned message: "Invalid request provided: The ZipFile attribute is not supported for the runtime 'nodejs14.x'".

Mine are also Edge Functions.

Same issue on us-east-1

[VincentvdE]

Same issue on eu-central-1

[bitconym]

Node v14.x not working for us-east-1 had to revert to Node v12.x

[ChrisPearce]

With NodeJS 16 then due to reach LTS on 26 Oct 2021, is there also a plan for that to then be supported as well?

[adcreare]

Its absolutely nuts that this is taking so long to get supported.. It's not new functionally, it's just adding that functionality to a current runtime. I don't understand why we are months down the track from that runtime release and this still isn't implemented.. I guess I'll log a case with with out account manager.

[tlindsay42]

Same issue in us-west-2. Reverting to Node.js 12.x worked.

[EBeureux]

Issue still exists with nodejs14.x as of today on eu-west-3...

[heikkima]

I received error The ZipFile attribute is not supported for the runtime 'nodejs14.x'" when I tried to deploy a new edge lambda to us-east-1 region.

I was able to first deploy the same lambda as nodejs12.x and after the CloudFormation stack was in COMPLETE state I updated the lambda to nodejs14.x

It's a temporary work-around but I hope it's helpful for others.

[chipironcin]

Happening in eu-west-1 too 😢
I would prefer not run my code with Node12.x

[bitconym]

History repeats with every new Node.js AWS Lambda runtime https://forums.aws.amazon.com/thread.jspa?threadID=303166

[paulsnappet]

It seems to be a per-account thing for me! Deploying to eu-west-1 in account A works fine, but deploying to same region in Account B gives the dreaded The ZipFile attribute is not supported for the runtime 'nodejs14.x'" message.

[abdennour]

happen in us-east-1 while deploying lambda edge thru cfn.
quick release of the revert will be helpful

[bitconym]

Is this fixed already? We're almost August and Node.js v16 will get into LTS active status in October https://nodejs.org/en/about/releases/ so suppose this will be the new Node.js version in AWS Lambda shortly.
I really think Amazon should make this ZipFile support automatic when a new Node.js version gets implemented into AWS Lambda. Don't get why we need to wait years before this works. Does it really need custom development for each version?

[hortondust]

I was able to deploy a ZipFile with node 14.x in us-west-2 today

[bitconym]

Finally, this works! Just tested with Node.js v14.x in us-east-1 all my Lambdas successfully deployed with the InlineCode directive in the SAM template definition file.

[ChrisPearce]

It is now working for eu-west-2

[hoangenouvo]

working now for ap-southeast-2 region 😃

[vileppanen]

Bumping up --> I'm getting the ZipFile unsupported error in eu-west-1 in my own account, for both node12 and node14.

Is there any written analysis somewhere on what is causing the issue?

[michaelbrewer]

is Python3.9 now also supported

[micahduron]

@michaelbrewer Yes, you can now inline python3.9 code using ZipFile.

We introduced a change that enables the use of the ZipFile property with all nodejs and python runtimes, so newly released versions of these runtimes will have day-one support for inlined code.