Time to Bail · Boarding pass
Act. You can stay.
Java17, java11 and java8.al2 on Lambda are deprecated June 30, 2027. Updates are blocked from August 31, 2027.[1]
Act means: change a setting or plan before the date. You can stay.
AWS Lambda Java runtimes on Amazon Linux 2 deprecated June 30, 2027
AWS deprecates the Lambda runtimes java17, java11 and java8.al2 on June 30, 2027. They run on Amazon Linux 2. Creating functions is blocked from July 29, 2027, and updating them from August 31, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
List functions with the runtime java17, java11 or java8.al2 in each region. The Lambda console can filter by runtime.
To keep your Java version, use java17.al2023, java11.al2023 or java8.al2023. Or move to java21 or java25.
Test each function. After August 31, 2027 you cannot update functions on these runtimes.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| Deprecation date | June 30, 2027[1] |
|---|---|
| Runtimes | java17, java11 and java8.al2 (Java 17, 11 and 8 on Amazon Linux 2)[1] |
| Creating new functions blocked | July 29, 2027[1] |
| Updating functions blocked | August 31, 2027[1] |
| Amazon Linux 2 | End of life June 30, 2026; AWS still sends critical and selected important Amazon Linux 2 fixes for these runtimes until their deprecation date[1] |
| Help to upgrade | AWS Transform custom can help you upgrade to Java 21 or Java 25[1] |
| After deprecation | AWS may stop security patches and technical support; you can still invoke your functions[1] |
| In the Lambda console | From the deprecation date you cannot create or update these functions there; the AWS CLI, AWS SAM and CloudFormation still work until the blocks[1] |
| Once updates are blocked | You cannot go back to the deprecated runtime[1] |
| How AWS tells you | Email and Health Dashboard notices at least 180 days before; Trusted Advisor lists the functions[1] |
| Can the dates change? | Yes. AWS says the dates are for planning and subject to change[1] |
| How to list them | aws lambda list-functions --function-version ALL --region us-east-1 --query "Functions[?Runtime=='java17'].FunctionArn" (repeat for java11 and java8.al2, once per region)[2] |
| Java runtimes on the newer Amazon Linux | Amazon Linux 2023: java8.al2023, java11.al2023, java17.al2023, java21 and java25 until June 30, 2029[1] |
| Functions on these runtimes | May get no security patches after June 30, 2027; no updates from August 31, 2027[1] |
In the Lambda console you can no longer create or update functions on java17, java11 or java8.al2. The AWS CLI, AWS SAM and CloudFormation still work until the blocks. Your functions keep running, but AWS may stop security patches.
aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='java17'].FunctionArn". Repeat for java11 and java8.al2, in each region.java17.al2023 (or java11.al2023, java8.al2023, java21, java25). Test it before you ship.Source: [1] Lambda runtimes (Amazon Web Services) · [2] Retrieve data about Lambda Event Functions that use a deprecated runtime (Amazon Web Services)
Check it yourself. Every fact above links here.
Time to bail on Lambda functions on java17, java11 or java8.al2? Act. You can stay. Java17, java11 and java8.al2 on Lambda are deprecated June 30, 2027. Updates are blocked from August 31, 2027.
On our scale this is Act: change a setting or plan before the date. You can stay.
AWS deprecates the Lambda runtimes java17, java11 and java8.al2 on June 30, 2027. They run on Amazon Linux 2. Creating functions is blocked from July 29, 2027, and updating them from August 31, 2027.
Here are the facts we checked:
You can stay on AWS Lambda. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Amazon Web Services is the main source for this page. AWS Lambda has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Functions on these runtimes: May get no security patches after June 30, 2027; no updates from August 31, 2027.
The date to remember is June 30, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on Lambda functions on java17, java11 or java8.al2 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.