AWS Lambda is an event-driven, serverless computing platform provided by Amazon as a part of Amazon Web Services. It is designed to enable developers to run code without provisioning or managing servers. It executes code in response to events and automatically manages the computing resources required by that code.
| Release | Released | Standard Support | Deprecated Support |
|---|---|---|---|
| Node.js 22 | 3 weeks ago (22 Nov 2024) |
Yes | Yes |
| Python 3.13 | 4 weeks ago (14 Nov 2024) |
Yes | Yes |
| Ruby 3.3 | 8 months ago (04 Apr 2024) |
Yes | Yes |
| .NET 8 | 9 months ago (22 Feb 2024) |
Yes | Yes |
| Python 3.12 | 12 months ago (14 Dec 2023) |
Yes | Yes |
| Java 21 | 1 year ago (17 Nov 2023) |
Yes | Yes |
| Node.js 20 | 1 year ago (15 Nov 2023) |
Yes | Yes |
| Custom Runtime (AL2023) | 1 year ago (10 Nov 2023) |
Yes | Yes |
| Python 3.11 | 1 year and 4 months ago (27 Jul 2023) |
Yes | Yes |
| Ruby 3.2 | 1 year and 6 months ago (07 Jun 2023) |
Yes | Yes |
| Java 17 | 1 year and 7 months ago (27 Apr 2023) |
Yes | Yes |
| Python 3.10 | 1 year and 8 months ago (18 Apr 2023) |
Yes | Yes |
| Node.js 18 | 2 years ago (18 Nov 2022) |
Ends
in 7 months (31 Jul 2025)
|
Ends
in 9 months (01 Oct 2025)
|
| .NET 7 (container-only) | 2 years ago (15 Nov 2022) |
Ended
7 months ago (14 May 2024)
|
No |
| Node.js 16 | 2 years and 7 months ago (12 May 2022) |
Ended
6 months ago (12 Jun 2024)
|
Ends
in 3 months and 2 weeks (31 Mar 2025)
|
| .NET 6 | 2 years and 9 months ago (24 Feb 2022) |
Ends
in 1 week (20 Dec 2024)
|
Ends
in 3 months and 2 weeks (31 Mar 2025)
|
| Python 3.9 | 3 years ago (16 Aug 2021) |
Yes | Yes |
| Node.js 14 | 3 years and 10 months ago (03 Feb 2021) |
Ended
1 year ago (04 Dec 2023)
|
Ends
in 2 months and 2 weeks (28 Feb 2025)
|
| .NET 5 (container-only) | 4 years ago (02 Dec 2020) |
Ended
2 years and 7 months ago (10 May 2022)
|
No |
| Java 8 (AL2) | 4 years ago (12 Aug 2020) |
Yes | Yes |
| Custom Runtime (AL2) | 4 years ago (12 Aug 2020) |
Yes | Yes |
| .NET Core 3.1 | 4 years and 8 months ago (31 Mar 2020) |
Ended
1 year and 8 months ago (03 Apr 2023)
|
Ended
1 year and 7 months ago (03 May 2023)
|
| Ruby 2.7 | 4 years and 9 months ago (19 Feb 2020) |
Ended
1 year ago (07 Dec 2023)
|
Ends
in 2 months and 2 weeks (28 Feb 2025)
|
| Node.js 12 | 5 years ago (18 Nov 2019) |
Ended
1 year and 8 months ago (31 Mar 2023)
|
Ended
1 year and 7 months ago (30 Apr 2023)
|
| Python 3.8 | 5 years ago (18 Nov 2019) |
Ended
2 months ago (14 Oct 2024)
|
Ends
in 3 months and 2 weeks (31 Mar 2025)
|
| Java 11 | 5 years ago (18 Nov 2019) |
Yes | Yes |
| Node.js 10 | 5 years and 7 months ago (15 May 2019) |
Ended
3 years and 4 months ago (30 Jul 2021)
|
Ended
2 years and 10 months ago (14 Feb 2022)
|
| Ruby 2.5 | 6 years ago (29 Nov 2018) |
Ended
3 years and 4 months ago (30 Jul 2021)
|
Ended
2 years and 8 months ago (31 Mar 2022)
|
| Custom Runtime (AL1) | 6 years ago (29 Nov 2018) |
Ended
11 months ago (08 Jan 2024)
|
Ends
in 2 months and 2 weeks (28 Feb 2025)
|
| Python 3.7 | 6 years ago (19 Nov 2018) |
Ended
1 year ago (04 Dec 2023)
|
Ends
in 2 months and 2 weeks (28 Feb 2025)
|
| .NET Core 2.1 | 6 years ago (09 Jul 2018) |
Ended
2 years and 11 months ago (05 Jan 2022)
|
Ended
2 years and 8 months ago (13 Apr 2022)
|
| Node.js 8.10 | 6 years and 8 months ago (02 Apr 2018) |
Ended
4 years and 9 months ago (06 Mar 2020)
|
Ended
4 years and 9 months ago (06 Mar 2020)
|
| .NET Core 2.0 | 6 years and 11 months ago (15 Jan 2018) |
Ended
5 years ago (30 May 2019)
|
Ended
5 years ago (30 May 2019)
|
| Go 1.x | 6 years and 11 months ago (15 Jan 2018) |
Ended
11 months ago (08 Jan 2024)
|
Ends
in 2 months and 2 weeks (28 Feb 2025)
|
| Node.js 4.3 edge | 7 years ago (17 Jul 2017) |
Ended
4 years and 9 months ago (05 Mar 2020)
|
Ended
4 years and 7 months ago (30 Apr 2020)
|
| Python 3.6 | 7 years ago (18 Apr 2017) |
Ended
2 years and 4 months ago (18 Jul 2022)
|
Ended
2 years and 3 months ago (29 Aug 2022)
|
| Node.js 6.10 | 7 years ago (22 Mar 2017) |
Ended
5 years ago (12 Aug 2019)
|
No |
| .NET Core 1.0 | 8 years ago (01 Dec 2016) |
Ended
5 years ago (27 Jun 2019)
|
Ended
5 years ago (30 Jul 2019)
|
| Node.js 4.3 | 8 years ago (07 Apr 2016) |
Ended
4 years and 9 months ago (05 Mar 2020)
|
Ended
4 years and 9 months ago (05 Mar 2020)
|
| Python 2.7 | 9 years ago (08 Oct 2015) |
Ended
3 years and 5 months ago (15 Jul 2021)
|
Ended
2 years and 6 months ago (30 May 2022)
|
| Java 8 (AL1) | 9 years ago (15 Jun 2015) |
Ended
11 months ago (08 Jan 2024)
|
Ends
in 2 months and 2 weeks (28 Feb 2025)
|
| Node.js 0.10 | 10 years ago (13 Nov 2014) |
No |
Ended
8 years ago (31 Oct 2016)
|
Supported runtimes
AWS Lambda supports the following runtimes:
Standard Support
Amazon provides security patches to the underlying runtimes, along with technical support.
Runtime updates are, most of the time, backward compatible with existing functions. But, in some rare cases, a runtime update can negatively impact an existing function. An example of such case is a lambda that make use of an insecure behavior fixed by a security patch.
There are three modes of runtime updates:
- Auto (default): functions are automatically updated to the most recent runtime version.
- Function update: runtime update is applied at function update.
- Manual: runtime version is set in the function configuration.
Responsibility for applying runtime updates varies according to chosen runtime update mode.
Trusted Advisor includes a check that provides 120 days’ notice of upcoming Lambda runtime end of support, and Lambda notifies you by email if you have functions using a runtime that is scheduled for end of support in the next 60 days.
Deprecated Support
Deprecation (end of support) for a runtime occurs in multiple steps:
- Deprecation: Security patches or other updates are no longer applied, and new functions that use the runtime cannot be created. Functions that use a deprecated runtime are also no longer eligible for technical support. This is documented in the table above as Standard Support.
- Block function creation: Starting from at least 30 days after the deprecation, new functions using a deprecated runtime cannot be created anymore.
- Block function update: Starting from at least 60 days after the deprecation, existing functions that use a deprecated runtime cannot be updated anymore. This is documented in the table above as Deprecated Support.
Invocations of functions that use deprecated runtime is never blocked.
More information is available on the AWS Lambda website.
You can submit an improvement to this page
on GitHub
.
This page has a corresponding Talk Page.
A JSON version of this page is available at /api/aws-lambda.json. See the API Documentation for more information. You can subscribe to the iCalendar feed at /calendar/aws-lambda.ics.