aws / aws/containers-roadmap

[ECS] [request]: Use Fargate spot from Step Functions RunTask

Open
#2,308 0 comments 5 reactions 1 assignee Claimed by @BWashishtha View on GitHub
ECS 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**
When we use ECS RunTask API from Step Functions ([doc](https://docs.aws.amazon.com/step-functions/latest/dg/connect-ecs.html)), we want to set `capacityProviderStrategy` to use Fargate spot capacity.

**Which service(s) is this request for?**
Fargate, ECS, Step Functions

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

Fargate spot is much cheaper than on-demand capacity. Also with Step Functions we can handle spot interruption events more easily. It'd be great match Step Functions x Fargate spot.

**Are you currently working around this issue?**
Currently we can only use fargate on-demand capacity.

**Additional context**

**Attachments**

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.