@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class TaskDefinition extends Object implements Serializable, Cloneable, StructuredPojo
The details of a task definition which describes the container and volume definitions of an Amazon Elastic Container Service task. You can specify which Docker images to use, the required resources, and other configurations related to launching the task definition through an Amazon ECS service or task.
| Constructor and Description |
|---|
TaskDefinition() |
| Modifier and Type | Method and Description |
|---|---|
TaskDefinition |
clone() |
boolean |
equals(Object obj) |
List<String> |
getCompatibilities()
The launch type to use with your task.
|
List<ContainerDefinition> |
getContainerDefinitions()
A list of container definitions in JSON format that describe the different containers that make up your task.
|
String |
getCpu()
The number of
cpu units used by the task. |
String |
getExecutionRoleArn()
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission
to make AWS API calls on your behalf.
|
String |
getFamily()
The name of a family that this task definition is registered to.
|
List<InferenceAccelerator> |
getInferenceAccelerators()
The Elastic Inference accelerator associated with the task.
|
String |
getIpcMode()
The IPC resource namespace to use for the containers in the task.
|
String |
getMemory()
The amount (in MiB) of memory used by the task.
|
String |
getNetworkMode()
The Docker networking mode to use for the containers in the task.
|
String |
getPidMode()
The process namespace to use for the containers in the task.
|
List<TaskDefinitionPlacementConstraint> |
getPlacementConstraints()
An array of placement constraint objects to use for tasks.
|
ProxyConfiguration |
getProxyConfiguration()
The configuration details for the App Mesh proxy.
|
List<Attribute> |
getRequiresAttributes()
The container instance attributes required by your task.
|
List<String> |
getRequiresCompatibilities()
The launch type the task requires.
|
Integer |
getRevision()
The revision of the task in a particular family.
|
String |
getStatus()
The status of the task definition.
|
String |
getTaskDefinitionArn()
The full Amazon Resource Name (ARN) of the task definition.
|
String |
getTaskRoleArn()
The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that
grants containers in the task permission to call AWS APIs on your behalf.
|
List<Volume> |
getVolumes()
The list of volume definitions for the task.
|
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller)
Marshalls this structured data using the given
ProtocolMarshaller. |
void |
setCompatibilities(Collection<String> compatibilities)
The launch type to use with your task.
|
void |
setContainerDefinitions(Collection<ContainerDefinition> containerDefinitions)
A list of container definitions in JSON format that describe the different containers that make up your task.
|
void |
setCpu(String cpu)
The number of
cpu units used by the task. |
void |
setExecutionRoleArn(String executionRoleArn)
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission
to make AWS API calls on your behalf.
|
void |
setFamily(String family)
The name of a family that this task definition is registered to.
|
void |
setInferenceAccelerators(Collection<InferenceAccelerator> inferenceAccelerators)
The Elastic Inference accelerator associated with the task.
|
void |
setIpcMode(IpcMode ipcMode)
The IPC resource namespace to use for the containers in the task.
|
void |
setIpcMode(String ipcMode)
The IPC resource namespace to use for the containers in the task.
|
void |
setMemory(String memory)
The amount (in MiB) of memory used by the task.
|
void |
setNetworkMode(NetworkMode networkMode)
The Docker networking mode to use for the containers in the task.
|
void |
setNetworkMode(String networkMode)
The Docker networking mode to use for the containers in the task.
|
void |
setPidMode(PidMode pidMode)
The process namespace to use for the containers in the task.
|
void |
setPidMode(String pidMode)
The process namespace to use for the containers in the task.
|
void |
setPlacementConstraints(Collection<TaskDefinitionPlacementConstraint> placementConstraints)
An array of placement constraint objects to use for tasks.
|
void |
setProxyConfiguration(ProxyConfiguration proxyConfiguration)
The configuration details for the App Mesh proxy.
|
void |
setRequiresAttributes(Collection<Attribute> requiresAttributes)
The container instance attributes required by your task.
|
void |
setRequiresCompatibilities(Collection<String> requiresCompatibilities)
The launch type the task requires.
|
void |
setRevision(Integer revision)
The revision of the task in a particular family.
|
void |
setStatus(String status)
The status of the task definition.
|
void |
setStatus(TaskDefinitionStatus status)
The status of the task definition.
|
void |
setTaskDefinitionArn(String taskDefinitionArn)
The full Amazon Resource Name (ARN) of the task definition.
|
void |
setTaskRoleArn(String taskRoleArn)
The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that
grants containers in the task permission to call AWS APIs on your behalf.
|
void |
setVolumes(Collection<Volume> volumes)
The list of volume definitions for the task.
|
String |
toString()
Returns a string representation of this object.
|
TaskDefinition |
withCompatibilities(Collection<String> compatibilities)
The launch type to use with your task.
|
TaskDefinition |
withCompatibilities(Compatibility... compatibilities)
The launch type to use with your task.
|
TaskDefinition |
withCompatibilities(String... compatibilities)
The launch type to use with your task.
|
TaskDefinition |
withContainerDefinitions(Collection<ContainerDefinition> containerDefinitions)
A list of container definitions in JSON format that describe the different containers that make up your task.
|
TaskDefinition |
withContainerDefinitions(ContainerDefinition... containerDefinitions)
A list of container definitions in JSON format that describe the different containers that make up your task.
|
TaskDefinition |
withCpu(String cpu)
The number of
cpu units used by the task. |
TaskDefinition |
withExecutionRoleArn(String executionRoleArn)
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission
to make AWS API calls on your behalf.
|
TaskDefinition |
withFamily(String family)
The name of a family that this task definition is registered to.
|
TaskDefinition |
withInferenceAccelerators(Collection<InferenceAccelerator> inferenceAccelerators)
The Elastic Inference accelerator associated with the task.
|
TaskDefinition |
withInferenceAccelerators(InferenceAccelerator... inferenceAccelerators)
The Elastic Inference accelerator associated with the task.
|
TaskDefinition |
withIpcMode(IpcMode ipcMode)
The IPC resource namespace to use for the containers in the task.
|
TaskDefinition |
withIpcMode(String ipcMode)
The IPC resource namespace to use for the containers in the task.
|
TaskDefinition |
withMemory(String memory)
The amount (in MiB) of memory used by the task.
|
TaskDefinition |
withNetworkMode(NetworkMode networkMode)
The Docker networking mode to use for the containers in the task.
|
TaskDefinition |
withNetworkMode(String networkMode)
The Docker networking mode to use for the containers in the task.
|
TaskDefinition |
withPidMode(PidMode pidMode)
The process namespace to use for the containers in the task.
|
TaskDefinition |
withPidMode(String pidMode)
The process namespace to use for the containers in the task.
|
TaskDefinition |
withPlacementConstraints(Collection<TaskDefinitionPlacementConstraint> placementConstraints)
An array of placement constraint objects to use for tasks.
|
TaskDefinition |
withPlacementConstraints(TaskDefinitionPlacementConstraint... placementConstraints)
An array of placement constraint objects to use for tasks.
|
TaskDefinition |
withProxyConfiguration(ProxyConfiguration proxyConfiguration)
The configuration details for the App Mesh proxy.
|
TaskDefinition |
withRequiresAttributes(Attribute... requiresAttributes)
The container instance attributes required by your task.
|
TaskDefinition |
withRequiresAttributes(Collection<Attribute> requiresAttributes)
The container instance attributes required by your task.
|
TaskDefinition |
withRequiresCompatibilities(Collection<String> requiresCompatibilities)
The launch type the task requires.
|
TaskDefinition |
withRequiresCompatibilities(Compatibility... requiresCompatibilities)
The launch type the task requires.
|
TaskDefinition |
withRequiresCompatibilities(String... requiresCompatibilities)
The launch type the task requires.
|
TaskDefinition |
withRevision(Integer revision)
The revision of the task in a particular family.
|
TaskDefinition |
withStatus(String status)
The status of the task definition.
|
TaskDefinition |
withStatus(TaskDefinitionStatus status)
The status of the task definition.
|
TaskDefinition |
withTaskDefinitionArn(String taskDefinitionArn)
The full Amazon Resource Name (ARN) of the task definition.
|
TaskDefinition |
withTaskRoleArn(String taskRoleArn)
The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that
grants containers in the task permission to call AWS APIs on your behalf.
|
TaskDefinition |
withVolumes(Collection<Volume> volumes)
The list of volume definitions for the task.
|
TaskDefinition |
withVolumes(Volume... volumes)
The list of volume definitions for the task.
|
public void setTaskDefinitionArn(String taskDefinitionArn)
The full Amazon Resource Name (ARN) of the task definition.
taskDefinitionArn - The full Amazon Resource Name (ARN) of the task definition.public String getTaskDefinitionArn()
The full Amazon Resource Name (ARN) of the task definition.
public TaskDefinition withTaskDefinitionArn(String taskDefinitionArn)
The full Amazon Resource Name (ARN) of the task definition.
taskDefinitionArn - The full Amazon Resource Name (ARN) of the task definition.public List<ContainerDefinition> getContainerDefinitions()
A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
public void setContainerDefinitions(Collection<ContainerDefinition> containerDefinitions)
A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
containerDefinitions - A list of container definitions in JSON format that describe the different containers that make up your
task. For more information about container definition parameters and defaults, see Amazon ECS Task
Definitions in the Amazon Elastic Container Service Developer Guide.public TaskDefinition withContainerDefinitions(ContainerDefinition... containerDefinitions)
A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
NOTE: This method appends the values to the existing list (if any). Use
setContainerDefinitions(java.util.Collection) or withContainerDefinitions(java.util.Collection)
if you want to override the existing values.
containerDefinitions - A list of container definitions in JSON format that describe the different containers that make up your
task. For more information about container definition parameters and defaults, see Amazon ECS Task
Definitions in the Amazon Elastic Container Service Developer Guide.public TaskDefinition withContainerDefinitions(Collection<ContainerDefinition> containerDefinitions)
A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
containerDefinitions - A list of container definitions in JSON format that describe the different containers that make up your
task. For more information about container definition parameters and defaults, see Amazon ECS Task
Definitions in the Amazon Elastic Container Service Developer Guide.public void setFamily(String family)
The name of a family that this task definition is registered to. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.
A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.
family - The name of a family that this task definition is registered to. Up to 255 letters (uppercase and
lowercase), numbers, hyphens, and underscores are allowed.
A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.
public String getFamily()
The name of a family that this task definition is registered to. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.
A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.
A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.
public TaskDefinition withFamily(String family)
The name of a family that this task definition is registered to. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.
A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.
family - The name of a family that this task definition is registered to. Up to 255 letters (uppercase and
lowercase), numbers, hyphens, and underscores are allowed.
A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.
public void setTaskRoleArn(String taskRoleArn)
The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that grants containers in the task permission to call AWS APIs on your behalf. For more information, see Amazon ECS Task Role in the Amazon Elastic Container Service Developer Guide.
IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you launch the
Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code in order to take
advantage of the feature. For more information, see Windows IAM Roles
for Tasks in the Amazon Elastic Container Service Developer Guide.
taskRoleArn - The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role
that grants containers in the task permission to call AWS APIs on your behalf. For more information, see
Amazon ECS Task
Role in the Amazon Elastic Container Service Developer Guide.
IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you
launch the Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code in
order to take advantage of the feature. For more information, see Windows IAM
Roles for Tasks in the Amazon Elastic Container Service Developer Guide.
public String getTaskRoleArn()
The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that grants containers in the task permission to call AWS APIs on your behalf. For more information, see Amazon ECS Task Role in the Amazon Elastic Container Service Developer Guide.
IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you launch the
Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code in order to take
advantage of the feature. For more information, see Windows IAM Roles
for Tasks in the Amazon Elastic Container Service Developer Guide.
IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you
launch the Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code in
order to take advantage of the feature. For more information, see Windows
IAM Roles for Tasks in the Amazon Elastic Container Service Developer Guide.
public TaskDefinition withTaskRoleArn(String taskRoleArn)
The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that grants containers in the task permission to call AWS APIs on your behalf. For more information, see Amazon ECS Task Role in the Amazon Elastic Container Service Developer Guide.
IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you launch the
Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code in order to take
advantage of the feature. For more information, see Windows IAM Roles
for Tasks in the Amazon Elastic Container Service Developer Guide.
taskRoleArn - The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role
that grants containers in the task permission to call AWS APIs on your behalf. For more information, see
Amazon ECS Task
Role in the Amazon Elastic Container Service Developer Guide.
IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you
launch the Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code in
order to take advantage of the feature. For more information, see Windows IAM
Roles for Tasks in the Amazon Elastic Container Service Developer Guide.
public void setExecutionRoleArn(String executionRoleArn)
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make AWS API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide.
executionRoleArn - The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent
permission to make AWS API calls on your behalf. The task execution IAM role is required depending on the
requirements of your task. For more information, see Amazon ECS
task execution IAM role in the Amazon Elastic Container Service Developer Guide.public String getExecutionRoleArn()
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make AWS API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide.
public TaskDefinition withExecutionRoleArn(String executionRoleArn)
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make AWS API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide.
executionRoleArn - The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent
permission to make AWS API calls on your behalf. The task execution IAM role is required depending on the
requirements of your task. For more information, see Amazon ECS
task execution IAM role in the Amazon Elastic Container Service Developer Guide.public void setNetworkMode(String networkMode)
The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is required.
If you are using the EC2 launch type, any network mode can be used. If the network mode is set to
none, you cannot specify port mappings in your container definitions, and the tasks containers do
not have external connectivity. The host and awsvpc network modes offer the highest
networking performance for containers because they use the EC2 network stack instead of the virtualized network
stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped directly to
the corresponding host port (for the host network mode) or the attached elastic network interface
port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you must
specify a NetworkConfiguration value when you create a service or run a task with the task definition. For
more information, see Task Networking in
the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init package, or
AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a single
container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition with
Windows containers, you must not specify a network mode. If you use the console to register a task definition
with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
networkMode - The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is
required. If you are using the EC2 launch type, any network mode can be used. If the network mode is set
to none, you cannot specify port mappings in your container definitions, and the tasks
containers do not have external connectivity. The host and awsvpc network modes
offer the highest networking performance for containers because they use the EC2 network stack instead of
the virtualized network stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped
directly to the corresponding host port (for the host network mode) or the attached elastic
network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic
host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you
must specify a NetworkConfiguration value when you create a service or run a task with the task
definition. For more information, see Task
Networking in the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init
package, or AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a
single container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition
with Windows containers, you must not specify a network mode. If you use the console to register a task
definition with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
NetworkModepublic String getNetworkMode()
The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is required.
If you are using the EC2 launch type, any network mode can be used. If the network mode is set to
none, you cannot specify port mappings in your container definitions, and the tasks containers do
not have external connectivity. The host and awsvpc network modes offer the highest
networking performance for containers because they use the EC2 network stack instead of the virtualized network
stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped directly to
the corresponding host port (for the host network mode) or the attached elastic network interface
port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you must
specify a NetworkConfiguration value when you create a service or run a task with the task definition. For
more information, see Task Networking in
the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init package, or
AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a single
container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition with
Windows containers, you must not specify a network mode. If you use the console to register a task definition
with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is
required. If you are using the EC2 launch type, any network mode can be used. If the network mode is set
to none, you cannot specify port mappings in your container definitions, and the tasks
containers do not have external connectivity. The host and awsvpc network modes
offer the highest networking performance for containers because they use the EC2 network stack instead of
the virtualized network stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped
directly to the corresponding host port (for the host network mode) or the attached elastic
network interface port (for the awsvpc network mode), so you cannot take advantage of
dynamic host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you
must specify a NetworkConfiguration value when you create a service or run a task with the task
definition. For more information, see Task
Networking in the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init
package, or AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a
single container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task
definition with Windows containers, you must not specify a network mode. If you use the console to
register a task definition with Windows containers, you must choose the <default>
network mode object.
For more information, see Network settings in the Docker run reference.
NetworkModepublic TaskDefinition withNetworkMode(String networkMode)
The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is required.
If you are using the EC2 launch type, any network mode can be used. If the network mode is set to
none, you cannot specify port mappings in your container definitions, and the tasks containers do
not have external connectivity. The host and awsvpc network modes offer the highest
networking performance for containers because they use the EC2 network stack instead of the virtualized network
stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped directly to
the corresponding host port (for the host network mode) or the attached elastic network interface
port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you must
specify a NetworkConfiguration value when you create a service or run a task with the task definition. For
more information, see Task Networking in
the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init package, or
AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a single
container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition with
Windows containers, you must not specify a network mode. If you use the console to register a task definition
with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
networkMode - The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is
required. If you are using the EC2 launch type, any network mode can be used. If the network mode is set
to none, you cannot specify port mappings in your container definitions, and the tasks
containers do not have external connectivity. The host and awsvpc network modes
offer the highest networking performance for containers because they use the EC2 network stack instead of
the virtualized network stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped
directly to the corresponding host port (for the host network mode) or the attached elastic
network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic
host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you
must specify a NetworkConfiguration value when you create a service or run a task with the task
definition. For more information, see Task
Networking in the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init
package, or AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a
single container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition
with Windows containers, you must not specify a network mode. If you use the console to register a task
definition with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
NetworkModepublic void setNetworkMode(NetworkMode networkMode)
The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is required.
If you are using the EC2 launch type, any network mode can be used. If the network mode is set to
none, you cannot specify port mappings in your container definitions, and the tasks containers do
not have external connectivity. The host and awsvpc network modes offer the highest
networking performance for containers because they use the EC2 network stack instead of the virtualized network
stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped directly to
the corresponding host port (for the host network mode) or the attached elastic network interface
port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you must
specify a NetworkConfiguration value when you create a service or run a task with the task definition. For
more information, see Task Networking in
the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init package, or
AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a single
container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition with
Windows containers, you must not specify a network mode. If you use the console to register a task definition
with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
networkMode - The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is
required. If you are using the EC2 launch type, any network mode can be used. If the network mode is set
to none, you cannot specify port mappings in your container definitions, and the tasks
containers do not have external connectivity. The host and awsvpc network modes
offer the highest networking performance for containers because they use the EC2 network stack instead of
the virtualized network stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped
directly to the corresponding host port (for the host network mode) or the attached elastic
network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic
host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you
must specify a NetworkConfiguration value when you create a service or run a task with the task
definition. For more information, see Task
Networking in the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init
package, or AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a
single container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition
with Windows containers, you must not specify a network mode. If you use the console to register a task
definition with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
NetworkModepublic TaskDefinition withNetworkMode(NetworkMode networkMode)
The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is required.
If you are using the EC2 launch type, any network mode can be used. If the network mode is set to
none, you cannot specify port mappings in your container definitions, and the tasks containers do
not have external connectivity. The host and awsvpc network modes offer the highest
networking performance for containers because they use the EC2 network stack instead of the virtualized network
stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped directly to
the corresponding host port (for the host network mode) or the attached elastic network interface
port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you must
specify a NetworkConfiguration value when you create a service or run a task with the task definition. For
more information, see Task Networking in
the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init package, or
AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a single
container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition with
Windows containers, you must not specify a network mode. If you use the console to register a task definition
with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
networkMode - The Docker networking mode to use for the containers in the task. The valid values are none,
bridge, awsvpc, and host. The default Docker network mode is
bridge. If you are using the Fargate launch type, the awsvpc network mode is
required. If you are using the EC2 launch type, any network mode can be used. If the network mode is set
to none, you cannot specify port mappings in your container definitions, and the tasks
containers do not have external connectivity. The host and awsvpc network modes
offer the highest networking performance for containers because they use the EC2 network stack instead of
the virtualized network stack provided by the bridge mode.
With the host and awsvpc network modes, exposed container ports are mapped
directly to the corresponding host port (for the host network mode) or the attached elastic
network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic
host port mappings.
If the network mode is awsvpc, the task is allocated an elastic network interface, and you
must specify a NetworkConfiguration value when you create a service or run a task with the task
definition. For more information, see Task
Networking in the Amazon Elastic Container Service Developer Guide.
Currently, only Amazon ECS-optimized AMIs, other Amazon Linux variants with the ecs-init
package, or AWS Fargate infrastructure support the awsvpc network mode.
If the network mode is host, you cannot run multiple instantiations of the same task on a
single container instance when port mappings are used.
Docker for Windows uses different network modes than Docker for Linux. When you register a task definition
with Windows containers, you must not specify a network mode. If you use the console to register a task
definition with Windows containers, you must choose the <default> network mode object.
For more information, see Network settings in the Docker run reference.
NetworkModepublic void setRevision(Integer revision)
The revision of the task in a particular family. The revision is a version number of a task definition in a
family. When you register a task definition for the first time, the revision is 1. Each time that
you register a new revision of a task definition in the same family, the revision value always increases by one,
even if you have deregistered previous revisions in this family.
revision - The revision of the task in a particular family. The revision is a version number of a task definition in
a family. When you register a task definition for the first time, the revision is 1. Each
time that you register a new revision of a task definition in the same family, the revision value always
increases by one, even if you have deregistered previous revisions in this family.public Integer getRevision()
The revision of the task in a particular family. The revision is a version number of a task definition in a
family. When you register a task definition for the first time, the revision is 1. Each time that
you register a new revision of a task definition in the same family, the revision value always increases by one,
even if you have deregistered previous revisions in this family.
1. Each
time that you register a new revision of a task definition in the same family, the revision value always
increases by one, even if you have deregistered previous revisions in this family.public TaskDefinition withRevision(Integer revision)
The revision of the task in a particular family. The revision is a version number of a task definition in a
family. When you register a task definition for the first time, the revision is 1. Each time that
you register a new revision of a task definition in the same family, the revision value always increases by one,
even if you have deregistered previous revisions in this family.
revision - The revision of the task in a particular family. The revision is a version number of a task definition in
a family. When you register a task definition for the first time, the revision is 1. Each
time that you register a new revision of a task definition in the same family, the revision value always
increases by one, even if you have deregistered previous revisions in this family.public List<Volume> getVolumes()
The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath parameters are
not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
If your tasks are using the Fargate launch type, the host and sourcePath
parameters are not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
public void setVolumes(Collection<Volume> volumes)
The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath parameters are
not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
volumes - The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath
parameters are not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
public TaskDefinition withVolumes(Volume... volumes)
The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath parameters are
not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
NOTE: This method appends the values to the existing list (if any). Use
setVolumes(java.util.Collection) or withVolumes(java.util.Collection) if you want to override
the existing values.
volumes - The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath
parameters are not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
public TaskDefinition withVolumes(Collection<Volume> volumes)
The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath parameters are
not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
volumes - The list of volume definitions for the task.
If your tasks are using the Fargate launch type, the host and sourcePath
parameters are not supported.
For more information about volume definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide.
public void setStatus(String status)
The status of the task definition.
status - The status of the task definition.TaskDefinitionStatuspublic String getStatus()
The status of the task definition.
TaskDefinitionStatuspublic TaskDefinition withStatus(String status)
The status of the task definition.
status - The status of the task definition.TaskDefinitionStatuspublic void setStatus(TaskDefinitionStatus status)
The status of the task definition.
status - The status of the task definition.TaskDefinitionStatuspublic TaskDefinition withStatus(TaskDefinitionStatus status)
The status of the task definition.
status - The status of the task definition.TaskDefinitionStatuspublic List<Attribute> getRequiresAttributes()
The container instance attributes required by your task. This field is not valid if you are using the Fargate launch type for your task.
public void setRequiresAttributes(Collection<Attribute> requiresAttributes)
The container instance attributes required by your task. This field is not valid if you are using the Fargate launch type for your task.
requiresAttributes - The container instance attributes required by your task. This field is not valid if you are using the
Fargate launch type for your task.public TaskDefinition withRequiresAttributes(Attribute... requiresAttributes)
The container instance attributes required by your task. This field is not valid if you are using the Fargate launch type for your task.
NOTE: This method appends the values to the existing list (if any). Use
setRequiresAttributes(java.util.Collection) or withRequiresAttributes(java.util.Collection) if
you want to override the existing values.
requiresAttributes - The container instance attributes required by your task. This field is not valid if you are using the
Fargate launch type for your task.public TaskDefinition withRequiresAttributes(Collection<Attribute> requiresAttributes)
The container instance attributes required by your task. This field is not valid if you are using the Fargate launch type for your task.
requiresAttributes - The container instance attributes required by your task. This field is not valid if you are using the
Fargate launch type for your task.public List<TaskDefinitionPlacementConstraint> getPlacementConstraints()
An array of placement constraint objects to use for tasks. This field is not valid if you are using the Fargate launch type for your task.
public void setPlacementConstraints(Collection<TaskDefinitionPlacementConstraint> placementConstraints)
An array of placement constraint objects to use for tasks. This field is not valid if you are using the Fargate launch type for your task.
placementConstraints - An array of placement constraint objects to use for tasks. This field is not valid if you are using the
Fargate launch type for your task.public TaskDefinition withPlacementConstraints(TaskDefinitionPlacementConstraint... placementConstraints)
An array of placement constraint objects to use for tasks. This field is not valid if you are using the Fargate launch type for your task.
NOTE: This method appends the values to the existing list (if any). Use
setPlacementConstraints(java.util.Collection) or withPlacementConstraints(java.util.Collection)
if you want to override the existing values.
placementConstraints - An array of placement constraint objects to use for tasks. This field is not valid if you are using the
Fargate launch type for your task.public TaskDefinition withPlacementConstraints(Collection<TaskDefinitionPlacementConstraint> placementConstraints)
An array of placement constraint objects to use for tasks. This field is not valid if you are using the Fargate launch type for your task.
placementConstraints - An array of placement constraint objects to use for tasks. This field is not valid if you are using the
Fargate launch type for your task.public List<String> getCompatibilities()
The launch type to use with your task. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
Compatibilitypublic void setCompatibilities(Collection<String> compatibilities)
The launch type to use with your task. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
compatibilities - The launch type to use with your task. For more information, see Amazon ECS Launch
Types in the Amazon Elastic Container Service Developer Guide.Compatibilitypublic TaskDefinition withCompatibilities(String... compatibilities)
The launch type to use with your task. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
NOTE: This method appends the values to the existing list (if any). Use
setCompatibilities(java.util.Collection) or withCompatibilities(java.util.Collection) if you
want to override the existing values.
compatibilities - The launch type to use with your task. For more information, see Amazon ECS Launch
Types in the Amazon Elastic Container Service Developer Guide.Compatibilitypublic TaskDefinition withCompatibilities(Collection<String> compatibilities)
The launch type to use with your task. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
compatibilities - The launch type to use with your task. For more information, see Amazon ECS Launch
Types in the Amazon Elastic Container Service Developer Guide.Compatibilitypublic TaskDefinition withCompatibilities(Compatibility... compatibilities)
The launch type to use with your task. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
compatibilities - The launch type to use with your task. For more information, see Amazon ECS Launch
Types in the Amazon Elastic Container Service Developer Guide.Compatibilitypublic List<String> getRequiresCompatibilities()
The launch type the task requires. If no value is specified, it will default to EC2. Valid values
include EC2 and FARGATE.
EC2. Valid
values include EC2 and FARGATE.Compatibilitypublic void setRequiresCompatibilities(Collection<String> requiresCompatibilities)
The launch type the task requires. If no value is specified, it will default to EC2. Valid values
include EC2 and FARGATE.
requiresCompatibilities - The launch type the task requires. If no value is specified, it will default to EC2. Valid
values include EC2 and FARGATE.Compatibilitypublic TaskDefinition withRequiresCompatibilities(String... requiresCompatibilities)
The launch type the task requires. If no value is specified, it will default to EC2. Valid values
include EC2 and FARGATE.
NOTE: This method appends the values to the existing list (if any). Use
setRequiresCompatibilities(java.util.Collection) or
withRequiresCompatibilities(java.util.Collection) if you want to override the existing values.
requiresCompatibilities - The launch type the task requires. If no value is specified, it will default to EC2. Valid
values include EC2 and FARGATE.Compatibilitypublic TaskDefinition withRequiresCompatibilities(Collection<String> requiresCompatibilities)
The launch type the task requires. If no value is specified, it will default to EC2. Valid values
include EC2 and FARGATE.
requiresCompatibilities - The launch type the task requires. If no value is specified, it will default to EC2. Valid
values include EC2 and FARGATE.Compatibilitypublic TaskDefinition withRequiresCompatibilities(Compatibility... requiresCompatibilities)
The launch type the task requires. If no value is specified, it will default to EC2. Valid values
include EC2 and FARGATE.
requiresCompatibilities - The launch type the task requires. If no value is specified, it will default to EC2. Valid
values include EC2 and FARGATE.Compatibilitypublic void setCpu(String cpu)
The number of cpu units used by the task. If you are using the EC2 launch type, this field is
optional and any value can be used. If you are using the Fargate launch type, this field is required and you must
use one of the following values, which determines your range of valid values for the memory
parameter:
256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6
GB), 7168 (7 GB), 8192 (8 GB)
2048 (2 vCPU) - Available memory values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024
(1 GB)
4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024
(1 GB)
cpu - The number of cpu units used by the task. If you are using the EC2 launch type, this field is
optional and any value can be used. If you are using the Fargate launch type, this field is required and
you must use one of the following values, which determines your range of valid values for the
memory parameter:
256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB),
6144 (6 GB), 7168 (7 GB), 8192 (8 GB)
2048 (2 vCPU) - Available memory values: Between 4096 (4 GB) and 16384 (16 GB) in increments
of 1024 (1 GB)
4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments
of 1024 (1 GB)
public String getCpu()
The number of cpu units used by the task. If you are using the EC2 launch type, this field is
optional and any value can be used. If you are using the Fargate launch type, this field is required and you must
use one of the following values, which determines your range of valid values for the memory
parameter:
256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6
GB), 7168 (7 GB), 8192 (8 GB)
2048 (2 vCPU) - Available memory values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024
(1 GB)
4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024
(1 GB)
cpu units used by the task. If you are using the EC2 launch type, this field
is optional and any value can be used. If you are using the Fargate launch type, this field is required
and you must use one of the following values, which determines your range of valid values for the
memory parameter:
256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB),
6144 (6 GB), 7168 (7 GB), 8192 (8 GB)
2048 (2 vCPU) - Available memory values: Between 4096 (4 GB) and 16384 (16 GB) in increments
of 1024 (1 GB)
4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments
of 1024 (1 GB)
public TaskDefinition withCpu(String cpu)
The number of cpu units used by the task. If you are using the EC2 launch type, this field is
optional and any value can be used. If you are using the Fargate launch type, this field is required and you must
use one of the following values, which determines your range of valid values for the memory
parameter:
256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6
GB), 7168 (7 GB), 8192 (8 GB)
2048 (2 vCPU) - Available memory values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024
(1 GB)
4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024
(1 GB)
cpu - The number of cpu units used by the task. If you are using the EC2 launch type, this field is
optional and any value can be used. If you are using the Fargate launch type, this field is required and
you must use one of the following values, which determines your range of valid values for the
memory parameter:
256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB),
6144 (6 GB), 7168 (7 GB), 8192 (8 GB)
2048 (2 vCPU) - Available memory values: Between 4096 (4 GB) and 16384 (16 GB) in increments
of 1024 (1 GB)
4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments
of 1024 (1 GB)
public void setMemory(String memory)
The amount (in MiB) of memory used by the task.
If using the EC2 launch type, this field is optional and any value can be used. If a task-level memory value is specified then the container-level memory value is optional.
If using the Fargate launch type, this field is required and you must use one of the following values, which
determines your range of valid values for the cpu parameter:
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu values: 1024 (1 vCPU)
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2
vCPU)
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4
vCPU)
memory - The amount (in MiB) of memory used by the task.
If using the EC2 launch type, this field is optional and any value can be used. If a task-level memory value is specified then the container-level memory value is optional.
If using the Fargate launch type, this field is required and you must use one of the following values,
which determines your range of valid values for the cpu parameter:
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu values: 1024 (1 vCPU)
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values:
2048 (2 vCPU)
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values:
4096 (4 vCPU)
public String getMemory()
The amount (in MiB) of memory used by the task.
If using the EC2 launch type, this field is optional and any value can be used. If a task-level memory value is specified then the container-level memory value is optional.
If using the Fargate launch type, this field is required and you must use one of the following values, which
determines your range of valid values for the cpu parameter:
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu values: 1024 (1 vCPU)
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2
vCPU)
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4
vCPU)
If using the EC2 launch type, this field is optional and any value can be used. If a task-level memory value is specified then the container-level memory value is optional.
If using the Fargate launch type, this field is required and you must use one of the following values,
which determines your range of valid values for the cpu parameter:
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu values: 1024 (1 vCPU)
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values:
2048 (2 vCPU)
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values:
4096 (4 vCPU)
public TaskDefinition withMemory(String memory)
The amount (in MiB) of memory used by the task.
If using the EC2 launch type, this field is optional and any value can be used. If a task-level memory value is specified then the container-level memory value is optional.
If using the Fargate launch type, this field is required and you must use one of the following values, which
determines your range of valid values for the cpu parameter:
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu values: 1024 (1 vCPU)
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2
vCPU)
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4
vCPU)
memory - The amount (in MiB) of memory used by the task.
If using the EC2 launch type, this field is optional and any value can be used. If a task-level memory value is specified then the container-level memory value is optional.
If using the Fargate launch type, this field is required and you must use one of the following values,
which determines your range of valid values for the cpu parameter:
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu values: 1024 (1 vCPU)
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values:
2048 (2 vCPU)
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values:
4096 (4 vCPU)
public List<InferenceAccelerator> getInferenceAccelerators()
The Elastic Inference accelerator associated with the task.
public void setInferenceAccelerators(Collection<InferenceAccelerator> inferenceAccelerators)
The Elastic Inference accelerator associated with the task.
inferenceAccelerators - The Elastic Inference accelerator associated with the task.public TaskDefinition withInferenceAccelerators(InferenceAccelerator... inferenceAccelerators)
The Elastic Inference accelerator associated with the task.
NOTE: This method appends the values to the existing list (if any). Use
setInferenceAccelerators(java.util.Collection) or
withInferenceAccelerators(java.util.Collection) if you want to override the existing values.
inferenceAccelerators - The Elastic Inference accelerator associated with the task.public TaskDefinition withInferenceAccelerators(Collection<InferenceAccelerator> inferenceAccelerators)
The Elastic Inference accelerator associated with the task.
inferenceAccelerators - The Elastic Inference accelerator associated with the task.public void setPidMode(String pidMode)
The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified the
host PID mode on the same container instance share the same process namespace with the host Amazon
EC2 instance. If task is specified, all containers within the specified task share the same process
namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run
reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker
security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
pidMode - The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified
the host PID mode on the same container instance share the same process namespace with the
host Amazon EC2 instance. If task is specified, all containers within the specified task
share the same process namespace. If no value is specified, the default is a private namespace. For more
information, see PID
settings in the Docker run reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
PidModepublic String getPidMode()
The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified the
host PID mode on the same container instance share the same process namespace with the host Amazon
EC2 instance. If task is specified, all containers within the specified task share the same process
namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run
reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker
security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
host or
task. If host is specified, then all containers within the tasks that specified
the host PID mode on the same container instance share the same process namespace with the
host Amazon EC2 instance. If task is specified, all containers within the specified task
share the same process namespace. If no value is specified, the default is a private namespace. For more
information, see PID
settings in the Docker run reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
PidModepublic TaskDefinition withPidMode(String pidMode)
The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified the
host PID mode on the same container instance share the same process namespace with the host Amazon
EC2 instance. If task is specified, all containers within the specified task share the same process
namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run
reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker
security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
pidMode - The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified
the host PID mode on the same container instance share the same process namespace with the
host Amazon EC2 instance. If task is specified, all containers within the specified task
share the same process namespace. If no value is specified, the default is a private namespace. For more
information, see PID
settings in the Docker run reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
PidModepublic void setPidMode(PidMode pidMode)
The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified the
host PID mode on the same container instance share the same process namespace with the host Amazon
EC2 instance. If task is specified, all containers within the specified task share the same process
namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run
reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker
security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
pidMode - The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified
the host PID mode on the same container instance share the same process namespace with the
host Amazon EC2 instance. If task is specified, all containers within the specified task
share the same process namespace. If no value is specified, the default is a private namespace. For more
information, see PID
settings in the Docker run reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
PidModepublic TaskDefinition withPidMode(PidMode pidMode)
The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified the
host PID mode on the same container instance share the same process namespace with the host Amazon
EC2 instance. If task is specified, all containers within the specified task share the same process
namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run
reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker
security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
pidMode - The process namespace to use for the containers in the task. The valid values are host or
task. If host is specified, then all containers within the tasks that specified
the host PID mode on the same container instance share the same process namespace with the
host Amazon EC2 instance. If task is specified, all containers within the specified task
share the same process namespace. If no value is specified, the default is a private namespace. For more
information, see PID
settings in the Docker run reference.
If the host PID mode is used, be aware that there is a heightened risk of undesired process
namespace expose. For more information, see Docker security.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
PidModepublic void setIpcMode(String ipcMode)
The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the tasks
that specified the host IPC mode on the same container instance share the same IPC resources with
the host Amazon EC2 instance. If task is specified, all containers within the specified task share
the same IPC resources. If none is specified, then IPC resources within the containers of a task are
private and not shared with other containers in a task or on the container instance. If no value is specified,
then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more
information, see IPC settings in
the Docker run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace
expose. For more information, see Docker
security.
If you are setting namespaced kernel parameters using systemControls for the containers in the task,
the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are not
supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will apply
to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
ipcMode - The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the
tasks that specified the host IPC mode on the same container instance share the same IPC
resources with the host Amazon EC2 instance. If task is specified, all containers within the
specified task share the same IPC resources. If none is specified, then IPC resources within
the containers of a task are private and not shared with other containers in a task or on the container
instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon
setting on the container instance. For more information, see IPC settings in the Docker
run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC
namespace expose. For more information, see Docker security.
If you are setting namespaced kernel parameters using systemControls for the containers in
the task, the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are
not supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will
apply to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
IpcModepublic String getIpcMode()
The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the tasks
that specified the host IPC mode on the same container instance share the same IPC resources with
the host Amazon EC2 instance. If task is specified, all containers within the specified task share
the same IPC resources. If none is specified, then IPC resources within the containers of a task are
private and not shared with other containers in a task or on the container instance. If no value is specified,
then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more
information, see IPC settings in
the Docker run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace
expose. For more information, see Docker
security.
If you are setting namespaced kernel parameters using systemControls for the containers in the task,
the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are not
supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will apply
to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
host,
task, or none. If host is specified, then all containers within
the tasks that specified the host IPC mode on the same container instance share the same IPC
resources with the host Amazon EC2 instance. If task is specified, all containers within the
specified task share the same IPC resources. If none is specified, then IPC resources within
the containers of a task are private and not shared with other containers in a task or on the container
instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon
setting on the container instance. For more information, see IPC settings in the Docker
run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC
namespace expose. For more information, see Docker security.
If you are setting namespaced kernel parameters using systemControls for the containers in
the task, the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are
not supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will
apply to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
IpcModepublic TaskDefinition withIpcMode(String ipcMode)
The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the tasks
that specified the host IPC mode on the same container instance share the same IPC resources with
the host Amazon EC2 instance. If task is specified, all containers within the specified task share
the same IPC resources. If none is specified, then IPC resources within the containers of a task are
private and not shared with other containers in a task or on the container instance. If no value is specified,
then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more
information, see IPC settings in
the Docker run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace
expose. For more information, see Docker
security.
If you are setting namespaced kernel parameters using systemControls for the containers in the task,
the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are not
supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will apply
to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
ipcMode - The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the
tasks that specified the host IPC mode on the same container instance share the same IPC
resources with the host Amazon EC2 instance. If task is specified, all containers within the
specified task share the same IPC resources. If none is specified, then IPC resources within
the containers of a task are private and not shared with other containers in a task or on the container
instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon
setting on the container instance. For more information, see IPC settings in the Docker
run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC
namespace expose. For more information, see Docker security.
If you are setting namespaced kernel parameters using systemControls for the containers in
the task, the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are
not supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will
apply to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
IpcModepublic void setIpcMode(IpcMode ipcMode)
The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the tasks
that specified the host IPC mode on the same container instance share the same IPC resources with
the host Amazon EC2 instance. If task is specified, all containers within the specified task share
the same IPC resources. If none is specified, then IPC resources within the containers of a task are
private and not shared with other containers in a task or on the container instance. If no value is specified,
then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more
information, see IPC settings in
the Docker run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace
expose. For more information, see Docker
security.
If you are setting namespaced kernel parameters using systemControls for the containers in the task,
the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are not
supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will apply
to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
ipcMode - The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the
tasks that specified the host IPC mode on the same container instance share the same IPC
resources with the host Amazon EC2 instance. If task is specified, all containers within the
specified task share the same IPC resources. If none is specified, then IPC resources within
the containers of a task are private and not shared with other containers in a task or on the container
instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon
setting on the container instance. For more information, see IPC settings in the Docker
run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC
namespace expose. For more information, see Docker security.
If you are setting namespaced kernel parameters using systemControls for the containers in
the task, the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are
not supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will
apply to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
IpcModepublic TaskDefinition withIpcMode(IpcMode ipcMode)
The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the tasks
that specified the host IPC mode on the same container instance share the same IPC resources with
the host Amazon EC2 instance. If task is specified, all containers within the specified task share
the same IPC resources. If none is specified, then IPC resources within the containers of a task are
private and not shared with other containers in a task or on the container instance. If no value is specified,
then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more
information, see IPC settings in
the Docker run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace
expose. For more information, see Docker
security.
If you are setting namespaced kernel parameters using systemControls for the containers in the task,
the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are not
supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will apply
to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
ipcMode - The IPC resource namespace to use for the containers in the task. The valid values are host,
task, or none. If host is specified, then all containers within the
tasks that specified the host IPC mode on the same container instance share the same IPC
resources with the host Amazon EC2 instance. If task is specified, all containers within the
specified task share the same IPC resources. If none is specified, then IPC resources within
the containers of a task are private and not shared with other containers in a task or on the container
instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon
setting on the container instance. For more information, see IPC settings in the Docker
run reference.
If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC
namespace expose. For more information, see Docker security.
If you are setting namespaced kernel parameters using systemControls for the containers in
the task, the following will apply to your IPC resource namespace. For more information, see System
Controls in the Amazon Elastic Container Service Developer Guide.
For tasks that use the host IPC mode, IPC namespace related systemControls are
not supported.
For tasks that use the task IPC mode, IPC namespace related systemControls will
apply to all containers within a task.
This parameter is not supported for Windows containers or tasks using the Fargate launch type.
IpcModepublic void setProxyConfiguration(ProxyConfiguration proxyConfiguration)
The configuration details for the App Mesh proxy.
Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least version
1.26.0-1 of the ecs-init package to enable a proxy configuration. If your container instances are
launched from the Amazon ECS-optimized AMI version 20190301 or later, then they contain the required
versions of the container agent and ecs-init. For more information, see Amazon ECS-optimized
Linux AMI in the Amazon Elastic Container Service Developer Guide.
proxyConfiguration - The configuration details for the App Mesh proxy.
Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least
version 1.26.0-1 of the ecs-init package to enable a proxy configuration. If your container
instances are launched from the Amazon ECS-optimized AMI version 20190301 or later, then they
contain the required versions of the container agent and ecs-init. For more information, see
Amazon
ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide.
public ProxyConfiguration getProxyConfiguration()
The configuration details for the App Mesh proxy.
Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least version
1.26.0-1 of the ecs-init package to enable a proxy configuration. If your container instances are
launched from the Amazon ECS-optimized AMI version 20190301 or later, then they contain the required
versions of the container agent and ecs-init. For more information, see Amazon ECS-optimized
Linux AMI in the Amazon Elastic Container Service Developer Guide.
Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least
version 1.26.0-1 of the ecs-init package to enable a proxy configuration. If your container
instances are launched from the Amazon ECS-optimized AMI version 20190301 or later, then
they contain the required versions of the container agent and ecs-init. For more
information, see Amazon
ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide.
public TaskDefinition withProxyConfiguration(ProxyConfiguration proxyConfiguration)
The configuration details for the App Mesh proxy.
Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least version
1.26.0-1 of the ecs-init package to enable a proxy configuration. If your container instances are
launched from the Amazon ECS-optimized AMI version 20190301 or later, then they contain the required
versions of the container agent and ecs-init. For more information, see Amazon ECS-optimized
Linux AMI in the Amazon Elastic Container Service Developer Guide.
proxyConfiguration - The configuration details for the App Mesh proxy.
Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least
version 1.26.0-1 of the ecs-init package to enable a proxy configuration. If your container
instances are launched from the Amazon ECS-optimized AMI version 20190301 or later, then they
contain the required versions of the container agent and ecs-init. For more information, see
Amazon
ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide.
public String toString()
toString in class ObjectObject.toString()public TaskDefinition clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojoProtocolMarshaller.marshall in interface StructuredPojoprotocolMarshaller - Implementation of ProtocolMarshaller used to marshall this object's data.