4 ms·

Surely .NET usage on AWS lambda is nowhere close to Node.js, and the Node.js 16 LTS has been out for almost a year and there's still no support for it.

• otterley 5y ago
  Amazonian here! (Speaking for myself, not for the company.) You can use any runtime you like for your Lambda functions, even if it's not supported as a first-class native runtime. The simplest way is to build a container image that has the runtime you want to use. All you need to do is to include the Lambda Runtime Interface Client with your image, and set the proper ENTRYPOINT. See https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/ https://aws.amazon.com/blogs/aws/new-for-aws-lambda-containe... for a blog post, and https://docs.aws.amazon.com/lambda/latest/dg/images-create.html https://docs.aws.amazon.com/lambda/latest/dg/images-create.h... for the reference documentation. Once you get the hang of it, it's super easy, and you may never want to go back to the old way!
  • solatic 5y ago
    Doesn't using a container image hurt the Lambda experience a lot? Longer cold start times, needing to maintain the userland dependencies (and not just the language-level dependencies) in the container image?
    • suzzer99 5y ago
      Yeah how about we just get native support for node 16 please.
• phillipcarter 5y ago
  Just speculation, but there may be different teams (or subsets of teams) responsible for different kinds of bindings, and it may be easier to support the latest .NET LTS than the latest Node LTS.