What's changed: In-scope service coverage (axis B): added CodeArtifact/CloudShell (s1) and Amplify (s3) definitions, roles, and selection criteria.
4.3Deployment Strategies and Elastic Beanstalk
Understand deployment-strategy trade-offs (all-at-once/rolling/blue-green/canary; speed vs. safety/rollback) and the PaaS Elastic Beanstalk.
How you release a new version involves a speed vs. safety trade-off. Choose a strategy considering downtime and ease of rollback.
4.3.1Deployment strategies
- All-at-once: replace everything at once; fastest but downtime risk.
- Rolling: update in batches; avoids full downtime but mixes versions briefly.
- Blue/Green: stand up a new env and shift traffic; easy rollback. Canary shifts a small % first, then ramps up.
- Elastic Beanstalk: a PaaS that builds/deploys an environment from uploaded code (with selectable strategies).
Common on DVA: avoid downtime with easy rollback = blue/green, gradual release from a small % = canary, upload code and get an environment = Elastic Beanstalk. Lambda aliases + weights also enable gradual deploys.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.