Important: Bug reports submitted here should relate specifically to the open source sample amazon-q-slack-gateway project. Do not submit bugs related to the Amazon Q service itself.
If your issue relates to Amazon Q setup, user provisioning, document ingestion, accuracy, or other aspects of the service, then first check the Amazon Q documentation, and then reproduce the problem using the Amazon Q console web experience before engaging AWS support directly. Thank you.
Describe the bug
This solution provisions Slack related Lambda Functions using Node.js v16. This version of Node.js has been end-of-life since September 2023.
To Reproduce
Steps to reproduce the behavior:
Deploy the solution to an AWS account.
Navigate to each of the Lambda Functions that were provisioned.
Verify each Lambda Function is using v16 of Node.js.
Expected behavior
I expect the solution to have the latest Node.js runtime available which at this time is Node.js v20.
Screenshots
Additional context
I am running cdk-nag against this solution and noticed it has several findings. One of which is the Lambda runtime. While I tend to disagree that runtimes should be on "latest", we should try to at least try to be on a supported version.
Important: Bug reports submitted here should relate specifically to the open source sample amazon-q-slack-gateway project. Do not submit bugs related to the Amazon Q service itself.
If your issue relates to Amazon Q setup, user provisioning, document ingestion, accuracy, or other aspects of the service, then first check the Amazon Q documentation, and then reproduce the problem using the Amazon Q console web experience before engaging AWS support directly. Thank you.
Describe the bug This solution provisions Slack related Lambda Functions using Node.js v16. This version of Node.js has been end-of-life since September 2023.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect the solution to have the latest Node.js runtime available which at this time is Node.js v20.
Screenshots
Additional context I am running cdk-nag against this solution and noticed it has several findings. One of which is the Lambda runtime. While I tend to disagree that runtimes should be on "latest", we should try to at least try to be on a supported version.