aws / aws/containers-roadmap

[Fargate] [request]: Support ECS_TASK_METADATA_RPS_LIMIT or similar parameter

Open
#1,649 3 comments 10 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**
Support ECS_TASK_METADATA_RPS_LIMIT parameter like the EC2-based ECS agent or a similar configuration in Task Definition.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Our application running in Fargate is failing to download files from S3 due to API throttling limits on the metadata end point. We would like to increase the limit, particularly /v2/credentials endpoint on the task instance.

**Are you currently working around this issue?**
We are planning to do exponential back-off. However, our pipeline uses a rigorous validation process so it will not be rolled out in time.

**Additional context**
We contacted AWS support and they pointed us to this roadmap. We also discuss about caching the credentials with AWS SDK.

**Attachments**
N/A

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or implementation entry points are identified in the issue. Start by reviewing the Fargate request and its ECS_TASK_METADATA_RPS_LIMIT comparison; done would mean a supported parameter or similar Task Definition configuration that addresses throttling at the task metadata endpoint.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.