Quarkus native on AWS Lambda uses deprecated Lambda runtime

[bkzoller]

Description

I have a Quarkus project which uses quarkus-amazon-lambda-rest compiled to a native image. The Lambda is deployed to AWS provided Lambda runtime.

However, this Lambda runtime has been deprecated since January 2024. Code can no longer be updated to that runtime starting November 2025. Deprecated Lambda runtimes

I checked current documentation and created a new Quarkus 3.22 project on https://code.quarkus.io/ . All documentation references I could find and the compiled sample project use the deprecated provided runtime for native images.

The other option I found is to use Dockerfile to create a container image which is suitable for Lambda, and changing the Lambda runtime from provided over to a container image. However, then it wouldn't even use the AWS Lambda runtime images which they maintain. Plus the container image will be much larger than the binary zip file, which would likely affect Lambda cold start time.

1. What would be required to target provided.al2 or provided.al2023 in a Quarkus native project deployed to AWS Lambda?
2. What's the recommendation going forward (AWS Lambda runtime or custom container image) since the default Lambda runtime in Quarkus native will soon not be viable?

https://quarkusio.zulipchat.com/#narrow/channel/187030-users/topic/AWS.20Lambda.20runtime.20with.20Quarkus.20native.20image/with/520079623

Implementation ideas

No response

[quarkus-bot]

You added a link to a Zulip discussion, please make sure the description of the issue is comprehensive and doesn't require accessing Zulip

_{This message is automatically generated by a bot.}

[quarkus-bot]

/cc @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda)