Support for runtime "provided.al2023"

[dkreuer]

AWS Lambda provides an updated OS-only Runtime "provided.al2023" as alternative to "provided.al2". Bref currently only supports "provided.al2".

Is there any plan to either migrate to "provided.al2023" or support both runtimes?

Additional links:

• https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
• https://aws.amazon.com/de/blogs/compute/introducing-the-amazon-linux-2023-runtime-for-aws-lambda/

[deleugpn]

brefphp/aws-lambda-layers#122

[sander-bol]

This is issue is getting more urgent, with AWS sending out deprecation notices for AL2 now.

This is a copy of the email we received last week:

We are contacting you as we have identified that your AWS Account currently has one or more AWS Lambda functions using the OS-only runtime for Amazon Linux 2 (provided.al2).

We are ending support for the OS-only runtime for Amazon Linux 2 (provided.al2) in Lambda on July 31, 2026. This follows Amazon Linux 2 End-Of-Life (EOL) on June 30, 2026 [1]. 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.

This notification does not apply to other Amazon Linux 2-based runtimes: Java 8, Java 11, Java 17, Python 3.10, and Python 3.11. See the Lambda runtime documentation [6] for the current deprecation schedule for each of these runtimes.

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in several stages.

• Starting on July 31, 2026, Lambda will no longer apply security patches and other updates to the OS-only runtime for Amazon Linux 2 (provided.al2), and functions using this runtime will no longer be eligible for technical support. Also, the OS-only runtime for Amazon Linux 2 (provided.al2) will no longer be available in the AWS Console, although you can still create and update functions using this runtime by using AWS CloudFormation, the AWS CLI, AWS Serverless Application Model (SAM), or other tools.

• Starting August 31, 2026, you will no longer be able to create new Lambda functions using the OS-only runtime for Amazon Linux 2 (provided.al2).

• Starting September 30, 2026, you will no longer be able to update existing functions using the OS-only runtime for Amazon Linux 2 (provided.al2).

We recommend that you upgrade your existing functions that use the OS-only runtime for Amazon Linux 2 (provided.al2) to the OS-only runtime for Amazon Linux 2023 (provided.al2023) before July 31, 2026.

Your impacted Lambda functions using the OS-only Runtime (Amazon Linux 2) runtime are listed on the 'Affected resources' tab of your AWS Health Dashboard.

This notification is generated for functions using the OS-only runtime for Amazon Linux 2 (provided.al2) for the $LATEST function version. The following command shows how to use the AWS CLI [3] to list all functions in a specific region that use this runtime, including published function versions. To find all such functions in your account, repeat the following command for each region:

aws lambda list-functions --region us-east-1 --output text --query "Functions[?Runtime=='provided.al2'].FunctionArn"

Starting 180 days before deprecation, you can also use Trusted Advisor to identify functions using the OS-only runtime for Amazon Linux 2 (provided.al2) [4].

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

Runtime deprecation may occasionally be deferred for operational reasons. You can check active notifications in AWS Health and the Lambda runtime documentation [6] for the current schedule.

[mnapoli]

Please read #1953 and try the beta versions.

[coopan]

Hi there,

Is there any timeline for the stable release? I have searched here/docs etc, but I can't find a roadmap to help communicate the plan for addressing this hard deadline internally. I imagine 3.0 stable will be before July 31, else Bref pro and enterprise will become compliance invalid, and outright dead products by September 30.

We can use the Beta for planning and validating our upgrade on staging. But it would be really good to have some idea on current stable release plan so we can plan things ourselves. And at the moment I haven't actually seen anything suggesting urgency or concern around this immutable AWS deadline.

[deleugpn]

And at the moment I haven't actually seen anything suggesting urgency or concern around this immutable AWS deadline.

That just means you're not paying attention and you're also not sponsoring the project you seem to be heavily dependent on. I work for a company that sponsor Bref and we have received communication in response to AWS announcements.

Sponsoring the project is a great way to have your concerns addressed swiftly.

[coopan]

No we're paying attention to it just fine thanks, so let's leave that there. It's not helpful. The point made is there is a critical piece of information that can't be paid attention to if it's not available.

As for sponsoring:

1. I wasn't aware that was an avenue
2. Gatekeeping release dates of an open source project behind sponsorship would be a very unusual model. And unnecessary when it's just a release roadmap. Are you suggesting that release roadmap is privileged information?

And ultimately, none of this has answered a pretty simple question.

[coopan]

For others finding this issue:

This bref/layers issue five days ago suggests Bref 3 stable is coming in the next few weeks.

The main Bref V3 PR linked in another dupe question mentions "The stable release is coming end of February/Early March."

This duplicate bref issue mentions a 2.x update, but I can't see confirmation or timeline for that. So I may be misinterpreting the comment.

[mnapoli]

@coopan there's no gatekeeping being sponsorship here. I've been trying to post updates in Slack, in GitHub issues (and yes people sponsoring the project get more attention from me, that's literally the point) and if that's not enough I'm sorry, but at some point you gotta chill please. You just had to click the link I posted. That was one click.

You're using an open source project for free, keep that in mind in your future interactions. Let's keep things constructive :)

[coopan]

@mnapoli the link was the confusion (along with other competing conversations around the issue register). And I think the fact that you were dealing with multiple duplicate issues raised on critical timeline illustrates my chill levels are completely fine.

It's released now so we put this one to bed. But I still believe that a lot of this confusion from multiple people could have been avoided with more centralised comms. That one click was actually actually became quite a few for you for a reason.

Please treat this as constructive feedback. And thank you for your hard work for the community.