[ECS] [request]: make available logConfiguration in Describe Task API Call
- 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**
I would like the AWS ECS "DescribeServices" API Call to expose the Log Configuration in the response. If there are other missing bits of data I would like to see those as well.
**Which service(s) is this request for?**
ECS, ECS Fargate
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
It seems that there is no way to (officially) determine where logs from a task are written using the AWS ECS API.
**Are you currently working around this issue?**
We know that the logs for this particular task are written to CloudWatch, so we capture the result of the AWS "Run Task" command and then use the resulting task ARN to intuit the log stream name (example: `app/app/6a974574e7404b78956074dd624290b1`) because the log stream name matches the last part of the task arn `(arn:aws:ecs:us-east-1::task/ecs-run-task/6a974574e7404b78956074dd624290b1)`.
**Additional context**
None
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Contributor guide
Research direction
Start by reviewing the AWS ECS DescribeServices API and the existing Run Task response and task ARN workaround described in the issue. Confirm whether logConfiguration is available through ECS or ECS Fargate responses, then identify the AWS service-side change and validation path needed for the requested CloudWatch log metadata to appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100