An ECS service is being updated.
Validate the new version gradually and return to the old version if an issue appears.
Which architecture is most appropriate?
Use an ECS blue/green deployment with CodeDeploy to test the new task set before switching traffic.
Detailed explanation
DNS TTL does not update or validate ECS task images.
DNS TTL does not update or validate ECS task images.
Separate task sets can run in parallel while validation and rollback are managed.
Separate task sets can run in parallel while validation and rollback are managed.
This causes interruption and makes rollback difficult.
This causes interruption and makes rollback difficult.
S3 Lifecycle manages objects and does not control ECS deployments.
S3 Lifecycle manages objects and does not control ECS deployments.
Check official documentation
Compare the following points with the official documentation.
CodeDeploy ECS blue/green deploymentの公式説明を確認する。
What to confirm
コンテナデプロイの検証・切り替え・ロールバックを説明できる。
Key points
- ECS blue/green
- CodeDeploy
- Rollback
Notes
- Environment: AWS公式ECS・CodeDeployドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Parallel validation
The new task set can be tested before it receives all production traffic.
Reversible change
Keeping the old task set makes rollback faster and safer.