AWS AmazonECS documentation change
Summary
Changed monitoring responsibility from CodeDeploy to Amazon ECS in deployment workflow documentation
Security assessment
Clarifies service responsibility but doesn't address security controls or vulnerabilities
Diff
diff --git a/AmazonECS/latest/developerguide/blue-green-deployment-how-it-works.md b/AmazonECS/latest/developerguide/blue-green-deployment-how-it-works.md index a7250b862..0d5b21d43 100644 --- a//AmazonECS/latest/developerguide/blue-green-deployment-how-it-works.md +++ b//AmazonECS/latest/developerguide/blue-green-deployment-how-it-works.md @@ -44 +44 @@ The enhanced deployment workflow includes the following detailed steps: - 6. **Monitoring and Validation** : Throughout the traffic shift, CodeDeploy monitors CloudWatch metrics, alarm states, and deployment health. Automatic rollback triggers activate if issues are detected. + 6. **Monitoring and Validation** : Throughout the traffic shift, Amazon ECS monitors CloudWatch metrics, alarm states, and deployment health. Automatic rollback triggers activate if issues are detected. @@ -50 +50 @@ The enhanced deployment workflow includes the following detailed steps: - 9. **Final State** : The green environment becomes the new production environment, handling 100% of traffic. The deployment is marked as successful in CodeDeploy. + 9. **Final State** : The green environment becomes the new production environment, handling 100% of traffic. The deployment is marked as successful.