Amazon ECS now integrates with CloudWatch alarms for deployment monitoring in the AWS GovCloud (US) Regions

[Amazon Elastic Container Service (Amazon ECS)](https://aws.amazon.com/ecs/) now lets you add automated safeguards for rolling updates of Amazon ECS services in the AWS GovCloud (US) Regions. You can now monitor and automatically react to changes during an Amazon ECS rolling update by using Amazon CloudWatch alarms. This allows you to more easily automate discovery and remediation for failed deployments and minimize the impact of a bad change. Amazon ECS customers use [deployment circuit breaker](https://aws.amazon.com/blogs/containers/announcing-amazon-ecs-deployment-circuit-breaker/) to monitor task launch and health check failures which indicate whether the deployment will reach steady state. In some cases, even if containers start running successfully, the deployment can introduce regressions that cause degradation in infrastructure usage (e.g. cpu utilization) or performance (e.g. response latency). To monitor and remediate such issues, you can now configure Amazon ECS to monitor Amazon CloudWatch alarms which track the metrics most relevant to your application. If a metric breach occurs during the deployment, Amazon ECS stops and rolls back the deployment to the previous stable version. When you use CloudWatch alarms to monitor your deployment, Amazon ECS monitors these alarms for a period of time after the new service version has reached steady state based on the configuration of your CloudWatch alarm. You can configure Amazon CloudWatch alarms to monitor rolling updates for new and existing Amazon ECS services that use the ‘ECS’ deployment controller in all AWS regions. To get started, follow steps in this [blog](https://aws.amazon.com/blogs/containers/automate-rollbacks-for-amazon-ecs-rolling-deployments-with-cloudwatch-alarms/), or read our [documentation](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html).