aws / aws/containers-roadmap

[ECS Fargate] [request]: Expose docker pull times

Open
#2,701 0 comments 3 reactions 0 assignees View on GitHub
ECS Fargate Proposed
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 to have information about the docker pull/extract times, and (for Windows specifically) the layers that were cached on the host. With this information we can monitor and optimize ECS Fargate start times.

**Which service(s) is this request for?**
This could be Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Though valid for all types of containers, specifically with Windows containers or other large images (like AI/ML), having real world metrics of pull times would enable a platform team to help developers optimize their docker images

**Are you currently working around this issue?**
Ensure images are small, local testing, ensure images are up to date (windows) so cached layers are used

Contributor guide

Open the contributing guide

Research direction

The issue names ECS Fargate and Docker pull/extract times but does not identify repository files, tests, or an implementation entry point. Start by locating the Fargate metrics or telemetry components; done means exposing pull and extraction timing, plus cached Windows layer information, in a usable form for monitoring start times.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker
Domain
cloud, observability, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.