What happens after the Availability end date of Retired Platform?

0

Hi,

Python 2.7 environments will be retired on March 1, 2020 according to AWS Elastic Beanstalk Platform Support Policy: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-support-policy.html which says For existing customers running an Elastic Beanstalk environment on a retired platform version beyond the 90 day period, Elastic Beanstalk may need to automatically remove the Elastic Beanstalk components and transfer ongoing management and support responsibility of the running application and associated AWS resources to the customer. and

AWS Elastic Beanstalk Platforms Glossary: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-glossary.html says
Retired platform versions aren't available for use in Elastic Beanstalk environments for either new or existing customers.

Could you make it clear what exactly will happen to existing running environments after the 90 days grace period?

  1. Will AWS terminate the environments or just disable creating new apps with these environments? I image clone feature of existing Python 2.7 environments will be disabled?
  2. Are we able to deploy a new version of app codes?
  3. Can we still use API/web console to make config changes to running environments?

Thanks.
PS. When will Amazon Linux 2 be available on Beanstalk?

asked 5 years ago881 views
2 Answers
0

Post closed. They don't care.

answered 4 years ago
0

Hello!

Please let me answer your questions and provide some information about retired platforms.

1 - Will AWS terminate the environments or just disable creating new apps with these environments? I image clone feature of existing Python 2.7 environments will be disabled? R: AWS will 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 hot-fixes for retired platform branches. Clone and Rebuild those environments still possible for the Customers that already have this versions, but the creation of new environments will be updated to the current supported versions.

2 - Are we able to deploy a new version of app codes? R: Yes, the environment still working, but keep in mind that retired versions mean that the supplier marking their component EOL, it means that the environment will not receive support neither security updates.

3 - Can we still use API/web console to make config changes to running environments? R: Yes, the environment will still running, but keep in mind that 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.

Let me point here that environment with retired platforms cannot be updated, it means that to update your application running environment, you must launch a new environment within a supported version. You can create a brand new one and swap the CNAME between then to verify if your application is performing as expected.

Another workaround is to migrate your application to a docker platform, where you will be able to use any version of Python for run time. But please keep in mind that if the version is retired by the supported it will represent a high risk for your security and for your performance.

Kindly refer to this documentation for more information about retired platforms: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-support-policy.html#platforms-support-policy.retired-platforms

AWS
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions