These are the differences for all platforms:ĭefault is nginx – The default proxy server on all Amazon Linux 2 platform versions is nginx. However, configuring the proxy server is slightlyĭifferent than it was on Amazon Linux AMI. Platforms enable proxy server configuration in a uniform way, as described in this section. The Tomcat, Node.js, PHP, and Python platform also support Apache HTTPD as an alternative. Versions use nginx as their default reverse proxy server. Platform Hooks section in Extending Elastic Beanstalk Linux platforms.Īmazon Linux 2 platform versions support the same reverse proxy servers as each platform supported in its Amazon Linux AMI platform versions. You should migrate any hooks to the new platform hooks. WithĪmazon Linux 2 platform versions, custom platform hooks don't work. These hooks weren't designed for managed platforms and weren't supported, but could work in useful ways in some cases. With previous Linux platform versions, you might have used custom platform ebextensions configuration files for any script that needs a reference to an AWS CloudFormationĪmazon Linux 2 platforms introduce a new way to extend your environment's platform by adding executable files to hook directories on theĮnvironment's instances. YAML file can be cumbersome and difficult to test. For example, writing command scripts inside a ![]() ebextensions configuration files, but they aren't as easy to work with. You can still use commands and container commands in We recommend using platform hooks to run custom code on your environment instances. ![]() Section in Extending Elastic Beanstalk Linux platforms. For details, expand the Reverse Proxy Configuration platform/nginx platform hooks directory. ebextensions/nginx directory should move to the Proxy configuration files provided in the. Some platform specific configuration options have moved from their platform specific namespaces to different, platform agnostic namespaces. Some software packages that you install using a configuration file might not be available on Amazon Linux 2, or their names might have changed. The following references may be helpful in planning your migration. To reference the specific steps of the blue/green deployment procedure, see Blue/Green deployments. For more information about the blue/green deployment best practice methods, see Blue/Green method. When your new environment is ready to go to production, you'll swap the CNAMEs of the two environments to redirect traffic to the newĮnvironment. Your existing production environment will remain active and unaffected, while you iterate through testing and making adjustments to the newĮnvironment. Following the best practices that are recommendedįor migration with a blue/green deployment procedure, you'll create a new environment that's based on an Amazon Linux 2 platform branch and deploy your applicationĬode to it. When you're ready to go to production, Elastic Beanstalk requires a blue/green deployment to perform the upgrade. Thoroughly in a development environment, and make any necessary adjustments. Therefore we recommend that you take your time, test your application Platform specific versions of runtime, build tools, and other dependencies. The Elastic Beanstalk service has also updated ![]() Although Amazon LinuxĪMI and Amazon Linux 2 share the same Linux kernel, they differ in their initialization system, libc versions, the compiler tool chain, andįor more information, see Amazon Linux 2 FAQs. Successfully deploys to the new platform version, it might behave or perform differently due to operating system and run time differences. Furthermore, even if your application code The AL2 based platform branches aren't guaranteed to be backward compatible with your existing application. ![]() Previous generation platform branchesīased on Amazon Linux AMI are now deprecated. If your Elastic Beanstalk application is based on an Amazon Linux AMI platform branch, use this page to learn how to migrate your application's environments to Amazon Linux 2.ĪWS Elastic Beanstalk uses Amazon Linux 2 as the operating system for Linux platforms. Elastic Beanstalk set the status of all platform branches based on Amazon Linux AMI (AL1) to retired.įor more information, see Amazon Linux AMI (AL1) platform retirement FAQ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |