[ECS] [request]: Expose Deployment status via metrics and appropriate CLI command
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
Introduce and expose Deployment metrics from ECS control plane via:
1. CloudWatch metrics
2. Appropriate changes to `aws ecs wait` or possibly introduce a new CLI command to track the deployment status.
**Which service(s) is this request for?**
ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
It is almost impossible to track failed deployments using the ECS control plane. We have to utilize AWS Lambda to poll the status of the rolled out tasks. The `aws ecs wait` does not fit the purpose if the service is using a circuit breaker. The lack of dedicated metrics is also making this harder from the CloudWatch perspective. Hence we rolled out AWS Lambda which checks that the latest Task Definition is in production.
**Are you currently working around this issue?**
Using AWS Lambda to inspect the newly rolled out tasks match the latest Task Definition. The AWS Lambda is invoked from the CI/CD.
**Additional context**
.
**Attachments**
Contributor guide
Assessment
This issue has not been assessed yet.