aws / aws/containers-roadmap

[ECS/CloudFormation] [request]: Assign New Capacity Providers to Existing Clusters Using CloudFormation

Open
#1,156 1 comment 0 reactions 0 assignees 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**
I would like to be able to assign a **Capacity Provider** to an existing **ECS Cluster** using CloudFormation.

**Which service(s) is this request for?**
ECS, CloudFormation

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I have an existing ECS Cluster created with a CFN template. This Cluster will have Services with specific Capacity Providers created with different CFN templates on a new stack. Currently assigning a Capacity Provider to a Service is not enough for the Cluster to 'know' it has a new Capacity Provider, and Services created as such will fail to deploy their tasks due to lack of ECS Instances.

**Are you currently working around this issue?**
I have implemented a lambda function with a custom resource that calls ```putClusterCapacityProviders``` in order to register the new Capacity Providers with the Cluster.

Having to implement this Custom Resource seems unnecessary because if a Capacity Provider is associated with a Service it should automatically be associated with the underlying Cluster. Or we should be able to pass a property to the Capacity Provider Resource defining the Cluster where it'll live.

Thanks

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or entry points are mentioned. Start by reviewing the ECS and CloudFormation capacity-provider behavior described in the issue and the existing custom-resource workaround; done would mean an agreed CloudFormation-supported way to register a new capacity provider on an existing ECS cluster.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.