Containers-roadmap: [Fargate] [request]: Add higher vCPU / Memory options

[mbj]

Tell us about your request

Increase maximum allowed vCPU / Memory resources of Fargate tasks.

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?

I want to offload computationally heavy tasks, that can only be locally parallelized to Fargate. Without having to boot an EC2 instance and its associated maintenance overhead.

An example of such a task is the compilation of GHC (the Haskell compiler). Its build system allows parallel computation, but no distribution.

Are you currently working around this issue?

Considering to script the use of a bigger EC2 instance, with its associated maintenance overhead.

Additional context

None.

[fengyj]

yes, pls support more cpu and more ebs. @abby-fuller , does AWS have any plan on this?

[srinivaspype]

Any SLA for this? Currently Fargate implementation provides general-purpose CPU cycle speed (2.2GHz- 2.3GHz) for us and not capable of running CPU/GPU critical applications.

[mavericknavs]

Please extend the current vCPUs limit. It will really help a lot of our Customers.

[Djolivald]

Any idea if other CPU option are even considered? This is 'proposed' for a while without feedback from AWS.
Would love to have 8/16/32 vcpu options, without having to take care of EC2 maintenance.