Validate a new ECS service version with five percent of users first.
Increase traffic only when the metrics remain healthy.
Which deployment method is most appropriate?
Use a CodeDeploy ECS canary deployment to shift traffic in stages while monitoring the new version.
Detailed explanation
A canary deployment sends staged traffic to the new version and can stop or roll back on signals.
A canary deployment sends staged traffic to the new version and can stop or roll back on signals.
An all-at-once switch removes staged validation and increases rollback impact.
An all-at-once switch removes staged validation and increases rollback impact.
DNS TTL does not define task-level canary delivery.
DNS TTL does not define task-level canary delivery.
S3 lifecycle management does not control ECS traffic.
S3 lifecycle management does not control ECS traffic.
Check official documentation
Compare the following points with the official documentation.
CodeDeploy ECS canary deploymentsの公式説明を確認する。
What to confirm
canary、blue/green、ローリング更新を区別できる。
Key points
- ECS canary
- Staged traffic
- CodeDeploy
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Progressive exposure
Small initial traffic limits impact while metrics are evaluated.
Rollback signal
Health metrics can determine whether the next traffic step should proceed.