aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Hitting max number of capacity providers per cluster
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::ECS::ClusterCapacityProviderAssociations
### Resource name
_No response_
### Description
Cx has initially created AWS::ECS::ClusterCapacityProviderAssociations resource with 8 Capacity providers.
And then performed an UPDATE operation on the resource to remove one of the existing Capacity provider (FARGATE) and added 3 new capacity providers to the CapacityProviders list. All together there are total of 10 Capacity providers (which is the max no. of capacity providers that can be associated with the ECS cluster.)
However, update operation has failed with the following error:
AWS::ECS::ClusterCapacityProviderAssociations EcsJobsClusterCapacityProviderAssociation
UPDATE_FAILED Resource handler returned message: "The maximum number of capacity providers per cluster has been exceeded. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 380dea5e-5765-4b12-b815-aaf759b0ff58; Proxy: null)" (RequestToken: 7db54b1a-4bf0-d057-3e18-cca01be93095, HandlerErrorCode: InvalidRequest)
Request to add ability to perform "REMOVE_CAPACITY_PROVIDERS" followed by "ADD_CAPACITY_PROVIDERS".
Contributor guide
Research direction
Start with the AWS::ECS::ClusterCapacityProviderAssociations resource behavior described in the report and determine how updates are currently processed. No repository file or test is identified; completion should cover an update that removes an existing provider before adding replacements without exceeding the ECS cluster limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100