aws / aws/containers-roadmap

[Fargate] [request]: ECS Add lower vCPU / Memory options

Open
#2,382 0 comments 4 reactions 1 assignee Claimed by @herrhound 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**
My service has some burst behaviour where a few of the containers in a task need a full vCPU for a limited amount of time. Really I need 3 vCPU in regard to RAM 4GB is more than sufficient.

**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?**
ECS has a defined list of vCPU and RAM combinations and the minimum step from 2vCPU with 4GB is to 4vCPU with 8GB.
Double the price is a kinda hard pill.

I could break the services apart to use 3 vCPU but the tasks within the service logically deploy in this combination (at least for now)

**Are you currently working around this issue?**

Not really, I've bumped to 4 vCPU with 8GB of ram

**Additional context**
Anything else we should know?

**Attachments**
none

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.