I'm getting the following error:

Unknown application error occurred
Runtime.ErrorLoadingHandler

And the only thing I'm changing between it working and this failure state is the node version. Previously I was using AWS' node14. Here's my js:

// index.js
export async function entry(event) {
  return {
    statusCode: 200,
    headers: {
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      result: 'success',
    }),
  };
}

tf:

resource "aws_lambda_function" "api_api" {
  function_name = random_pet.lambda_api_function.id

  s3_bucket = aws_s3_bucket.api_bucket.id
  s3_key    = aws_s3_bucket_object.api_bucket_obj.key

  runtime = "provided"
  layers  = ["arn:aws:lambda:us-east-1:072686360478:layer:node-16_9_1:3"] # https://github.com/fusebit/everynode
  handler = "index.entry"

  source_code_hash = data.archive_file.lambda_api.output_base64sha256

  role = aws_iam_role.api_exec.arn

  tags = var.tags
}

There's a space in the Fusebit URL at the top of the README.md that the fuse bit logo links to.

I tried a couple of different browsers, and neither of them would navigate to Fusebit, which means that people can't easily click through.

I could make a PR, but a forking your codebase and making a PR to remove a single space is probably overkill. ;)

I am using a AWS::Serverless::Function resource to deploy my Lambda function.

I added arn:aws:lambda:eu-west-1:072686360478:layer:node-16_0_0:3 as a Layer to my function, and set runtime to provided.

Deployed the stack, but when running the Lambda, I get

Unknown application error occurred Runtime.ErrorLoadingHandler

My cloudformation config for the Lambda

MyLambdaFunction:
    Type: 'AWS::Serverless::Function'
    Description: create endpoint
    Properties:
      Handler: index.main
      CodeUri: ../.dist/lambda/Create/lambda.zip
      Runtime: provided
      Timeout: 5
      MemorySize: 768
      Role: !GetAtt LambdaRole.Arn
      Environment:
        Variables:
          REGION: !Ref AWS::Region
      Layers:
        - arn:aws:lambda:eu-west-1:072686360478:layer:node-16_0_0:3
        - !Ref Layer

When running on the new 18_0_0:1 layer, lambdas fail with the following errors:

/opt/node/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/node/bin/node)
/opt/node/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /opt/node/bin/node)
/opt/node/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/node/bin/node)

This is presumably caused by the toolchain changes mentioned in the blog post: https://nodejs.org/en/blog/announcements/v18-release-announce/#toolchain-and-compiler-upgrades

START RequestId: 7cfca2a1-9f55-43b4-af5c-af4d7339cc20 Version: $LATEST
/opt/node/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/node/bin/node)
/opt/node/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /opt/node/bin/node)
/opt/node/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/node/bin/node)
END RequestId: 7cfca2a1-9f55-43b4-af5c-af4d7339cc20
REPORT RequestId: 7cfca2a1-9f55-43b4-af5c-af4d7339cc20	Duration: 40.55 ms	Billed Duration: 41 ms	Memory Size: 256 MB	Max Memory Used: 4 MB	
RequestId: 7cfca2a1-9f55-43b4-af5c-af4d7339cc20 Error: Runtime exited with error: exit status 1
Runtime.ExitError

Hello, how can this project work with Serverless?

I'd like to deploy a lambda function with this layer using Serverless, but it has a HandlerNotFound error or a ModuleNotFound error on my handler. If I remove runtime: 'provided', the handler is found fine, but the process.env shows version is still 14.

Any ideas?

This is the second time I’ve seen this repo posted, so I thought I’d ask about docker support 😄 There used to be https://github.com/lambci/lambci, but it is no longer maintained

Docker images can be found on https://hub.docker.com/r/amazon/aws-lambda-nodejs and https://gallery.ecr.aws/lambda/nodejs

More information on using docker with AWS Lambda can be found:

• https://docs.aws.amazon.com/lambda/latest/dg/nodejs-image.html
• https://docs.aws.amazon.com/lambda/latest/dg/images-create.html
• https://www.serverless.com/blog/container-support-for-lambda

These resources may also be helpful:

• https://www.npmjs.com/package/aws-lambda-ric
• https://docs.docker.com/develop/develop-images/multistage-build/

While attempting to test this repo I encountered a couple of hiccups. First, I wasn't seeing the node version updated when checking inside my Lambda runtime. After some testing I realized that my runtime in my Lambda template was still set to "nodejs14.x" which was overriding any changes the Lambda made. This setting would be useful to highlight in the readMe.

Second, I'm having issues getting other layers to work when using in conjunction with this repo. For my use case it seems that using a node shebang declaration in my other layer fails. This layer works when using AWS node runtimes so it seems that the layer has changed other parts of the environment outside of node version. This likely just requires some tweaking on my end but it would be helpful to include some documentation on how running an everynode layer differs from the standard AWS node runtime.

#!/usr/bin/env node

/usr/bin/env: node: No such file or directory

Appreciate the work here. Very interesting feature!

Hey friends!

This library is super amazing and I am a huge fan of the work being done here. I was just curious if it might be helpful though to write out some of the drawbacks, if there are any, in the readme. For example, since it's using a lambda layer, I assume this means it will cut into the space available per lambda. The normal limit is ~250mb, and node image layers are ~100mb. Additionally, is there a performance penalty incurred when loading node through the layer on a cold boot? Is there anything else I'm missing?

Not trying to be a downer at all here, I just want to make sure that the tradeoffs are clear for anyone thinking about adopting 😁