Cloudformation-coverage-roadmap: 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 https://github.com/aws/aws-cdk/pull/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.

[kylelaker]

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?

[PatMyron]

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.

I think this is the key. ZipFile is currently restricted to Lambda Runtimes with cfn-response support. While there may be more work for cfn-response support, I think that restriction should be removed because ZipFile support is still useful without cfn-response support

[takeda]

Any update on enabling ZipFile for python3.8?

[nico-oculusd]

Bump: Any update on enabling ZipFile for python3.8?

[tjstansell]

@PatMyron According to https://github.com/awslabs/aws-cloudformation-templates/commit/44b76a1f694f82eeee14fe804bf9dc973fdc2230#diff-c5c12db01c1b4f18f951451d08e7828f, cfnresponse has not depended on the requests library since April 29, 2020... there should be nothing blocking adding python3.8 support in ZipFile. Can anyone here comment on a timeline for this?

[luiseduardocolon]

Hello there. Just wanted to let you know that we expect to release this soon, hopefully in the coming days, barring any last-minute regression.

[bchew]

@luiseduardocolon I've just tried to deploy using ZipFile with nodejs14.x, have gotten the failure back from CloudFormation: ZipFile can only be used when Runtime is set to either of nodejs8.10, nodejs10.x, nodejs12.x, python2.7, python3.6, python3.7, python3.8.

[anirudhsaligram]

~I see the same issue as @bchew here.~

[jensrutschmann]

@luiseduardocolon nodejs14.x is still not available for use with ZipFile. That's quite annoying because node 14 is the current LTS and because it's unavailable I need to migrate from node 10 to 12 now (when it's already known that node 16 will be the next LTS later this year). Wish I could upgrade to 16.
Any news when at least node 14 will be available for ZipFile?

[brianterry]

@jensrutschmann , nodejs14.x is now supported.

Please review the docs at:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html

[yerzhan7]

I have just tried to deploy to eu-west-1 region and still got error:

Resource handler returned message: "Invalid request provided: The ZipFile attribute is not supported for the runtime 'nodejs14.x'" (RequestToken: 5be7b547-9896-877d-b30f-7fd299b22b32, HandlerErrorCode: InvalidRequest)

Please re-open the issue, thanks.

[danilobuerger]

@yerzhan7 @brianterry For me it worked just fine on us-east-1. Maybe its not deployed to every region yet?

[brianterry]

Thanks, @danilobuerger. We are researching.

[bchew]

I've just tested redeploying the same stack which failed back in February per previous comment, worked fine in us-west-2 region with nodejs14.x. Thanks @brianterry!

[ChrisPearce]

Unfortunately it is not working in eu-west-2

[Canuteson]

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.

[hoangenouvo]

same error with @Canuteson when build on ap-southeast-2 region

[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

[imjustd]

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.