Struct aws_sdk_ecs::client::fluent_builders::RunTask [−][src]
pub struct RunTask<C = DynConnector, M = AwsMiddleware, R = Standard> { /* fields omitted */ }
Expand description
Fluent builder constructing a request to RunTask
.
Starts a new task using the specified task definition.
You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies. For more information, see Scheduling Tasks in the Amazon Elastic Container Service Developer Guide.
Alternatively, you can use StartTask to use your own scheduler or place tasks manually on specific container instances.
The Amazon ECS API follows an eventual consistency model, due to the distributed nature of the system supporting the API. This means that the result of an API command you run that affects your Amazon ECS resources might not be immediately visible to all subsequent commands you run. Keep this in mind when you carry out an API command that immediately follows a previous API command.
To manage eventual consistency, you can do the following:
-
Confirm the state of the resource before you run a command to modify it. Run the DescribeTasks command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. To do this, run the DescribeTasks command repeatedly, starting with a couple of seconds of wait time and increasing gradually up to five minutes of wait time.
-
Add wait time between subsequent commands, even if the DescribeTasks command returns an accurate response. 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.
Implementations
impl<C, M, R> RunTask<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
impl<C, M, R> RunTask<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
pub async fn send(self) -> Result<RunTaskOutput, SdkError<RunTaskError>> where
R::Policy: SmithyRetryPolicy<RunTaskInputOperationOutputAlias, RunTaskOutput, RunTaskError, RunTaskInputOperationRetryAlias>,
pub async fn send(self) -> Result<RunTaskOutput, SdkError<RunTaskError>> where
R::Policy: SmithyRetryPolicy<RunTaskInputOperationOutputAlias, RunTaskOutput, RunTaskError, RunTaskInputOperationRetryAlias>,
Sends the request and returns the response.
If an error occurs, an SdkError
will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
Appends an item to capacityProviderStrategy
.
To override the contents of this collection use set_capacity_provider_strategy
.
The capacity provider strategy to use for the task.
If a capacityProviderStrategy
is specified, the launchType
parameter must be omitted. If no capacityProviderStrategy
or
launchType
is specified, the
defaultCapacityProviderStrategy
for the cluster is used.
When you use cluster auto scaling, you must specify capacityProviderStrategy
and not launchType
.
A capacity provider strategy may contain a maximum of 6 capacity providers.
pub fn set_capacity_provider_strategy(
self,
input: Option<Vec<CapacityProviderStrategyItem>>
) -> Self
pub fn set_capacity_provider_strategy(
self,
input: Option<Vec<CapacityProviderStrategyItem>>
) -> Self
The capacity provider strategy to use for the task.
If a capacityProviderStrategy
is specified, the launchType
parameter must be omitted. If no capacityProviderStrategy
or
launchType
is specified, the
defaultCapacityProviderStrategy
for the cluster is used.
When you use cluster auto scaling, you must specify capacityProviderStrategy
and not launchType
.
A capacity provider strategy may contain a maximum of 6 capacity providers.
The short name or full Amazon Resource Name (ARN) of the cluster on which to run your task. If you do not specify a cluster, the default cluster is assumed.
The short name or full Amazon Resource Name (ARN) of the cluster on which to run your task. If you do not specify a cluster, the default cluster is assumed.
The number of instantiations of the specified task to place on your cluster. You can specify up to 10 tasks per call.
The number of instantiations of the specified task to place on your cluster. You can specify up to 10 tasks per call.
Specifies whether to enable Amazon ECS managed tags for the task. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide.
Specifies whether to enable Amazon ECS managed tags for the task. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide.
Whether or not to enable the execute command functionality for the containers in this
task. If true
, this enables execute command functionality on all containers
in the task.
Whether or not to enable the execute command functionality for the containers in this
task. If true
, this enables execute command functionality on all containers
in the task.
The name of the task group to associate with the task. The default value is the family
name of the task definition (for example, family:my-family-name
).
The name of the task group to associate with the task. The default value is the family
name of the task definition (for example, family:my-family-name
).
The infrastructure on which to run your standalone task. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
The FARGATE
launch type runs your tasks on Fargate On-Demand
infrastructure.
Fargate Spot infrastructure is available for use but a capacity provider strategy must be used. For more information, see Fargate capacity providers in the Amazon ECS User Guide for Fargate.
The EC2
launch type runs your tasks on Amazon EC2 instances registered to your
cluster.
The EXTERNAL
launch type runs your tasks on your on-premise server or
virtual machine (VM) capacity registered to your cluster.
A task can use either a launch type or a capacity provider strategy. If a
launchType
is specified, the capacityProviderStrategy
parameter must be omitted.
When you use cluster auto scaling, you must specify capacityProviderStrategy
and not launchType
.
The infrastructure on which to run your standalone task. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
The FARGATE
launch type runs your tasks on Fargate On-Demand
infrastructure.
Fargate Spot infrastructure is available for use but a capacity provider strategy must be used. For more information, see Fargate capacity providers in the Amazon ECS User Guide for Fargate.
The EC2
launch type runs your tasks on Amazon EC2 instances registered to your
cluster.
The EXTERNAL
launch type runs your tasks on your on-premise server or
virtual machine (VM) capacity registered to your cluster.
A task can use either a launch type or a capacity provider strategy. If a
launchType
is specified, the capacityProviderStrategy
parameter must be omitted.
When you use cluster auto scaling, you must specify capacityProviderStrategy
and not launchType
.
The network configuration for the task. This parameter is required for task
definitions that use the awsvpc
network mode to receive their own elastic
network interface, and it is not supported for other network modes. For more
information, see Task networking
in the Amazon Elastic Container Service Developer Guide.
The network configuration for the task. This parameter is required for task
definitions that use the awsvpc
network mode to receive their own elastic
network interface, and it is not supported for other network modes. For more
information, see Task networking
in the Amazon Elastic Container Service Developer Guide.
A list of container overrides in JSON format that specify the name of a container in
the specified task definition and the overrides it should receive. You can override the
default command for a container (that is specified in the task definition or Docker
image) with a command
override. You can also override existing environment
variables (that are specified in the task definition or Docker image) on a container or
add new environment variables to it with an environment
override.
A total of 8192 characters are allowed for overrides. This limit includes the JSON formatting characters of the override structure.
A list of container overrides in JSON format that specify the name of a container in
the specified task definition and the overrides it should receive. You can override the
default command for a container (that is specified in the task definition or Docker
image) with a command
override. You can also override existing environment
variables (that are specified in the task definition or Docker image) on a container or
add new environment variables to it with an environment
override.
A total of 8192 characters are allowed for overrides. This limit includes the JSON formatting characters of the override structure.
Appends an item to placementConstraints
.
To override the contents of this collection use set_placement_constraints
.
An array of placement constraint objects to use for the task. You can specify up to 10 constraints per task (including constraints in the task definition and those specified at runtime).
An array of placement constraint objects to use for the task. You can specify up to 10 constraints per task (including constraints in the task definition and those specified at runtime).
Appends an item to placementStrategy
.
To override the contents of this collection use set_placement_strategy
.
The placement strategy objects to use for the task. You can specify a maximum of 5 strategy rules per task.
The placement strategy objects to use for the task. You can specify a maximum of 5 strategy rules per task.
The platform version the task should use. A platform version is only specified for
tasks hosted on Fargate. If one is not specified, the LATEST
platform version is used by default. For more information, see Fargate platform versions in the
Amazon Elastic Container Service Developer Guide.
The platform version the task should use. A platform version is only specified for
tasks hosted on Fargate. If one is not specified, the LATEST
platform version is used by default. For more information, see Fargate platform versions in the
Amazon Elastic Container Service Developer Guide.
Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags are not propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action.
An error will be received if you specify the SERVICE
option when
running a task.
Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags are not propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action.
An error will be received if you specify the SERVICE
option when
running a task.
The reference ID to use for the task. The reference ID can have a maximum length of 1024 characters.
The reference ID to use for the task. The reference ID can have a maximum length of 1024 characters.
An optional tag specified when a task is started. For example, if you automatically
trigger a task to run a batch process job, you could apply a unique identifier for that
job to your task with the startedBy
parameter. You can then identify which
tasks belong to that job by filtering the results of a ListTasks call
with the startedBy
value. Up to 36 letters (uppercase and lowercase),
numbers, hyphens, and underscores are allowed.
If a task is started by an Amazon ECS service, then the startedBy
parameter
contains the deployment ID of the service that starts it.
An optional tag specified when a task is started. For example, if you automatically
trigger a task to run a batch process job, you could apply a unique identifier for that
job to your task with the startedBy
parameter. You can then identify which
tasks belong to that job by filtering the results of a ListTasks call
with the startedBy
value. Up to 36 letters (uppercase and lowercase),
numbers, hyphens, and underscores are allowed.
If a task is started by an Amazon ECS service, then the startedBy
parameter
contains the deployment ID of the service that starts it.
Appends an item to tags
.
To override the contents of this collection use set_tags
.
The metadata that you apply to the task to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define.
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.
The metadata that you apply to the task to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define.
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.
The family
and revision
(family:revision
) or
full ARN of the task definition to run. If a revision
is not specified,
the latest ACTIVE
revision is used.
The full ARN value must match the value that you specified ias the Resource
of the IAM principal's permissions policy. For example, if the Resource
is
arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*, the
taskDefinition
ARN value must be
arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName
.
The family
and revision
(family:revision
) or
full ARN of the task definition to run. If a revision
is not specified,
the latest ACTIVE
revision is used.
The full ARN value must match the value that you specified ias the Resource
of the IAM principal's permissions policy. For example, if the Resource
is
arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*, the
taskDefinition
ARN value must be
arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName
.
Trait Implementations
Auto Trait Implementations
impl<C = DynConnector, M = AwsMiddleware, R = Standard> !RefUnwindSafe for RunTask<C, M, R>
impl<C = DynConnector, M = AwsMiddleware, R = Standard> !UnwindSafe for RunTask<C, M, R>
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more