Update Lambda runtime from Go 1.x (Deprecated) to custom runtime on Amazon Linux 2

[fabiozig]

Problem:

Amazon announced the end of support for Go 1.x runtime and the lambdas deployed with cdk-ecr-deployment running on go 1.x runtime will no longer receive support from December 31, 2023 and we will not longer be able to deploy new functions from January 30, 2024.

We are ending support for the Go 1.x runtime in AWS Lambda, in line with Amazon Linux AMI end of maintenance support on December 31, 2023. Lambda continues to support the Go programming language, using the provided.al2 runtime. Using the provided.al2 runtime offers several benefits over the go1.x runtime, including support for AWS Graviton2 processors and a streamlined implementation with a smaller deployment package and faster function invoke path. For more information, see our blog post. As described in the Lambda runtime support policy, end of support for language runtimes in Lambda happens in two stages. Starting December 31, 2023, Lambda will no longer apply security patches and other updates to the Go 1.x runtime used by Lambda functions, and functions using Go 1.x will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Go 1.x runtime. Starting January 30, 2024, you will no longer be able to update existing functions using the Go 1.x runtime. We recommend that you upgrade your existing Go 1.x functions to the provided.al2 runtime before December 31, 2023.

Reference:
https://aws.amazon.com/blogs/compute/migrating-aws-lambda-functions-from-the-go1-x-runtime-to-the-custom-runtime-on-amazon-linux-2/

Request:

Update the runtime to provided.al2 runtime as mentioned by AWS

[SamStephens]

@scanlonp I'm tagging you here based on cdklabs/cdk-docker-image-deployment#433. I've previously tried to get someone to look at this repository and that issue received no attention.

Users of this package are in a pretty unpleasant position. An AWS recommended solution appears to be now abandoned. I have projects depending on this that will no longer be deployable to new accounts as of next year, and no path forward I know of other than create my own replacement (as we know cdk-docker-image-deployment does not support Python currently).

I'd be willing to do the work to revive and release #323, but currently it seems like I'd be wasting my time because there's no owner here to merge the change.

Frankly, it appears AWS's custodianship of its open source eco-system appears to be failing; I urge you to raise this with your leadership. AWS needs to either commit more resource, or actually bite the bullet and either shut these packages down or find owners outside AWS for them. Currently these unsupported packages are a trap - you build a solution around them, and only then find that the level of support and care you expect from something with the AWS brand on it just isn't there.

[scanlonp]

@SamStephens I have no problem helping that PR get merged if you would like to finish up the work on it. However, this repository is not going to be one that I personally will commit to maintaining.

I think your larger point about the state of this & other repositories in our open source sphere has weight. It is something that we are concerned with, and we are doing work to strategize on. I will voice your message to the team.

[scanlonp]

@SamStephens Also I do not know if you have a presence on the cdk.dev slack channel, but feel free to message me there! I have some thoughts about this specific issue (user control of docker images in cdk projects) that we could discuss & maybe tailor some solutions to your use case. (More than happy to have discussions on Github, just wanted to offer since Slack it is a little more direct + immediate in terms of communication!)