![]() ![]() Procedure to safely migrate your environment to the new platform version.įind and fix any application compatibility issues that you couldn't discover during the development phase.Įnsure that any customizations that your application makes using configuration files work correctly in the Verify that your application still works as expected, and make any necessary code fixes and changes. When you migrate across major platform versions or to platform versions with major component updates, there's a greater likelihood that yourĪpplication, or some aspects of it, might not function as expected on the new platform version, and might require changes.īefore performing the migration, update your local development machine to the newer runtime versions and other components of the platform you plan on It's also required when you're migrating off of a deprecated or retired platform branch. This is typically necessary when you want to take advantage of new runtime capabilities or the latest Elastic Beanstalkįunctionality. Use this method to update to a different platform branch-with a different runtime, web server, application server, or operating system, or to aĭifferent major platform version. Method 2 – Perform a Blue/Green deployment For details, see Managed platform updates. Update immediately if instances running your application on the new version fail health checks. Elastic Beanstalk applies managed updates with no downtime or reduction in capacity, and cancels the You can configure your environment to apply minor and patch version updatesĪutomatically during a configurable weekly maintenance window. To further simplify platform updates, Elastic Beanstalk can manage them for you. Versions are incompatible with previous Amazon Linux AMI platform versions.įor more help with choosing the best platform update method, expand the section for your environment's platform. ![]() Migrating a Linux application to Amazon Linux 2 requires a blue/green deployment, because Amazon Linux 2 platform ![]() Versions are incompatible with currently supported versions. Migrating from a legacy platform version requires a blue/green deployment, because these platform This is a good approach when you want to take advantage of new runtime capabilities or the latestĮlastic Beanstalk functionality, or when you want to move off of a deprecated or retired platform branch. System, or to a different major platform version. You're updating to a platform version in a different platform branch-with a different runtime, web server, application server, or operating Method 2 – Perform a Blue/Green deployment. This is the most common and routine platform update. System, and without a change in the major platform version. You're updating to the latest platform version within a platform branch-with the same runtime, web server, application server, and operating Method 1 – Update your environment's platform version. Depending on the platform version you'd like to update to,Įlastic Beanstalk recommends one of two methods for performing platform updates. You can use the Elastic Beanstalk console or the EB CLI to update your environment's platform version. Platform versions, see Elastic Beanstalk platforms glossary. New platform versions provide updates to existing software components and support for new features and configuration options. Information about migrating to a current and fully supported Amazon Linux 2 platform branch, see Migrating your Elastic Beanstalk Linux application to Amazon Linux 2.Įlastic Beanstalk regularly releases new platform versions to update all Linux-based and Windows Server-based platforms. To avoid availability impact, we advise that you upgrade your AL1 basedīeanstalk environments the latest Amazon Linux 2 platform release before June 28, 2023. Variations of Amazon Linux AMI (AL1) platforms may be Amazon Linux AMI (AL1) Platformsġ8,2022, Elastic Beanstalk set the status of all platform branches based on Amazon Linux AMI (AL1) to ![]() Update your affected Windows environments before June 28, 2023.įor details and best practices about updating your environment, read the information in this topic. To avoid availability impact, we advise that you V1.2 is used by Elastic Beanstalk Windows platforms on platform version 2.10.7 or later. These listed platforms versions run TLS v1.1 or earlier and will therefore be impacted. Windows Server 2008 - all platform versions this platform was retired on October 28, Windows Server 2012 - platform version 2.10.6 or prior versions Windows Server 2016 - platform version 2.10.6 or prior versions ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |