Create a task set in the specified cluster and service
Source:R/ecs_operations.R
ecs_create_task_set.RdCreate a task set in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide.
See https://www.paws-r-sdk.com/docs/ecs_create_task_set/ for full documentation.
Usage
ecs_create_task_set(
service,
cluster,
externalId = NULL,
taskDefinition,
networkConfiguration = NULL,
loadBalancers = NULL,
serviceRegistries = NULL,
launchType = NULL,
capacityProviderStrategy = NULL,
platformVersion = NULL,
scale = NULL,
clientToken = NULL,
tags = NULL
)Arguments
- service
[required] The short name or full Amazon Resource Name (ARN) of the service to create the task set in.
- cluster
[required] The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service to create the task set in.
- externalId
An optional non-unique tag that identifies this task set in external systems. If the task set is associated with a service discovery registry, the tasks in this task set will have the
ECS_TASK_SET_EXTERNAL_IDCloud Map attribute set to the provided value.- taskDefinition
[required] The task definition for the tasks in the task set to use. If a revision isn't specified, the latest
ACTIVErevision is used.- networkConfiguration
An object representing the network configuration for a task set.
- loadBalancers
A load balancer object representing the load balancer to use with the task set. The supported load balancer types are either an Application Load Balancer or a Network Load Balancer.
- serviceRegistries
The details of the service discovery registries to assign to this task set. For more information, see Service discovery.
- launchType
The launch type that new tasks in the task set uses. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
If a
launchTypeis specified, thecapacityProviderStrategyparameter must be omitted.- capacityProviderStrategy
The capacity provider strategy to use for the task set.
A capacity provider strategy consists of one or more capacity providers along with the
baseandweightto assign to them. A capacity provider must be associated with the cluster to be used in a capacity provider strategy. Theput_cluster_capacity_providersAPI is used to associate a capacity provider with a cluster. Only capacity providers with anACTIVEorUPDATINGstatus can be used.If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used.If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New capacity providers can be created with the CreateCapacityProviderProviderAPI operation.
To use a Fargate capacity provider, specify either the
FARGATEorFARGATE_SPOTcapacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used.The
put_cluster_capacity_providersAPI operation is used to update the list of available capacity providers for a cluster after the cluster is created.- platformVersion
The platform version that the tasks in the task set uses. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used.- scale
A floating-point percentage of the desired number of tasks to place and keep running in the task set.
- clientToken
An identifier that you provide to ensure the idempotency of the request. It must be unique and is case sensitive. Up to 36 ASCII characters in the range of 33-126 (inclusive) are allowed.
The metadata that you apply to the task set to help you categorize and organize them. Each tag consists of a key and an optional value. You define both. When a service is deleted, the tags are deleted.
The following basic restrictions apply to tags:
Maximum number of tags per resource - 50
For each resource, each tag key must be unique, and each tag key can have only one value.
Maximum key length - 128 Unicode characters in UTF-8
Maximum value length - 256 Unicode characters in UTF-8
If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
Tag keys and values are case-sensitive.
Do not use
aws:,AWS:, or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.