![]() ![]() For more information about the environment variable file syntax, see Declare default environment variables in file. Lines beginning with # are treated as comments and are ignored. Each line in an environment file should contain an environment variable in VARIABLE=VALUE format. You can specify up to ten environment files. Ī list of files containing the environment variables to pass to a container. ![]() 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. ![]() 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.Īn 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. 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 no weight value is specified, the default value of 0 is used. The weight value is taken into consideration after the base value, if defined, is satisfied. The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The 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.Ī capacity provider strategy may contain a maximum of 6 capacity providers. To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation. If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster. 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. 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. The details of a capacity provider strategy. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |