I have a couple notes for node.js on AWS Lambda. If you're at all security conscious you'll want to regularly bump the runtime version and update your packages.

I have a couple notes for node.js on AWS Lambda. If you're at all security conscious you'll want to regularly bump the runtime version and update your packages.json. Some automation with GitHub actions or similar should be able to do that. Probably add some basic testing to make sure things still work before you deploy. I haven't automated the ones I manage, and I've updated them maybe 1-2 times a year for security reasons. As an example, node 12 was released in 2019 [1] and will begin deprecation phases in another month [2]. So it looks like a 4 year support cycle, although old runtime versions will still run. If you're using any of the AWS security scanning tools, these will flag any vulnerable dependencies and then you'd update them. Those seem fairly common in the node ecosystem, so other languages may see lower toil. [1] https://nodejs.org/en/blog/release/v12.0.0/ https://nodejs.org/en/blog/release/v12.0.0/ [2] https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes...