[Fargate][ECS] [Feature Request]: Allow Fargate to run only 1 task per Availability Zone
- 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**
What do you want us to build?
Create some sort of Daemon Set option for Fargate in which only 1 Task per Availability Zone will be scheduled
**Which service(s) is this request for?**
This could be Fargate, ECS.
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently there is no way to do this, and the ECS Scheduler will spread tasks evenly across AZs, and if one AZ goes down, a Task might end up on the same AZ as the other one.
**Are you currently working around this issue?**
The only work around is to set the Desired Count equal to the number of subnets in the service, but if one eventually goes down, a task will eventually be placed on the same subnet as another one already running
**Additional context**
Anything else we should know?
**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
This is a roadmap request for Fargate/ECS scheduling rather than a repository change, and the payload names no files, tests, or entry points. Start by researching the ECS Scheduler's Availability Zone placement behavior and the requested one-task-per-AZ constraint; done means Fargate reliably maintains at most one task in each Availability Zone, including after an AZ failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100