Guest User

Untitled

a guest
Jul 17th, 2018
85
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.84 KB | None | 0 0
  1. START
  2.  
  3. Create a Base AMI and harden it if you have too.
  4.  
  5. IF DOCKER:
  6. Create base Container with libraries and dependencies and store it in your container hub (you don't want to recreate the whole container every time)
  7. Create an as-light-as possible Dockerfile (used a base container)
  8. Copy code on build into Docker Container (run dockerfile)
  9. Deploy Container to base AMI
  10.  
  11. ELSE:
  12. Bake the AMI using configuration scripts.
  13.  
  14. Create new configuration with auto-scaling group (with or without ELB) and use the previously bake AMI ID as reference.
  15. Test in different environments (dev, staging)
  16. Deploy to prod (inactive)
  17. Add new reference (DNS or Load Balancer)
  18. Allow traffic flow slowly to new version (start with 5% and ramp up)
  19. Keep old version around until new version is 100% and you are fully satisfied with the behaviour
  20. Fast rollback if things go wrong
  21.  
  22. END
Add Comment
Please, Sign In to add comment