Release a new application version to production.
Keep the old environment available, shift traffic only after validation, and roll back if needed.
Which deployment method is most appropriate?
Use a CodeDeploy blue/green deployment to validate the new environment before switching traffic.
Detailed explanation
Separate old and new environments allow validation, traffic switching, and rollback.
Separate old and new environments allow validation, traffic switching, and rollback.
DNS TTL does not deploy an EC2 application version.
DNS TTL does not deploy an EC2 application version.
A simultaneous update increases outage risk and removes a simple rollback path.
A simultaneous update increases outage risk and removes a simple rollback path.
S3 Lifecycle is not an application deployment controller.
S3 Lifecycle is not an application deployment controller.
Check official documentation
Compare the following points with the official documentation.
AWS CodeDeploy blue green deploymentsの公式説明を確認する。
What to confirm
インプレース更新とblue/green切り替えの違いを説明できる。
Key points
- CodeDeploy
- Blue/green deployment
- Rollback
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Release isolation
Separate environments limit the blast radius of a faulty revision.
Traffic switch
A controlled routing change makes the validated environment active and preserves a rollback path.