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.

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 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.

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.