Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- START
- Create a Base AMI and harden it if you have too.
- IF DOCKER:
- 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)
- Create an as-light-as possible Dockerfile (used a base container)
- Copy code on build into Docker Container (run dockerfile)
- Deploy Container to base AMI
- ELSE:
- Bake the AMI using configuration scripts.
- Create new configuration with auto-scaling group (with or without ELB) and use the previously bake AMI ID as reference.
- Test in different environments (dev, staging)
- Deploy to prod (inactive)
- Add new reference (DNS or Load Balancer)
- Allow traffic flow slowly to new version (start with 5% and ramp up)
- Keep old version around until new version is 100% and you are fully satisfied with the behaviour
- Fast rollback if things go wrong
- END
Add Comment
Please, Sign In to add comment