Posted On: May 22, 2020
You can now select the Traffic Splitting deployment policy when deploying application code using Amazon Elastic Beanstalk. This is in addition to the four existing deployment policies that Elastic Beanstalk currently supports (i.e. All at once, Rolling, Rolling with additional batch, and Immutable).
You can now use the Traffic Splitting deployment policy to update an application running in an Elastic Beanstalk Webserver environment that uses Application Load Balancer. This deployment policy is well suited for updates in production environments where you want to reduce the risk of application failure when committing changes to your application code. Traffic Splitting deployment allows you to monitor the health of your new application version under a percentage of production traffic specified by you before completing the deployment. In case of deployment failures, Traffic Splitting will minimize the application downtime through an automatic rollback mechanism.
When using Traffic Splitting deployment, you can specify the percent of production traffic and the amount of time to monitor a new application version before completing the deployment. Once the deployment starts, you can monitor the health of your new application version from Elastic Beanstalk events in real time. You can also obtain the Traffic Splitting deployment logs from Elastic Beanstalk events. To get started, enable Traffic Splitting deployment policy using the Elastic Beanstalk console, Elastic Beanstalk CLI, or through the Elastic Beanstalk API. Learn more about Traffic Splitting deployment policy in our documentation.