Class CfnTaskSet.CapacityProviderStrategyItemProperty
The details of a capacity provider strategy.
Inheritance
Namespace: Amazon.CDK.AWS.ECS
Assembly: Amazon.CDK.Lib.dll
Syntax (csharp)
public class CapacityProviderStrategyItemProperty : Object, CfnTaskSet.ICapacityProviderStrategyItemPropertySyntax (vb)
Public Class CapacityProviderStrategyItemProperty
Inherits Object
Implements CfnTaskSet.ICapacityProviderStrategyItemPropertyRemarks
A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.
Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.
If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateClusterCapacityProvider API operation.
To use a AWS Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The AWS Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.
With FARGATE_SPOT , you can run interruption tolerant tasks at a rate that's discounted compared to the FARGATE price. FARGATE_SPOT runs tasks on spare compute capacity. When AWS needs the capacity back, your tasks are interrupted with a two-minute warning. FARGATE_SPOT supports Linux tasks with the X86_64 architecture on platform version 1.3.0 or later. FARGATE_SPOT supports Linux tasks with the ARM64 architecture on platform version 1.4.0 or later.
A capacity provider strategy can contain a maximum of 20 capacity providers.
ExampleMetadata: fixture=_generated
Examples
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
using Amazon.CDK.AWS.ECS;
var capacityProviderStrategyItemProperty = new CapacityProviderStrategyItemProperty {
Base = 123,
CapacityProvider = "capacityProvider",
Weight = 123
};Synopsis
Constructors
| Capacity |
Properties
| Base | The base value designates how many tasks, at a minimum, to run on the specified capacity provider. |
| Capacity |
The short name of the capacity provider. |
| Weight | The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. |
Constructors
CapacityProviderStrategyItemProperty()
public CapacityProviderStrategyItemProperty()Properties
Base
The base value designates how many tasks, at a minimum, to run on the specified capacity provider.
public Nullable<double> Base { get; set; }Property Value
System.
Remarks
Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.
CapacityProvider
The short name of the capacity provider.
public string CapacityProvider { get; set; }Property Value
System.
Remarks
Weight
The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider.
public Nullable<double> Weight { get; set; }Property Value
System.
Remarks
The weight value is taken into consideration after the base value, if defined, is satisfied.
If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.
An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .