08 - Updating ElasticBeanstalk Flashcards Preview

AWS-CDA-2019-08 - Other Services > 08 - Updating ElasticBeanstalk > Flashcards

Flashcards in 08 - Updating ElasticBeanstalk Deck (5):
1

Updating ElasticBeanstalk - Overview

Updating ElasticBeanstalk

  • Remember the four different deployment approaches:

 

All At Once

  • Service interruption while you update the entire environment at once
  • To roll back, perform a further All At Once upgrade

Rolling

  • Reduced capacity during deployment
  • To roll back, perform a further Rolling Update

Rolling with Additional Batch

  • Maintains full capacity
  • To roll back, perform a further Rolling Update

Immutable

  • Preferred option for mission critical production systems
  • Maintains full capacity
  • To roll back, just delete the new instances and autoscaling group

2

All At Once

At Once Updates - Outage

  • Deploys the new version to all instances simultaneously 
  • All of your instances are out of service while the deployment takes place
  • You will experience an outage while the deployment is taking place - not ideal for mission critical production systems
  • If the update fails, you need to roll back the changes by re-deploying the original version to all your instances

3

Rolling

Rolling Deployment Updates - Reduced Capacity, Rolling Update to Rollback

  • Deploys the new version in batches
  • Each batch of instances is taken out of service while the deployment takes place
  • Your environment capacity will be reduced by the number of instances in a batch while the deployment takes place
  • Not ideal for performance sensitive systems
  • If the update fails, you need to perform an additional rolling update to roll back the changes

4

Rolling with Additional Batch

Rolling with Additional Batch Deployment Updates - Full Capacity, Rolling Update to Rollback

  • Launches an additional batch of instances
  • Deploys the new version in batches
  • Maintains full capacity during the deployment process
  • If the update fails, you need to perform an additional rolling update to roll back the changes

5

Immutable

Immutable Deployment Updates - Full Capacity, rollback terminates new autoscaling group

  • Deploys the new version to a fresh group of instances in their own new autoscaling group
  • When the new instances pass their health checks, they are moved to your autoscaling group, and finally the old instances are terminated
  • Maintains full capacity during the deployment process
  • The impact of a failed update is far less, and the rollback process requires only terminating the new autoscaling group
  • Preferred option for mission critical production systems