aws / aws/containers-roadmap

[Fargate] [request]: Need capacity guarantee for Fargate

Open
#752 0 comments 1 reaction 0 assignees View on GitHub
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**
Provide a way to guarantee capacity for Fargate clusters.

**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?**
In case of a disaster in my primary AWS region, I want to be able to make sure I have reserved capacity for my Fargate clusters in my DR region.

**Are you currently working around this issue?**
How are you currently solving this problem? No workarounds

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the request for guaranteed Fargate capacity and its disaster-recovery use case in a secondary AWS region. Define what reserved capacity for Fargate clusters would mean and how success would be verified; the issue names no repository files, tests, or implementation entry point.

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.