Difference between revisions of "Amazon ECS capacity providers"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
== Related == | == Related == | ||
* <code>[[The maximum number of capacity providers per cluster has been exceeded]]</code> | * <code>[[The maximum number of capacity providers per cluster has been exceeded]]</code> | ||
| + | * [[Auto Scaling group capacity providers]] and [[Fargate capacity providers]] | ||
== See also == | == See also == | ||
Revision as of 10:44, 22 July 2022
aws ecs create-capacity-provider aws ecs delete-capacity-provider aws ecs describe-capacity-providers aws ecs put-cluster-capacity-providers aws ecs update-capacity-provider
Related
The maximum number of capacity providers per cluster has been exceeded- Auto Scaling group capacity providers and Fargate capacity providers
See also
aws ecs [ create-capacity-provider | delete-capacity-provider | describe-capacity-providers | put-cluster-capacity-providers | update-capacity-provider ]- Amazon ECS, Service, Tasks (Task overview), capacity providers, Cluster Auto Scaling (CAS),
aws ecs, ecs-cli, ~/.ecs/config, AWS Copilot, AWS Fargate, AWS CloudWatch Container Insights,/etc/ecs/ecs.config, Security group (SG), container agent, task definition, Amazon ECS events, best practices, Amazon ECS Exec Checker, Amazon ECS Agent, Service Connect,AWSServiceRoleForECS, Terraform ECS, AWS ECS Rolling deployments
Advertising:
