Elastic Beanstalk

Question 1

EB

Answer 1

• use all aws components together, automatically handles capacity provisioning, load balancing, scaling, etc
  
  • allows the dev to focus on actually coding!
• can easily clone environments
• uses CloudFormation under the hood

Question 2

EB components

Answer 2

• application - collection of beanstalk components
• app version - iteration of you app code
• environment - collection of aws resources running an app version (dev, test, prod)
  
  • tiers
    
    • web server tier
    • worker environment tier - sqs queue
    • can combing web server and worker env

Question 3

EB Deployment modes

Answer 3

• single instance - great for dev
  
  • DNS name → elastic IP
• high availability w/ load balancer - great for prod
  
  • DNS name → ELB DNS name

Question 4

All at once Deployment

Answer 4

(deploy all in one go) - fastest but instances aren’t available to serve traffic for a bit

Question 5

Rolling Deployment

Answer 5

update a few instances at a time (bucket) and then move onto the next bucket once first bucket is healthy

Question 6

Rolling with additional batches deployment

Answer 6

rolling but spins up new instances to move the batch (so that the old app is still available)

Question 7

Immutable

Answer 7

spins up new instances in a new ASG, deploys version to these instances, then swaps all instances when everything is healthy. Original instances in old asg remain untouched until deployment is complete.

Question 8

blue/green deployment

Answer 8

swap CNAME (environment URLs)

Question 9

Canary Deployment

Answer 9

traffic splitting between ASGs

Question 10

Deployment method overview

Answer 10

Question 11

EB extension

Answer 11

• parameters set in UI can be configured in code using files
• .ebextensions directory in root of source code
  
  • contains .config extensions (logging.config)
  • anything under ebextensions gets deleted with the environment

Question 12

EB load balancer migration

Answer 12

• after env creation, you cannot change the ELB type (only configuration)
• steps
  
  • create new env with same configuration except LB
  • deploy app to new env
  • perform CNAME swap or Route 53 update

Question 13

EB w/ Docker

Answer 13

• can run an app as a single docker container
  
  • beanstalk in single docker container does NOT use ECS
• multi docker containers per ec2 instance
  
  • requires a dockerrun.aws.json at root of source code - used to generate task defintion in ECS
  • image must be pre-built and stored in a repo somewhere