task_definition
The full task definition description. | STRUCT(
"task_definition_arn" VARCHAR,
"container_definitions" STRUCT(
"name" VARCHAR,
"image" VARCHAR,
"repository_credentials" STRUCT(
"credentials_parameter" VARCHAR
),
"cpu" BIGINT,
"memory" BIGINT,
"memory_reservation" BIGINT,
"links" VARCHAR[],
"port_mappings" STRUCT(
"container_port" BIGINT,
"host_port" BIGINT,
"protocol" VARCHAR,
"name" VARCHAR,
"app_protocol" VARCHAR,
"container_port_range" VARCHAR
)[],
"essential" BOOLEAN,
"restart_policy" STRUCT(
"enabled" BOOLEAN,
"ignored_exit_codes" BIGINT[],
"restart_attempt_period" BIGINT
),
"entry_point" VARCHAR[],
"command" VARCHAR[],
"environment" STRUCT(
"name" VARCHAR,
"value" VARCHAR
)[],
"environment_files" STRUCT(
"value" VARCHAR,
"type" VARCHAR
)[],
"mount_points" STRUCT(
"source_volume" VARCHAR,
"container_path" VARCHAR,
"read_only" BOOLEAN
)[],
"volumes_from" STRUCT(
"source_container" VARCHAR,
"read_only" BOOLEAN
)[],
"linux_parameters" STRUCT(
"capabilities" STRUCT(
"add" VARCHAR[],
"drop" VARCHAR[]
),
"devices" STRUCT(
"host_path" VARCHAR,
"container_path" VARCHAR,
"permissions" VARCHAR[]
)[],
"init_process_enabled" BOOLEAN,
"shared_memory_size" BIGINT,
"tmpfs" STRUCT(
"container_path" VARCHAR,
"size" BIGINT,
"mount_options" VARCHAR[]
)[],
"max_swap" BIGINT,
"swappiness" BIGINT
),
"secrets" STRUCT(
"name" VARCHAR,
"value_from" VARCHAR
)[],
"depends_on" STRUCT(
"container_name" VARCHAR,
"condition" VARCHAR
)[],
"start_timeout" BIGINT,
"stop_timeout" BIGINT,
"hostname" VARCHAR,
"user" VARCHAR,
"working_directory" VARCHAR,
"disable_networking" BOOLEAN,
"privileged" BOOLEAN,
"readonly_root_filesystem" BOOLEAN,
"dns_servers" VARCHAR[],
"dns_search_domains" VARCHAR[],
"extra_hosts" STRUCT(
"hostname" VARCHAR,
"ip_address" VARCHAR
)[],
"docker_security_options" VARCHAR[],
"interactive" BOOLEAN,
"pseudo_terminal" BOOLEAN,
"docker_labels" MAP(VARCHAR, VARCHAR),
"ulimits" STRUCT(
"name" VARCHAR,
"soft_limit" BIGINT,
"hard_limit" BIGINT
)[],
"log_configuration" STRUCT(
"log_driver" VARCHAR,
"options" MAP(VARCHAR, VARCHAR),
"secret_options" STRUCT(
"name" VARCHAR,
"value_from" VARCHAR
)[]
),
"health_check" STRUCT(
"command" VARCHAR[],
"interval" BIGINT,
"timeout" BIGINT,
"retries" BIGINT,
"start_period" BIGINT
),
"system_controls" STRUCT(
"namespace" VARCHAR,
"value" VARCHAR
)[],
"resource_requirements" STRUCT(
"value" VARCHAR,
"type" VARCHAR
)[],
"firelens_configuration" STRUCT(
"type" VARCHAR,
"options" MAP(VARCHAR, VARCHAR)
),
"credential_specs" VARCHAR[]
)[],
"family" VARCHAR,
"task_role_arn" VARCHAR,
"execution_role_arn" VARCHAR,
"network_mode" VARCHAR,
"revision" BIGINT,
"volumes" STRUCT(
"name" VARCHAR,
"host" STRUCT(
"source_path" VARCHAR
),
"docker_volume_configuration" STRUCT(
"scope" VARCHAR,
"autoprovision" BOOLEAN,
"driver" VARCHAR,
"driver_opts" MAP(VARCHAR, VARCHAR),
"labels" MAP(VARCHAR, VARCHAR)
),
"efs_volume_configuration" STRUCT(
"file_system_id" VARCHAR,
"root_directory" VARCHAR,
"transit_encryption" VARCHAR,
"transit_encryption_port" BIGINT,
"authorization_config" STRUCT(
"access_point_id" VARCHAR,
"iam" VARCHAR
)
),
"fsx_windows_file_server_volume_configuration" STRUCT(
"file_system_id" VARCHAR,
"root_directory" VARCHAR,
"authorization_config" STRUCT(
"credentials_parameter" VARCHAR,
"domain" VARCHAR
)
),
"configured_at_launch" BOOLEAN
)[],
"status" VARCHAR,
"requires_attributes" STRUCT(
"name" VARCHAR,
"value" VARCHAR,
"target_type" VARCHAR,
"target_id" VARCHAR
)[],
"placement_constraints" STRUCT(
"type" VARCHAR,
"expression" VARCHAR
)[],
"compatibilities" VARCHAR[],
"runtime_platform" STRUCT(
"cpu_architecture" VARCHAR,
"operating_system_family" VARCHAR
),
"requires_compatibilities" VARCHAR[],
"cpu" VARCHAR,
"memory" VARCHAR,
"inference_accelerators" STRUCT(
"device_name" VARCHAR,
"device_type" VARCHAR
)[],
"pid_mode" VARCHAR,
"ipc_mode" VARCHAR,
"proxy_configuration" STRUCT(
"type" VARCHAR,
"container_name" VARCHAR,
"properties" STRUCT(
"name" VARCHAR,
"value" VARCHAR
)[]
),
"registered_at" TIMESTAMP_S,
"deregistered_at" TIMESTAMP_S,
"registered_by" VARCHAR,
"ephemeral_storage" STRUCT(
"size_in_gi_b" BIGINT
)
) |
Show child fields- task_definition.compatibilities[]
- task_definition.container_definitions[]
Show child fields- task_definition.container_definitions[].command[]
- task_definition.container_definitions[].cpu
The number of cpu units reserved for the container. This parameter maps to CpuShares in the docker conainer create commandand the --cpu-shares option to docker run. This field is optional for tasks using the Fargate launch type, and the only requirement is that the total amount of CPU reserved for all containers within a task be lower than the task-level cpu value. You can determine the number of CPU units that are available per EC2 instance type by multiplying the vCPUs listed for that instance type on the Amazon EC2 Instances detail page by 1,024. Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount. For example, if you run a single-container task on a single-core instance type with 512 CPU units specified for that container, and that's the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time. However, if you launched another copy of the same task on that container instance, each task is guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float to higher CPU usage if the other container was not using it. If both tasks were 100% active all of the time, they would be limited to 512 CPU units. On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers. The minimum valid CPU share value that the Linux kernel allows is 2, and the maximum valid CPU share value that the Linux kernel allows is 262144. However, the CPU parameter isn't required, and you can use CPU values below 2 or above 262144 in your container definitions. For CPU values below 2 (including null) or above 262144, the behavior varies based on your Amazon ECS container agent version: -
Agent versions less than or equal to 1.1.0: Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares. -
Agent versions greater than or equal to 1.2.0: Null, zero, and CPU values of 1 are passed to Docker as 2. -
Agent versions greater than or equal to 1.84.0: CPU values greater than 256 vCPU are passed to Docker as 256, which is equivalent to 262144 CPU shares. On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota. Windows containers only have access to the specified amount of CPU that's described in the task definition. A null or zero CPU value is passed to Docker as 0, which Windows interprets as 1% of one CPU. - task_definition.container_definitions[].credential_specs[]
- task_definition.container_definitions[].depends_on[]
Show child fields- task_definition.container_definitions[].depends_on[].condition
The dependency condition of the container. The following are the available conditions and their behavior: -
START - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start. -
COMPLETE - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container. -
SUCCESS - This condition is the same as COMPLETE, but it also requires that the container exits with a zero status. This condition can't be set on an essential container. -
HEALTHY - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup. - task_definition.container_definitions[].depends_on[].container_name
The name of a container.
- task_definition.container_definitions[].disable_networking
When this parameter is true, networking is off within the container. This parameter maps to NetworkDisabled in the docker conainer create command. This parameter is not supported for Windows containers. - task_definition.container_definitions[].dns_search_domains[]
- task_definition.container_definitions[].dns_servers[]
- task_definition.container_definitions[].docker_labels
A key/value map of labels to add to the container. This parameter maps to Labels in the docker conainer create command and the --label option to docker run. This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}' - task_definition.container_definitions[].docker_security_options[]
- task_definition.container_definitions[].entry_point[]
- task_definition.container_definitions[].environment[]
Show child fields- task_definition.container_definitions[].environment[].name
The name of the key-value pair. For environment variables, this is the name of the environment variable. - task_definition.container_definitions[].environment[].value
The value of the key-value pair. For environment variables, this is the value of the environment variable.
- task_definition.container_definitions[].environment_files[]
Show child fields- task_definition.container_definitions[].environment_files[].type
The file type to use. Environment files are objects in Amazon S3. The only supported value is s3. - task_definition.container_definitions[].environment_files[].value
The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.
- task_definition.container_definitions[].essential
If the essential parameter of a container is marked as true, and that container fails or stops for any reason, all other containers that are part of the task are stopped. If the essential parameter of a container is marked as false, its failure doesn't affect the rest of the containers in a task. If this parameter is omitted, a container is assumed to be essential. All tasks must have at least one essential container. If you have an application that's composed of multiple containers, group containers that are used for a common purpose into components, and separate the different components into multiple task definitions. For more information, see Application Architecture in the Amazon Elastic Container Service Developer Guide. - task_definition.container_definitions[].extra_hosts[]
Show child fields- task_definition.container_definitions[].extra_hosts[].hostname
The hostname to use in the /etc/hosts entry. - task_definition.container_definitions[].extra_hosts[].ip_address
The IP address to use in the /etc/hosts entry.
- task_definition.container_definitions[].firelens_configuration
The FireLens configuration for the container. This is used to specify and configure a log router for container logs. For more information, see Custom Log Routing in the Amazon Elastic Container Service Developer Guide. Show child fields- task_definition.container_definitions[].firelens_configuration.options
The options to use when configuring the log router. This field is optional and can be used to specify a custom configuration file or to add additional metadata, such as the task, task definition, cluster, and container instance details to the log event. If specified, the syntax to use is "options":{"enable-ecs-log-metadata":"true|false","config-file-type:"s3|file","config-file-value":"arn:aws:s3:::mybucket/fluent.conf|filepath"}. For more information, see Creating a task definition that uses a FireLens configuration in the Amazon Elastic Container Service Developer Guide. Tasks hosted on Fargate only support the file configuration file type. - task_definition.container_definitions[].firelens_configuration.type
The log router to use. The valid values are fluentd or fluentbit.
- task_definition.container_definitions[].health_check
The container health check command and associated configuration parameters for the container. This parameter maps to HealthCheck in the docker conainer create command and the HEALTHCHECK parameter of docker run. Show child fields- task_definition.container_definitions[].health_check.command[]
- task_definition.container_definitions[].health_check.interval
The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds. - task_definition.container_definitions[].health_check.retries
The number of times to retry a failed health check before the container is considered unhealthy. You may specify between 1 and 10 retries. The default value is 3. - task_definition.container_definitions[].health_check.start_period
The optional grace period to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You can specify between 0 and 300 seconds. By default, the startPeriod is off. If a health check succeeds within the startPeriod, then the container is considered healthy and any subsequent failures count toward the maximum number of retries. - task_definition.container_definitions[].health_check.timeout
The time period in seconds to wait for a health check to succeed before it is considered a failure. You may specify between 2 and 60 seconds. The default value is 5.
- task_definition.container_definitions[].hostname
The hostname to use for your container. This parameter maps to Hostname in thethe docker conainer create command and the --hostname option to docker run. The hostname parameter is not supported if you're using the awsvpc network mode. - task_definition.container_definitions[].image
The image used to start a container. This string is passed directly to the Docker daemon. By default, images in the Docker Hub registry are available. Other repositories are specified with either repository-url/image:tag or repository-url/image@digest . Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to Image in the docker conainer create command and the IMAGE parameter of docker run. -
When a new task starts, the Amazon ECS container agent pulls the latest version of the specified image and tag for the container to use. However, subsequent updates to a repository image aren't propagated to already running tasks. -
Images in Amazon ECR repositories can be specified by either using the full registry/repository:tag or registry/repository@digest. For example, 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>:latest or 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>@sha256:94afd1f2e64d908bc90dbca0035a5b567EXAMPLE. -
Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo). -
Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent). -
Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu). - task_definition.container_definitions[].interactive
When this parameter is true, you can deploy containerized applications that require stdin or a tty to be allocated. This parameter maps to OpenStdin in the docker conainer create command and the --interactive option to docker run. - task_definition.container_definitions[].links[]
- task_definition.container_definitions[].linux_parameters
Linux-specific modifications that are applied to the container, such as Linux kernel capabilities. For more information see KernelCapabilities. This parameter is not supported for Windows containers. Show child fields- task_definition.container_definitions[].linux_parameters.capabilities
The Linux capabilities for the container that are added to or dropped from the default configuration provided by Docker. For tasks that use the Fargate launch type, capabilities is supported for all platform versions but the add parameter is only supported if using platform version 1.4.0 or later. Show child fields- task_definition.container_definitions[].linux_parameters.capabilities.add[]
- task_definition.container_definitions[].linux_parameters.capabilities.drop[]
- task_definition.container_definitions[].linux_parameters.devices[]
Show child fields- task_definition.container_definitions[].linux_parameters.devices[].container_path
The path inside the container at which to expose the host device. - task_definition.container_definitions[].linux_parameters.devices[].host_path
The path for the device on the host container instance. - task_definition.container_definitions[].linux_parameters.devices[].permissions[]
- task_definition.container_definitions[].linux_parameters.init_process_enabled
Run an init process inside the container that forwards signals and reaps processes. This parameter maps to the --init option to docker run. This parameter requires version 1.25 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}' - task_definition.container_definitions[].linux_parameters.max_swap
The total amount of swap memory (in MiB) a container can use. This parameter will be translated to the --memory-swap option to docker run where the value would be the sum of the container memory plus the maxSwap value. If a maxSwap value of 0 is specified, the container will not use swap. Accepted values are 0 or any positive integer. If the maxSwap parameter is omitted, the container will use the swap configuration for the container instance it is running on. A maxSwap value must be set for the swappiness parameter to be used. If you're using tasks that use the Fargate launch type, the maxSwap parameter isn't supported. If you're using tasks on Amazon Linux 2023 the swappiness parameter isn't supported. - task_definition.container_definitions[].linux_parameters.shared_memory_size
The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run. If you are using tasks that use the Fargate launch type, the sharedMemorySize parameter is not supported. - task_definition.container_definitions[].linux_parameters.swappiness
This allows you to tune a container's memory swappiness behavior. A swappiness value of 0 will cause swapping to not happen unless absolutely necessary. A swappiness value of 100 will cause pages to be swapped very aggressively. Accepted values are whole numbers between 0 and 100. If the swappiness parameter is not specified, a default value of 60 is used. If a value is not specified for maxSwap then this parameter is ignored. This parameter maps to the --memory-swappiness option to docker run. If you're using tasks that use the Fargate launch type, the swappiness parameter isn't supported. If you're using tasks on Amazon Linux 2023 the swappiness parameter isn't supported. - task_definition.container_definitions[].linux_parameters.tmpfs[]
Show child fields- task_definition.container_definitions[].linux_parameters.tmpfs[].container_path
The absolute file path where the tmpfs volume is to be mounted. - task_definition.container_definitions[].linux_parameters.tmpfs[].mount_options[]
- task_definition.container_definitions[].linux_parameters.tmpfs[].size
The maximum size (in MiB) of the tmpfs volume.
- task_definition.container_definitions[].log_configuration
The log configuration specification for the container. This parameter maps to LogConfig in the docker conainer create command and the --log-driver option to docker run. By default, containers use the same logging driver that the Docker daemon uses. However the container can use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers may be available in future releases of the Amazon ECS container agent. This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}' The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide. Show child fields- task_definition.container_definitions[].log_configuration.log_driver
The log driver to use for the container. For tasks on Fargate, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Send Amazon ECS logs to CloudWatch in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log driver, see Send Amazon ECS logs to an Amazon Web Services service or Amazon Web Services Partner. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - task_definition.container_definitions[].log_configuration.options
The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}' - task_definition.container_definitions[].log_configuration.secret_options[]
Show child fields- task_definition.container_definitions[].log_configuration.secret_options[].name
The name of the secret. - task_definition.container_definitions[].log_configuration.secret_options[].value_from
The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- task_definition.container_definitions[].memory
The amount (in MiB) of memory to present to the container. If your container attempts to exceed the memory specified here, the container is killed. The total amount of memory reserved for all containers within a task must be lower than the task memory value, if one is specified. This parameter maps to Memory in thethe docker conainer create command and the --memory option to docker run. If using the Fargate launch type, this parameter is optional. If using the EC2 launch type, you must specify either a task-level memory value or a container-level memory value. If you specify both a container-level memory and memoryReservation value, memory must be greater than memoryReservation. If you specify memoryReservation, then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used. The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers. The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers. - task_definition.container_definitions[].memory_reservation
The soft limit (in MiB) of memory to reserve for the container. When system memory is under heavy contention, Docker attempts to keep the container memory to this soft limit. However, your container can consume more memory when it needs to, up to either the hard limit specified with the memory parameter (if applicable), or all of the available memory on the container instance, whichever comes first. This parameter maps to MemoryReservation in the the docker conainer create command and the --memory-reservation option to docker run. If a task-level memory value is not specified, you must specify a non-zero integer for one or both of memory or memoryReservation in a container definition. If you specify both, memory must be greater than memoryReservation. If you specify memoryReservation, then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used. For example, if your container normally uses 128 MiB of memory, but occasionally bursts to 256 MiB of memory for short periods of time, you can set a memoryReservation of 128 MiB, and a memory hard limit of 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory from the remaining resources on the container instance, but also allow the container to consume more memory resources when needed. The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers. The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers. - task_definition.container_definitions[].mount_points[]
Show child fields- task_definition.container_definitions[].mount_points[].container_path
The path on the container to mount the host volume at. - task_definition.container_definitions[].mount_points[].read_only
If this value is true, the container has read-only access to the volume. If this value is false, then the container can write to the volume. The default value is false. - task_definition.container_definitions[].mount_points[].source_volume
The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume.
- task_definition.container_definitions[].name
The name of a container. If you're linking multiple containers together in a task definition, the name of one container can be entered in the links of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to name in tthe docker conainer create command and the --name option to docker run. - task_definition.container_definitions[].port_mappings[]
Show child fields- task_definition.container_definitions[].port_mappings[].app_protocol
The application protocol that's used for the port mapping. This parameter only applies to Service Connect. We recommend that you set this parameter to be consistent with the protocol that your application uses. If you set this parameter, Amazon ECS adds protocol-specific connection handling to the Service Connect proxy. If you set this parameter, Amazon ECS adds protocol-specific telemetry in the Amazon ECS console and CloudWatch. If you don't set a value for this parameter, then TCP is used. However, Amazon ECS doesn't add protocol-specific telemetry for TCP. appProtocol is immutable in a Service Connect service. Updating this field requires a service deletion and redeployment. Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - task_definition.container_definitions[].port_mappings[].container_port
The port number on the container that's bound to the user-specified or automatically assigned host port. If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort. If you use containers in a task with the bridge network mode and you specify a container port and not a host port, your container automatically receives a host port in the ephemeral port range. For more information, see hostPort. Port mappings that are automatically assigned in this way do not count toward the 100 reserved ports limit of a container instance. - task_definition.container_definitions[].port_mappings[].container_port_range
The port number range on the container that's bound to the dynamically mapped host port range. The following rules apply when you specify a containerPortRange: -
You must use either the bridge network mode or the awsvpc network mode. -
This parameter is available for both the EC2 and Fargate launch types. -
This parameter is available for both the Linux and Windows operating systems. -
The container instance must have at least version 1.67.0 of the container agent and at least version 1.67.0-1 of the ecs-init package -
You can specify a maximum of 100 port ranges per container. -
You do not specify a hostPortRange. The value of the hostPortRange is set as follows: -
For containers in a task with the awsvpc network mode, the hostPortRange is set to the same value as the containerPortRange. This is a static mapping strategy. -
For containers in a task with the bridge network mode, the Amazon ECS agent finds open host ports from the default ephemeral range and passes it to docker to bind them to the container ports. -
The containerPortRange valid values are between 1 and 65535. -
A port can only be included in one port mapping per container. -
You cannot specify overlapping port ranges. -
The first port in the range must be less than last port in the range. -
Docker recommends that you turn off the docker-proxy in the Docker daemon config file when you have a large number of ports. For more information, see Issue #11185 on the Github website. For information about how to turn off the docker-proxy in the Docker daemon config file, see Docker daemon in the Amazon ECS Developer Guide. You can call DescribeTasks to view the hostPortRange which are the host ports that are bound to the container ports. - task_definition.container_definitions[].port_mappings[].host_port
The port number on the container instance to reserve for your container. If you specify a containerPortRange, leave this field empty and the value of the hostPort is set as follows: -
For containers in a task with the awsvpc network mode, the hostPort is set to the same value as the containerPort. This is a static mapping strategy. -
For containers in a task with the bridge network mode, the Amazon ECS agent finds open ports on the host and automatically binds them to the container ports. This is a dynamic mapping strategy. If you use containers in a task with the awsvpc or host network mode, the hostPort can either be left blank or set to the same value as the containerPort. If you use containers in a task with the bridge network mode, you can specify a non-reserved host port for your container port mapping, or you can omit the hostPort (or set it to 0) while specifying a containerPort and your container automatically receives a port in the ephemeral port range for your container instance operating system and Docker version. The default ephemeral port range for Docker version 1.6.0 and later is listed on the instance under /proc/sys/net/ipv4/ip_local_port_range. If this kernel parameter is unavailable, the default ephemeral port range from 49153 through 65535 (Linux) or 49152 through 65535 (Windows) is used. Do not attempt to specify a host port in the ephemeral port range as these are reserved for automatic assignment. In general, ports below 32768 are outside of the ephemeral port range. The default reserved ports are 22 for SSH, the Docker ports 2375 and 2376, and the Amazon ECS container agent ports 51678-51680. Any host port that was previously specified in a running task is also reserved while the task is running. That is, after a task stops, the host port is released. The current reserved ports are displayed in the remainingResources of DescribeContainerInstances output. A container instance can have up to 100 reserved ports at a time. This number includes the default reserved ports. Automatically assigned ports aren't included in the 100 reserved ports quota. - task_definition.container_definitions[].port_mappings[].name
The name that's used for the port mapping. This parameter only applies to Service Connect. This parameter is the name that you use in the serviceConnectConfiguration of a service. The name can include up to 64 characters. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - task_definition.container_definitions[].port_mappings[].protocol
The protocol used for the port mapping. Valid values are tcp and udp. The default is tcp. protocol is immutable in a Service Connect service. Updating this field requires a service deletion and redeployment.
- task_definition.container_definitions[].privileged
When this parameter is true, the container is given elevated privileges on the host container instance (similar to the root user). This parameter maps to Privileged in the the docker conainer create command and the --privileged option to docker run This parameter is not supported for Windows containers or tasks run on Fargate. - task_definition.container_definitions[].pseudo_terminal
When this parameter is true, a TTY is allocated. This parameter maps to Tty in tthe docker conainer create command and the --tty option to docker run. - task_definition.container_definitions[].readonly_root_filesystem
When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the docker conainer create command and the --read-only option to docker run. This parameter is not supported for Windows containers. - task_definition.container_definitions[].repository_credentials
The private repository authentication credentials to use. Show child fields- task_definition.container_definitions[].repository_credentials.credentials_parameter
The Amazon Resource Name (ARN) of the secret containing the private repository credentials. When you use the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same Region as the task that you're launching then you can use either the full ARN or the name of the secret. When you use the Amazon Web Services Management Console, you must specify the full ARN of the secret.
- task_definition.container_definitions[].resource_requirements[]
Show child fields- task_definition.container_definitions[].resource_requirements[].type
The type of resource to assign to a container. - task_definition.container_definitions[].resource_requirements[].value
The value for the specified resource type. When the type is GPU, the value is the number of physical GPUs the Amazon ECS container agent reserves for the container. The number of GPUs that's reserved for all containers in a task can't exceed the number of available GPUs on the container instance that the task is launched on. When the type is InferenceAccelerator, the value matches the deviceName for an InferenceAccelerator specified in a task definition.
- task_definition.container_definitions[].restart_policy
The restart policy for a container. When you set up a restart policy, Amazon ECS can restart the container without needing to replace the task. For more information, see Restart individual containers in Amazon ECS tasks with container restart policies in the Amazon Elastic Container Service Developer Guide. Show child fields- task_definition.container_definitions[].restart_policy.enabled
Specifies whether a restart policy is enabled for the container. - task_definition.container_definitions[].restart_policy.ignored_exit_codes[]
- task_definition.container_definitions[].restart_policy.restart_attempt_period
A period of time (in seconds) that the container must run for before a restart can be attempted. A container can be restarted only once every restartAttemptPeriod seconds. If a container isn't able to run for this time period and exits early, it will not be restarted. You can set a minimum restartAttemptPeriod of 60 seconds and a maximum restartAttemptPeriod of 1800 seconds. By default, a container must run for 300 seconds before it can be restarted.
- task_definition.container_definitions[].secrets[]
Show child fields- task_definition.container_definitions[].secrets[].name
The name of the secret. - task_definition.container_definitions[].secrets[].value_from
The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- task_definition.container_definitions[].start_timeout
Time duration (in seconds) to wait before giving up on resolving dependencies for a container. For example, you specify two containers in a task definition with containerA having a dependency on containerB reaching a COMPLETE, SUCCESS, or HEALTHY status. If a startTimeout value is specified for containerB and it doesn't reach the desired status within that time then containerA gives up and not start. This results in the task transitioning to a STOPPED state. When the ECS_CONTAINER_START_TIMEOUT container agent configuration variable is used, it's enforced independently from this start timeout value. For tasks using the Fargate launch type, the task or service requires the following platforms: For tasks using the EC2 launch type, your container instances require at least version 1.26.0 of the container agent to use a container start timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide. If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from 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. The valid values for Fargate are 2-120 seconds. - task_definition.container_definitions[].stop_timeout
Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own. For tasks using the Fargate launch type, the task or service requires the following platforms: The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used. For tasks that use the EC2 launch type, if the stopTimeout parameter isn't specified, the value set for the Amazon ECS container agent configuration variable ECS_CONTAINER_STOP_TIMEOUT is used. If neither the stopTimeout parameter or the ECS_CONTAINER_STOP_TIMEOUT agent configuration variable are set, then the default values of 30 seconds for Linux containers and 30 seconds on Windows containers are used. Your container instances require at least version 1.26.0 of the container agent to use a container stop timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide. If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from 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. The valid values are 2-120 seconds. - task_definition.container_definitions[].system_controls[]
Show child fields- task_definition.container_definitions[].system_controls[].namespace
The namespaced kernel parameter to set a value for. - task_definition.container_definitions[].system_controls[].value
The namespaced kernel parameter to set a value for. Valid IPC namespace values: "kernel.msgmax" | "kernel.msgmnb" | "kernel.msgmni" | "kernel.sem" | "kernel.shmall" | "kernel.shmmax" | "kernel.shmmni" | "kernel.shm_rmid_forced", and Sysctls that start with "fs.mqueue.*" Valid network namespace values: Sysctls that start with "net.*" All of these values are supported by Fargate.
- task_definition.container_definitions[].ulimits[]
Show child fields- task_definition.container_definitions[].ulimits[].hard_limit
The hard limit for the ulimit type. - task_definition.container_definitions[].ulimits[].name
The type of the ulimit. - task_definition.container_definitions[].ulimits[].soft_limit
The soft limit for the ulimit type.
- task_definition.container_definitions[].user
The user to use inside the container. This parameter maps to User in the docker conainer create command and the --user option to docker run. When running tasks using the host network mode, don't run containers using the root user (UID 0). We recommend using a non-root user for better security. You can specify the user using the following formats. If specifying a UID or GID, you must specify it as a positive integer. -
user -
user:group -
uid -
uid:gid -
user:gid -
uid:group This parameter is not supported for Windows containers. - task_definition.container_definitions[].volumes_from[]
Show child fields- task_definition.container_definitions[].volumes_from[].read_only
If this value is true, the container has read-only access to the volume. If this value is false, then the container can write to the volume. The default value is false. - task_definition.container_definitions[].volumes_from[].source_container
The name of another container within the same task definition to mount volumes from.
- task_definition.container_definitions[].working_directory
The working directory to run commands inside the container in. This parameter maps to WorkingDir in the docker conainer create command and the --workdir option to docker run.
- task_definition.cpu
The number of cpu units used by the task. If you use the EC2 launch type, this field is optional. Any value can be used. If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines your range of valid values for the memory parameter. If you use the EC2 launch type, this field is optional. Supported values are between 128 CPU units (0.125 vCPUs) and 10240 CPU units (10 vCPUs). The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate. -
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: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) -
4096 (4 vCPU) - Available memory values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) -
8192 (8 vCPU) - Available memory values: 16 GB and 60 GB in 4 GB increments This option requires Linux platform 1.4.0 or later. -
16384 (16vCPU) - Available memory values: 32GB and 120 GB in 8 GB increments This option requires Linux platform 1.4.0 or later. - task_definition.deregistered_at
The Unix timestamp for the time when the task definition was deregistered. - task_definition.ephemeral_storage
The ephemeral storage settings to use for tasks run with the task definition. Show child fields- task_definition.ephemeral_storage.size_in_gi_b
The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 20 GiB and the maximum supported value is 200 GiB.
- task_definition.execution_role_arn
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. For informationabout the required IAM roles for Amazon ECS, see IAM roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. - task_definition.family
The name of a family that this task definition is registered to. Up to 255 characters are allowed. Letters (both uppercase and lowercase letters), 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. - task_definition.inference_accelerators[]
Show child fields- task_definition.inference_accelerators[].device_name
The Elastic Inference accelerator device name. The deviceName must also be referenced in a container definition as a ResourceRequirement. - task_definition.inference_accelerators[].device_type
The Elastic Inference accelerator type to use.
- task_definition.ipc_mode
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. If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace expose. 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 run on Fargate. - task_definition.memory
The amount (in MiB) of memory used by the task. If your tasks runs on Amazon EC2 instances, you must specify either a task-level memory value or a container-level memory value. This field is optional and any value can be used. If a task-level memory value is specified, the container-level memory value is optional. For more information regarding container-level memory and memory reservation, see ContainerDefinition. If your tasks runs on Fargate, this field is required. You must use one of the following values. The value you choose 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) -
Between 16 GB and 60 GB in 4 GB increments - Available cpu values: 8192 (8 vCPU) This option requires Linux platform 1.4.0 or later. -
Between 32GB and 120 GB in 8 GB increments - Available cpu values: 16384 (16 vCPU) This option requires Linux platform 1.4.0 or later. - task_definition.network_mode
The Docker networking mode to use for the containers in the task. The valid values are none, bridge, awsvpc, and host. If no network mode is specified, the default is bridge. For Amazon ECS tasks on Fargate, the awsvpc network mode is required. For Amazon ECS tasks on Amazon EC2 Linux instances, any network mode can be used. For Amazon ECS tasks on Amazon EC2 Windows instances, <default> or awsvpc 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. When using the host network mode, you should not run containers using the root user (UID 0). It is considered best practice to use a non-root user. 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. 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. - task_definition.pid_mode
The process namespace to use for the containers in the task. The valid values are host or task. On Fargate for Linux containers, the only valid value is task. For example, monitoring sidecars might need pidMode to access information about other containers running in the same task. If host is specified, 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 each container. If the host PID mode is used, there's a heightened risk of undesired process namespace exposure. This parameter is not supported for Windows containers. This parameter is only supported for tasks that are hosted on Fargate if the tasks are using platform version 1.4.0 or later (Linux). This isn't supported for Windows containers on Fargate. - task_definition.placement_constraints[]
Show child fields- task_definition.placement_constraints[].expression
A cluster query language expression to apply to the constraint. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - task_definition.placement_constraints[].type
The type of constraint. The MemberOf constraint restricts selection to be from a group of valid candidates.
- task_definition.proxy_configuration
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 use a proxy configuration. If your container instances are launched from the Amazon ECS optimized AMI version 20190301 or later, 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. Show child fields- task_definition.proxy_configuration.container_name
The name of the container that will serve as the App Mesh proxy. - task_definition.proxy_configuration.properties[]
Show child fields- task_definition.proxy_configuration.properties[].name
The name of the key-value pair. For environment variables, this is the name of the environment variable. - task_definition.proxy_configuration.properties[].value
The value of the key-value pair. For environment variables, this is the value of the environment variable.
- task_definition.proxy_configuration.type
The proxy type. The only supported value is APPMESH.
- task_definition.registered_at
The Unix timestamp for the time when the task definition was registered. - task_definition.registered_by
The principal that registered the task definition. - task_definition.requires_attributes[]
Show child fields- task_definition.requires_attributes[].name
The name of the attribute. The name must contain between 1 and 128 characters. The name may contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), forward slashes (/), back slashes (\), or periods (.). - task_definition.requires_attributes[].target_id
The ID of the target. You can specify the short form ID for a resource or the full Amazon Resource Name (ARN). - task_definition.requires_attributes[].target_type
The type of the target to attach the attribute with. This parameter is required if you use the short form ID for a resource instead of the full ARN. - task_definition.requires_attributes[].value
The value of the attribute. The value must contain between 1 and 128 characters. It can contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), periods (.), at signs (@), forward slashes (/), back slashes (\), colons (:), or spaces. The value can't start or end with a space.
- task_definition.requires_compatibilities[]
- task_definition.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. This is even if you deregistered previous revisions in this family. - task_definition.runtime_platform
The operating system that your task definitions are running on. A platform family is specified only for tasks using the Fargate launch type. When you specify a task in a service, this value must match the runtimePlatform value of the service. Show child fields- task_definition.runtime_platform.cpu_architecture
The CPU architecture. You can run your Linux tasks on an ARM-based platform by setting the value to ARM64. This option is available for tasks that run on Linux Amazon EC2 instance or Linux containers on Fargate. - task_definition.runtime_platform.operating_system_family
The operating system.
- task_definition.status
The status of the task definition. - task_definition.task_definition_arn
The full Amazon Resource Name (ARN) of the task definition. - task_definition.task_role_arn
The short name or full Amazon Resource Name (ARN) of the Identity and Access Management role that grants containers in the task permission to call Amazon Web Services APIs on your behalf. For informationabout the required IAM roles for Amazon ECS, see IAM roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. - task_definition.volumes[]
Show child fields- task_definition.volumes[].configured_at_launch
Indicates whether the volume should be configured at launch time. This is used to create Amazon EBS volumes for standalone tasks or tasks created as part of a service. Each task definition revision may only have one volume configured at launch in the volume configuration. To configure a volume at launch time, use this task definition revision and specify a volumeConfigurations object when calling the CreateService, UpdateService, RunTask or StartTask APIs. - task_definition.volumes[].docker_volume_configuration
This parameter is specified when you use Docker volumes. Windows containers only support the use of the local driver. To use bind mounts, specify the host parameter instead. Docker volumes aren't supported by tasks run on Fargate. Show child fields- task_definition.volumes[].docker_volume_configuration.autoprovision
If this value is true, the Docker volume is created if it doesn't already exist. This field is only used if the scope is shared. - task_definition.volumes[].docker_volume_configuration.driver
The Docker volume driver to use. The driver value must match the driver name provided by Docker because it is used for task placement. If the driver was installed using the Docker plugin CLI, use docker plugin ls to retrieve the driver name from your container instance. If the driver was installed using another method, use Docker plugin discovery to retrieve the driver name. This parameter maps to Driver in the docker conainer create command and the xxdriver option to docker volume create. - task_definition.volumes[].docker_volume_configuration.driver_opts
A map of Docker driver-specific options passed through. This parameter maps to DriverOpts in the docker create-volume command and the xxopt option to docker volume create. - task_definition.volumes[].docker_volume_configuration.labels
Custom metadata to add to your Docker volume. This parameter maps to Labels in the docker conainer create command and the xxlabel option to docker volume create. - task_definition.volumes[].docker_volume_configuration.scope
The scope for the Docker volume that determines its lifecycle. Docker volumes that are scoped to a task are automatically provisioned when the task starts and destroyed when the task stops. Docker volumes that are scoped as shared persist after the task stops.
- task_definition.volumes[].efs_volume_configuration
This parameter is specified when you use an Amazon Elastic File System file system for task storage. Show child fields- task_definition.volumes[].efs_volume_configuration.authorization_config
The authorization configuration details for the Amazon EFS file system. Show child fields- task_definition.volumes[].efs_volume_configuration.authorization_config.access_point_id
The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the EFSVolumeConfiguration must either be omitted or set to / which will enforce the path set on the EFS access point. If an access point is used, transit encryption must be on in the EFSVolumeConfiguration. For more information, see Working with Amazon EFS access points in the Amazon Elastic File System User Guide. - task_definition.volumes[].efs_volume_configuration.authorization_config.iam
Determines whether to use the Amazon ECS task role defined in a task definition when mounting the Amazon EFS file system. If it is turned on, transit encryption must be turned on in the EFSVolumeConfiguration. If this parameter is omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS access points in the Amazon Elastic Container Service Developer Guide.
- task_definition.volumes[].efs_volume_configuration.file_system_id
The Amazon EFS file system ID to use. - task_definition.volumes[].efs_volume_configuration.root_directory
The directory within the Amazon EFS file system to mount as the root directory inside the host. If this parameter is omitted, the root of the Amazon EFS volume will be used. Specifying / will have the same effect as omitting this parameter. If an EFS access point is specified in the authorizationConfig, the root directory parameter must either be omitted or set to / which will enforce the path set on the EFS access point. - task_definition.volumes[].efs_volume_configuration.transit_encryption
Determines whether to use encryption for Amazon EFS data in transit between the Amazon ECS host and the Amazon EFS server. Transit encryption must be turned on if Amazon EFS IAM authorization is used. If this parameter is omitted, the default value of DISABLED is used. For more information, see Encrypting data in transit in the Amazon Elastic File System User Guide. - task_definition.volumes[].efs_volume_configuration.transit_encryption_port
The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you do not specify a transit encryption port, it will use the port selection strategy that the Amazon EFS mount helper uses. For more information, see EFS mount helper in the Amazon Elastic File System User Guide.
- task_definition.volumes[].fsx_windows_file_server_volume_configuration
This parameter is specified when you use Amazon FSx for Windows File Server file system for task storage. Show child fields- task_definition.volumes[].fsx_windows_file_server_volume_configuration.authorization_config
The authorization configuration details for the Amazon FSx for Windows File Server file system. Show child fields- task_definition.volumes[].fsx_windows_file_server_volume_configuration.authorization_config.credentials_parameter
The authorization credential option to use. The authorization credential options can be provided using either the Amazon Resource Name (ARN) of an Secrets Manager secret or SSM Parameter Store parameter. The ARN refers to the stored credentials. - task_definition.volumes[].fsx_windows_file_server_volume_configuration.authorization_config.domain
A fully qualified domain name hosted by an Directory Service Managed Microsoft AD (Active Directory) or self-hosted AD on Amazon EC2.
- task_definition.volumes[].fsx_windows_file_server_volume_configuration.file_system_id
The Amazon FSx for Windows File Server file system ID to use. - task_definition.volumes[].fsx_windows_file_server_volume_configuration.root_directory
The directory within the Amazon FSx for Windows File Server file system to mount as the root directory inside the host.
- task_definition.volumes[].host
This parameter is specified when you use bind mount host volumes. The contents of the host parameter determine whether your bind mount host volume persists on the host container instance and where it's stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data isn't guaranteed to persist after the containers that are associated with it stop running. Windows containers can mount whole directories on the same drive as $env:ProgramData. Windows containers can't mount directories on a different drive, and mount point can't be across drives. For example, you can mount C:\my\path:C:\my\path and D:\:D:\, but not D:\my\path:C:\my\path or D:\:C:\my\path. Show child fields- task_definition.volumes[].host.source_path
When the host parameter is used, specify a sourcePath to declare the path on the host container instance that's presented to the container. If this parameter is empty, then the Docker daemon has assigned a host path for you. If the host parameter contains a sourcePath file location, then the data volume persists at the specified location on the host container instance until you delete it manually. If the sourcePath value doesn't exist on the host container instance, the Docker daemon creates it. If the location does exist, the contents of the source path folder are exported. If you're using the Fargate launch type, the sourcePath parameter is not supported.
- task_definition.volumes[].name
The name of the volume. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. When using a volume configured at launch, the name is required and must also be specified as the volume name in the ServiceVolumeConfiguration or TaskVolumeConfiguration parameter when creating your service or standalone task. For all other types of volumes, this name is referenced in the sourceVolume parameter of the mountPoints object in the container definition. When a volume is using the efsVolumeConfiguration, the name is required.
|