Elastic Beanstalk platform support policy - Amazon Elastic Beanstalk
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Elastic Beanstalk platform support policy

Amazon Elastic Beanstalk provides a variety of platforms for running applications on Amazon. Elastic Beanstalk supports platform branches that still receive ongoing minor and patch updates from their suppliers (owners or community). For a complete definition of related terms, see Elastic Beanstalk platforms glossary.

Retired platform branches

When a component (operating system [OS], runtime, application server, or web server) of a supported platform branch is marked End of Life (EOL) by its supplier, Elastic Beanstalk marks the platform branch as retired. When a platform branch is marked as retired, Elastic Beanstalk no longer makes it available to new Elastic Beanstalk customers for deployments to new environments. There is a 90 day grace period from the published retirement date for existing customers with active environments that are running on retired platform branches.

Note

The retired platform branch will not be available in the Create environment wizard. However, it will be available through the Amazon CLI, EB CLI and EB API for customers that have existing environments based on the retired platform branch. Also, existing customers can use the Clone environment and Rebuild environment consoles.

Beyond the 90 day grace period

Existing customers running an Elastic Beanstalk environment on a retired platform branch beyond 90 days from the published retirement date should be aware of the risks of doing so. We would never remove access or delete the environment's resources. However, such environments can end up in an unpredictable situation, because Elastic Beanstalk isn't able to provide security updates, technical support, or hotfixes for retired platform branches due to the supplier marking their component EOL.

For example, a detrimental and critical security vulnerability may surface in an environment running on a retired platform branch. Or an EB API action may stop working for the environment if it becomes incompatible with the Elastic Beanstalk service over time. The opportunity for these types of risks increases the longer an environment on a retired platform branch remains active. To continue to benefit from important security, performance, and functionality enhancements offered by component suppliers in more recent releases, we strongly encourage you to update all your Elastic Beanstalk environments to a supported platform version.

If a circumstance like the ones just described should arise for an application that you must keep running and that you're not able to update to a supported Elastic Beanstalk platform, you'll need to consider and employ other alternatives. Workarounds include encapsulating the application into a Docker image to run it as a Docker container. This would allow a customer to use any of our Docker solutions, such as our Elastic Beanstalk AL2023/AL2 Docker platforms, or other Docker based services such as Amazon ECS, Amazon EKS, or Amazon App Runner. Non-Docker alternatives include our Amazon CodeDeploy service, which allows complete customization of the runtimes you desire.

Retiring platform branch schedule

The following tables list existing platform components that are either marked as retired or have retirement dates scheduled. The tables provide the availability end date for Elastic Beanstalk platform branches that contain these components.

For a list of related Elastic Beanstalk retiring platform branches, see platform versions scheduled for retirement in the Amazon Elastic Beanstalk Platforms guide.

Amazon Linux platforms

Amazon Linux 2 (AL2) - Runtime versions and platform branches

Runtime version or platform branch

Platform retirement date

Python 3.7 AL2

September 30, 2024

Node.js 14 AL2

September 30, 2024

Node.js 16 AL2

September 30, 2024

Ruby 2.7 AL2

September 30, 2024

Ruby 3.0 AL2

September 30, 2024

Corretto 8 with Tomcat 8.5 AL2

September 30, 2024

Corretto 11 with Tomcat 8.5 AL2

September 30, 2024

PHP 8.0 AL2

September 30, 2024

Retired platform branch history

The following tables list platform components that were marked as retired in the past. The tables provide the date on which Elastic Beanstalk retired platform branches that contained these components.

Note

For more information about the retirement of the Windows 2012 R2 platform branches, see Windows Server 2012 R2 platform branches retired in the Amazon Elastic Beanstalk Release Notes.

On July 18,2022, Elastic Beanstalk set the status of all platform branches based on Amazon Linux AMI (AL1) to retired. For more information, see Platform retirement FAQ.

Operating System (OS) versions

OS version

Platform retirement date

Windows Server 2012 R2 running IIS 8.5

December 4, 2023

Windows Server Core 2012 R2 running IIS 8.5

December 4, 2023

Amazon Linux AMI (AL1)

July 18, 2022

Windows Server 2012 R1

June 22, 2022

Windows Server 2008 R2

October 28, 2019

Application server versions

Application server version

Availability end date

Tomcat 7

June 29, 2022 for Amazon Linux 2 (AL2) platforms

July 18, 2022 for Amazon Linux AMI (AL1) platforms

Tomcat 6

October 31, 2020

Tomcat 8

October 31, 2020

Web server versions

Web server version

Availability end date

IIS 8 running on 64bit Windows Server

June 22, 2022

Apache HTTP Server 2.2

October 31, 2020

Nginx 1.12.2

October 31, 2020

Amazon Linux 2 (AL2) - Runtime versions and platform branches

Runtime version or platform branch

Platform retirement date

Corretto 11 with Tomcat 7 AL2

June 29, 2022

Corretto 8 with Tomcat 7 AL2

June 29, 2022

Node.js 12 AL2

December 23, 2022

Node.js 10 AL2

June 29, 2022

PHP 7.4 AL2

June 9, 2023

PHP 7.3 AL2

June 29, 2022

PHP 7.2 AL2

June 29, 2022

Ruby 2.6 AL2

December 23, 2022

Ruby 2.5 AL2

June 29, 2022

Amazon Linux AMI (AL1) - Runtime versions and platform branches

Runtime version or platform branch

Availability end date

Single Container Docker

July 18, 2022

Multicontainer Docker

July 18, 2022

Preconfigured Docker - GlassFish 5.0 with Java 8

July 18, 2022

Go 1

July 18, 2022

Java 8

July 18, 2022

Java 7

July 18, 2022

Java 8 with Tomcat 8.5

July 18, 2022

Java 7 with Tomcat 7

July 18, 2022

Node.js

July 18, 2022

PHP 7.2 - 7.3

July 18, 2022

Python 3.6

July 18, 2022

Ruby 2,4, 2.5, 2.6 with Passenger

July 18, 2022

Ruby 2.4, 2.5, 2.6 with Puma

July 18, 2022

Go 1.3–1.10

October 31, 2020

Java 6

October 31, 2020

Node.js 4.x–8.x

October 31, 2020

PHP 5.4–5.6

October 31, 2020

PHP 7.0–7.1

October 31, 2020

Python 2.6, 2.7, 3.4

October 31, 2020

Ruby 1.9.3

October 31, 2020

Ruby 2.0–2.3

October 31, 2020

Windows Server - Platform branches and Platform versions

Platform branch or platform version

Retirement date

IIS 8.5 running on 64bit Windows Server (& Core) 2012 R2 version 0.1.0

June 29, 2022

IIS 8.5 running on 64bit Windows Server (& Core) 2012 R2 version 1.2.0

June 29, 2022

IIS 10.0 running on 64bit Windows Server 2016 (& Core) version 1.2.0

June 29, 2022

IIS 8 running on 64bit Windows Server 2012 R1 Platform Branch

June 22, 2022

IIS 8 running on 64bit Windows Server 2012 R1 version 0.1.0

June 22, 2022

IIS 8 running on 64bit Windows Server 2012 R1 version 1.2.0

June 22, 2022