Node.js - Githubissues

marc1aj commented 2 years ago

We received a notification from AWS about Node.js:

_We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Node.js 12 runtime.

We are ending support for Node.js 12 in AWS Lambda. This follows Node.js 12 End-Of-Life (EOL) reached on April 30, 2022 [1].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 14, 2022, Lambda will no longer apply security patches and other updates to the Node.js 12 runtime used by Lambda functions, and functions using Node.js 12 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 12 runtime. Starting December 14, 2022, you will no longer be able to update existing functions using the Node.js 12 runtime.

We recommend that you upgrade your existing Node.js 12 functions to Node.js 16 before November 14, 2022.

End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.

The following command shows how to use the AWS CLI [3] to list all functions in a specific region using Node.js 12. To find all such functions in your account, repeat this command for each region:

aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='nodejs12.x'].FunctionArn"

If you have any concerns or require further assistance, please contact AWS Support [4].

[1] https://nodejs.org/en/blog/release/v12.22.12/ [2] https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html [3] https://aws.amazon.com/cli/ [4] https://aws.amazon.com/support_

We were wondering if you were planning to upgrade the connector you created as a result of this notification.

Thanks, Marcia

ori229 commented 2 years ago

Dear Marcia, We believe the connector should work with Node.js 16 – you can upgrade, and please update here if it went well.

I did this small test: Check Node ver: C:...\exl-touchnet-connector>node Welcome to Node.js v16.13.0.

Cloned from Git, and then: C:...\exl-touchnet-connector>npm install … C:...\exl-touchnet-connector>npm start

exl-touchnet-connector@0.0.7 start node app/index.js

Opened my browser with http://localhost:3002/ and received "Touchnet connector"

ori229 commented 2 years ago

Today we upgraded our hosted connector, mentioned here: https://github.com/ExLibrisGroup/exl-touchnet-connector/#hosted-connector-experimental

msghens commented 1 year ago

I was experimenting using cloud formation.

It failed.

This is what I got:

LakshmiUCI commented 1 year ago

I was experimenting using cloud formation.

It failed.

This is what I got:

2023-03-17 14:23:16 UTC-0700 ExlTouchnetConnectorTest ROLLBACK_COMPLETE - 2023-03-17 14:23:15 UTC-0700 LambdaExecutionRole DELETE_COMPLETE - 2023-03-17 14:23:14 UTC-0700 pubPrivateVPC DELETE_COMPLETE - 2023-03-17 14:23:14 UTC-0700 internetGateway DELETE_COMPLETE - 2023-03-17 14:23:13 UTC-0700 Dependencies05f9b2d67b DELETE_SKIPPED - 2023-03-17 14:23:13 UTC-0700 LambdaExecutionRole DELETE_IN_PROGRESS - 2023-03-17 14:23:12 UTC-0700 pubPrivateVPC DELETE_IN_PROGRESS - 2023-03-17 14:23:12 UTC-0700 internetGateway DELETE_IN_PROGRESS - 2023-03-17 14:23:08 UTC-0700 ExlTouchnetConnectorTest ROLLBACK_IN_PROGRESS The following resource(s) failed to create: [LambdaExecutionRole, internetGateway, pubPrivateVPC, Dependencies05f9b2d67b]. Rollback requested by user. 2023-03-17 14:23:08 UTC-0700 pubPrivateVPC CREATE_FAILED Resource creation cancelled 2023-03-17 14:23:07 UTC-0700 internetGateway CREATE_FAILED Resource creation cancelled 2023-03-17 14:23:07 UTC-0700 LambdaExecutionRole CREATE_FAILED Resource creation cancelled 2023-03-17 14:23:07 UTC-0700 pubPrivateVPC CREATE_IN_PROGRESS Resource creation Initiated 2023-03-17 14:23:07 UTC-0700 Dependencies05f9b2d67b CREATE_FAILED Error occurred while GetObject. S3 Error Code: PermanentRedirect. S3 Error Message: The bucket is in this region: us-east-1. Please use this region to retry the request (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 86c0d6a3-4b55-4e82-8cdf-df3b1f721274; Proxy: null) 2023-03-17 14:23:06 UTC-0700 internetGateway CREATE_IN_PROGRESS Resource creation Initiated 2023-03-17 14:23:06 UTC-0700 LambdaExecutionRole CREATE_IN_PROGRESS Resource creation Initiated 2023-03-17 14:23:06 UTC-0700 Dependencies05f9b2d67b CREATE_IN_PROGRESS - 2023-03-17 14:23:05 UTC-0700 LambdaExecutionRole CREATE_IN_PROGRESS - 2023-03-17 14:23:05 UTC-0700 pubPrivateVPC CREATE_IN_PROGRESS - 2023-03-17 14:23:05 UTC-0700 internetGateway CREATE_IN_PROGRESS - 2023-03-17 14:23:00 UTC-0700 ExlTouchnetConnectorTest CREATE_IN_PROGRESS Transformation succeeded 2023-03-17 14:22:55 UTC-0700 ExlTouchnetConnectorTest CREATE_IN_PROGRESS User Initiated

Try creating the stack(cloud formation) in a different region(us-east-1) based the error message specified. When we implemented this we had to create it in different AWS region because of VPC limit for that region.

msghens commented 1 year ago

Thanks that did the trick. Used N. Virgina.

ExLibrisGroup / exl-touchnet-connector

Node.js #24