From 9a3a3f695c05f892116db66bf1c0a2f4da0f610e Mon Sep 17 00:00:00 2001
From: awstools
If you update the service with an empty string ""
for the namespace name,
+ *
If you update the cluster with an empty string ""
for the namespace name,
* the cluster configuration for Service Connect is removed. Note that the namespace will
* remain in Cloud Map and must be deleted separately.
For more information about Cloud Map, see Working
@@ -4049,13 +4049,11 @@ export type EnvironmentFileType = (typeof EnvironmentFileType)[keyof typeof Envi
/**
* @public
- * A list of files containing the environment variables to pass to a container. You can
- * specify up to ten environment files. The file must have a A list of files containing the environment variables to pass to a container. You can specify
+ * up to ten environment files. The file must have a .env
file
- * extension. Each line in an environment file should contain an environment variable in
+ * .env
file extension. Each
+ * line in an environment file should contain an environment variable in
* VARIABLE=VALUE
format. Lines beginning with #
are treated
- * as comments and are ignored. For more information about the environment variable file
- * syntax, see Declare default
- * environment variables in file.
If there are environment variables specified using the environment
* parameter in a container definition, they take precedence over the variables contained
* within an environment file. If multiple environment files are specified that contain the
@@ -4071,6 +4069,18 @@ export type EnvironmentFileType = (typeof EnvironmentFileType)[keyof typeof Envi
*
Windows platform version 1.0.0
or later.
Consider the following when using the Fargate launch type:
+ *The file is handled like a native Docker env-file.
+ *There is no support for shell escape handling.
+ *The container entry point interperts the VARIABLE
values.
You can view the health status of both individual containers and a task with the * DescribeTasks API operation or when viewing the task details in the console.
- *The health check is designed to make sure that your containers survive - * agent restarts, upgrades, or temporary unavailability.
+ *The health check is designed to make sure that your containers survive agent restarts, + * upgrades, or temporary unavailability.
*The following describes the possible healthStatus
values for a
* container:
- * UNKNOWN
-The container health check is being evaluated or
- * there's no container health check defined.
UNKNOWN
-The container health check is being evaluated,
+ * there's no container health check defined, or Amazon ECS doesn't have the health
+ * status of the container.
* The following describes the possible healthStatus
values for a task. The
- * container health check status of
- * non-essential containers don't have an effect on the health status of a task.
The following describes the possible healthStatus
values based on the
+ * container health checker status of essential containers in the task with the following
+ * priority order (high to low):
- * HEALTHY
-All essential containers within the task have
- * passed their health checks.
UNHEALTHY
-One or more essential containers have failed
+ * their health check.
*
- * UNHEALTHY
-One or more essential containers have failed
- * their health check.
UNKNOWN
-Any essential container running within the task is
+ * in an UNKNOWN
state and no other essential containers have an
+ * UNHEALTHY
state.
*
- * UNKNOWN
-The essential containers within the task are still
- * having their health checks evaluated, there are only nonessential containers
- * with health checks defined, or there are no container health checks
- * defined.
HEALTHY
-All essential containers within the task have
+ * passed their health checks.
+ * Consider the following task health example with 2 containers.
+ *If Container1 is UNHEALTHY
and Container2 is
+ * UNKNOWN
, the task health is UNHEALTHY
.
If Container1 is UNHEALTHY
and Container2 is
+ * HEALTHY
, the task health is UNHEALTHY
.
If Container1 is HEALTHY
and Container2 is UNKNOWN
,
+ * the task health is UNKNOWN
.
If Container1 is HEALTHY
and Container2 is HEALTHY
,
+ * the task health is HEALTHY
.
Consider the following task health example with 3 containers.
+ *If Container1 is UNHEALTHY
and Container2 is UNKNOWN
, and Container3
+ * is UNKNOWN
, the task health is UNHEALTHY
.
If Container1 is UNHEALTHY
and Container2 is UNKNOWN
, and Container3
+ * is HEALTHY
, the task health is UNHEALTHY
.
If Container1 is UNHEALTHY
and Container2 is HEALTHY
, and Container3
+ * is HEALTHY
, the task health is UNHEALTHY
.
If Container1 is HEALTHY
and Container2 is UNKNOWN
, and Container3
+ * is HEALTHY
, the task health is UNKNOWN
.
If Container1 is HEALTHY
and Container2 is UNKNOWN
,
+ * and Container3 is UNKNOWN
, the task health is
+ * UNKNOWN
.
If Container1 is HEALTHY
and Container2 is HEALTHY
,
+ * and Container3 is HEALTHY
, the task health is
+ * HEALTHY
.
If a task is run manually, and not as part of a service, the task will continue its @@ -4216,12 +4274,13 @@ export interface FirelensConfiguration { *
The following are notes about container health check support:
*When the Amazon ECS agent cannot connect to the Amazon ECS service, the
- * service reports the container as UNHEALTHY
.
When the Amazon ECS agent cannot connect to the Amazon ECS service, the service reports
+ * the container as UNHEALTHY
.
The health check statuses are the "last heard from" response from the Amazon ECS agent. There - * are no assumptions made about the status of the container health checks.
+ *The health check statuses are the "last heard from" response from the Amazon ECS + * agent. There are no assumptions made about the status of the container health + * checks.
*Container health checks require version 1.17.0 or greater of the Amazon ECS @@ -4725,8 +4784,8 @@ export interface PortMapping { *
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
+ * the hostPortRange
is set to the same value as the
+ * containerPortRange
. This is a static mapping
* strategy.
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
+ * the hostPortRange
is set to the same value as the
+ * containerPortRange
. This is a static mapping
* strategy.
The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace that's used when you create a service and don't specify\n\t\t\ta Service Connect configuration. The namespace name can include up to 1024 characters.\n\t\t\tThe name is case-sensitive. The name can't include hyphens (-), tilde (~), greater than\n\t\t\t(>), less than (<), or slash (/).
\nIf you enter an existing namespace name or ARN, then that namespace will be used.\n\t\t\tAny namespace type is supported. The namespace must be in this account and this Amazon Web Services\n\t\t\tRegion.
\nIf you enter a new name, a Cloud Map namespace will be created. Amazon ECS creates a\n\t\t\tCloud Map namespace with the \"API calls\" method of instance discovery only. This instance\n\t\t\tdiscovery method is the \"HTTP\" namespace type in the Command Line Interface. Other types of instance\n\t\t\tdiscovery aren't used by Service Connect.
\nIf you update the service with an empty string \"\"
for the namespace name,\n\t\t\tthe cluster configuration for Service Connect is removed. Note that the namespace will\n\t\t\tremain in Cloud Map and must be deleted separately.
For more information about Cloud Map, see Working\n\t\t\t\twith Services in the Cloud Map Developer Guide.
", + "smithy.api#documentation": "The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace that's used when you create a service and don't specify\n\t\t\ta Service Connect configuration. The namespace name can include up to 1024 characters.\n\t\t\tThe name is case-sensitive. The name can't include hyphens (-), tilde (~), greater than\n\t\t\t(>), less than (<), or slash (/).
\nIf you enter an existing namespace name or ARN, then that namespace will be used.\n\t\t\tAny namespace type is supported. The namespace must be in this account and this Amazon Web Services\n\t\t\tRegion.
\nIf you enter a new name, a Cloud Map namespace will be created. Amazon ECS creates a\n\t\t\tCloud Map namespace with the \"API calls\" method of instance discovery only. This instance\n\t\t\tdiscovery method is the \"HTTP\" namespace type in the Command Line Interface. Other types of instance\n\t\t\tdiscovery aren't used by Service Connect.
\nIf you update the cluster with an empty string \"\"
for the namespace name,\n\t\t\tthe cluster configuration for Service Connect is removed. Note that the namespace will\n\t\t\tremain in Cloud Map and must be deleted separately.
For more information about Cloud Map, see Working\n\t\t\t\twith Services in the Cloud Map Developer Guide.
", "smithy.api#required": {} } } @@ -3085,10 +3085,10 @@ "loadBalancers": [], "pendingCount": 0, "runningCount": 0, - "serviceArn": "arn:aws:ecs:us-east-1:012345678910:service/ecs-simple-service", + "serviceArn": "arn:aws:ecs:us-east-1:012345678910:service/default/ecs-simple-service", "serviceName": "ecs-simple-service", "status": "ACTIVE", - "taskDefinition": "arn:aws:ecs:us-east-1:012345678910:task-definition/hello_world:6" + "taskDefinition": "arn:aws:ecs:us-east-1:012345678910:task-definition/default/hello_world:6" } } } @@ -4422,9 +4422,7 @@ "title": "To describe a cluster", "documentation": "This example provides a description of the specified cluster in your default region.", "input": { - "clusters": [ - "default" - ] + "clusters": ["default"] }, "output": { "clusters": [ @@ -4510,9 +4508,7 @@ "documentation": "This example provides a description of the specified container instance in your default region, using the container instance UUID as an identifier.", "input": { "cluster": "default", - "containerInstances": [ - "f2756532-8f13-4d53-87c9-aed50dc94cd7" - ] + "containerInstances": ["f2756532-8f13-4d53-87c9-aed50dc94cd7"] }, "output": { "failures": [], @@ -4521,14 +4517,14 @@ "status": "ACTIVE", "registeredResources": [ { - "doubleValue": 0, + "doubleValue": 0.0, "type": "INTEGER", "longValue": 0, "integerValue": 2048, "name": "CPU" }, { - "doubleValue": 0, + "doubleValue": 0.0, "type": "INTEGER", "longValue": 0, "integerValue": 3768, @@ -4537,31 +4533,26 @@ { "name": "PORTS", "longValue": 0, - "doubleValue": 0, - "stringSetValue": [ - "2376", - "22", - "51678", - "2375" - ], + "doubleValue": 0.0, + "stringSetValue": ["2376", "22", "51678", "2375"], "type": "STRINGSET", "integerValue": 0 } ], "ec2InstanceId": "i-807f3249", "agentConnected": true, - "containerInstanceArn": "arn:aws:ecs:us-east-1:012345678910:container-instance/f2756532-8f13-4d53-87c9-aed50dc94cd7", + "containerInstanceArn": "arn:aws:ecs:us-east-1:012345678910:container-instance/default/f2756532-8f13-4d53-87c9-aed50dc94cd7", "pendingTasksCount": 0, "remainingResources": [ { - "doubleValue": 0, + "doubleValue": 0.0, "type": "INTEGER", "longValue": 0, "integerValue": 1948, "name": "CPU" }, { - "doubleValue": 0, + "doubleValue": 0.0, "type": "INTEGER", "longValue": 0, "integerValue": 3668, @@ -4570,14 +4561,8 @@ { "name": "PORTS", "longValue": 0, - "doubleValue": 0, - "stringSetValue": [ - "2376", - "22", - "80", - "51678", - "2375" - ], + "doubleValue": 0.0, + "stringSetValue": ["2376", "22", "80", "51678", "2375"], "type": "STRINGSET", "integerValue": 0 } @@ -4666,9 +4651,7 @@ "title": "To describe a service", "documentation": "This example provides descriptive information about the service named ``ecs-simple-service``.", "input": { - "services": [ - "ecs-simple-service" - ] + "services": ["ecs-simple-service"] }, "output": { "failures": [], @@ -4703,10 +4686,10 @@ "loadBalancers": [], "pendingCount": 0, "runningCount": 0, - "serviceArn": "arn:aws:ecs:us-east-1:012345678910:service/ecs-simple-service", + "serviceArn": "arn:aws:ecs:us-east-1:012345678910:service/default/ecs-simple-service", "serviceName": "ecs-simple-service", "status": "ACTIVE", - "taskDefinition": "arn:aws:ecs:us-east-1:012345678910:task-definition/hello_world:6" + "taskDefinition": "arn:aws:ecs:us-east-1:012345678910:task-definition/default/hello_world:6" } ] } @@ -4869,9 +4852,7 @@ { "mountPoints": [], "name": "wordpress", - "links": [ - "mysql" - ], + "links": ["mysql"], "image": "wordpress", "cpu": 10, "environment": [], @@ -5072,15 +5053,13 @@ "title": "To describe a task", "documentation": "This example provides a description of the specified task, using the task UUID as an identifier.", "input": { - "tasks": [ - "c5cba4eb-5dad-405e-96db-71ef8eefe6a8" - ] + "tasks": ["c5cba4eb-5dad-405e-96db-71ef8eefe6a8"] }, "output": { "failures": [], "tasks": [ { - "taskArn": "arn:aws:ecs:A list of files containing the environment variables to pass to a container. You can\n\t\t\tspecify up to ten environment files. The file must have a .env
file\n\t\t\textension. Each line in an environment file should contain an environment variable in\n\t\t\t\tVARIABLE=VALUE
format. Lines beginning with #
are treated\n\t\t\tas comments and are ignored. For more information about the environment variable file\n\t\t\tsyntax, see Declare default\n\t\t\t\tenvironment variables in file.
If there are environment variables specified using the environment
\n\t\t\tparameter in a container definition, they take precedence over the variables contained\n\t\t\twithin an environment file. If multiple environment files are specified that contain the\n\t\t\tsame variable, they're processed from the top down. We recommend that you use unique\n\t\t\tvariable names. For more information, see Specifying environment\n\t\t\t\tvariables in the Amazon Elastic Container Service Developer Guide.
You must use the following platforms for the Fargate launch type:
\nLinux platform version 1.4.0
or later.
Windows platform version 1.0.0
or later.
A list of files containing the environment variables to pass to a container. You can specify\n\t\t\tup to ten environment files. The file must have a .env
file extension. Each\n\t\t\tline in an environment file should contain an environment variable in\n\t\t\t\tVARIABLE=VALUE
format. Lines beginning with #
are treated\n\t\t\tas comments and are ignored.
If there are environment variables specified using the environment
\n\t\t\tparameter in a container definition, they take precedence over the variables contained\n\t\t\twithin an environment file. If multiple environment files are specified that contain the\n\t\t\tsame variable, they're processed from the top down. We recommend that you use unique\n\t\t\tvariable names. For more information, see Specifying environment\n\t\t\t\tvariables in the Amazon Elastic Container Service Developer Guide.
You must use the following platforms for the Fargate launch type:
\nLinux platform version 1.4.0
or later.
Windows platform version 1.0.0
or later.
Consider the following when using the Fargate launch type:
\nThe file is handled like a native Docker env-file.
\nThere is no support for shell escape handling.
\nThe container entry point interperts the VARIABLE
values.
An object representing a container health check. Health check parameters that are\n\t\t\tspecified in a container definition override any Docker health checks that exist in the\n\t\t\tcontainer image (such as those specified in a parent image or from the image's\n\t\t\tDockerfile). This configuration maps to the HEALTHCHECK
parameter of docker run.
The Amazon ECS container agent only monitors and reports on the health checks specified\n\t\t\t\tin the task definition. Amazon ECS does not monitor Docker health checks that are\n\t\t\t\tembedded in a container image and not specified in the container definition. Health\n\t\t\t\tcheck parameters that are specified in a container definition override any Docker\n\t\t\t\thealth checks that exist in the container image.
\nYou can view the health status of both individual containers and a task with the\n\t\t\tDescribeTasks API operation or when viewing the task details in the console.
\nThe health check is designed to make sure that your containers survive\n\t\t\tagent restarts, upgrades, or temporary unavailability.
\nThe following describes the possible healthStatus
values for a\n\t\t\tcontainer:
\n HEALTHY
-The container health check has passed\n\t\t\t\t\tsuccessfully.
\n UNHEALTHY
-The container health check has failed.
\n UNKNOWN
-The container health check is being evaluated or\n\t\t\t\t\tthere's no container health check defined.
The following describes the possible healthStatus
values for a task. The\n\t\t\tcontainer health check status of\n\t\t\tnon-essential containers don't have an effect on the health status of a task.
\n HEALTHY
-All essential containers within the task have\n\t\t\t\t\tpassed their health checks.
\n UNHEALTHY
-One or more essential containers have failed\n\t\t\t\t\ttheir health check.
\n UNKNOWN
-The essential containers within the task are still\n\t\t\t\t\thaving their health checks evaluated, there are only nonessential containers\n\t\t\t\t\twith health checks defined, or there are no container health checks\n\t\t\t\t\tdefined.
If a task is run manually, and not as part of a service, the task will continue its\n\t\t\tlifecycle regardless of its health status. For tasks that are part of a service, if the\n\t\t\ttask reports as unhealthy then the task will be stopped and the service scheduler will\n\t\t\treplace it.
\nThe following are notes about container health check support:
\nWhen the Amazon ECS agent cannot connect to the Amazon ECS service, the\n\t\t\t\t\tservice reports the container as UNHEALTHY
.
The health check statuses are the \"last heard from\" response from the Amazon ECS agent. There\n\t\t\t\t\tare no assumptions made about the status of the container health checks.
\nContainer health checks require version 1.17.0 or greater of the Amazon ECS\n\t\t\t\t\tcontainer agent. For more information, see Updating the\n\t\t\t\t\t\tAmazon ECS container agent.
\nContainer health checks are supported for Fargate tasks if\n\t\t\t\t\tyou're using platform version 1.1.0
or greater. For more\n\t\t\t\t\tinformation, see Fargate\n\t\t\t\t\t\tplatform versions.
Container health checks aren't supported for tasks that are part of a service\n\t\t\t\t\tthat's configured to use a Classic Load Balancer.
\nAn object representing a container health check. Health check parameters that are\n\t\t\tspecified in a container definition override any Docker health checks that exist in the\n\t\t\tcontainer image (such as those specified in a parent image or from the image's\n\t\t\tDockerfile). This configuration maps to the HEALTHCHECK
parameter of docker run.
The Amazon ECS container agent only monitors and reports on the health checks specified\n\t\t\t\tin the task definition. Amazon ECS does not monitor Docker health checks that are\n\t\t\t\tembedded in a container image and not specified in the container definition. Health\n\t\t\t\tcheck parameters that are specified in a container definition override any Docker\n\t\t\t\thealth checks that exist in the container image.
\nYou can view the health status of both individual containers and a task with the\n\t\t\tDescribeTasks API operation or when viewing the task details in the console.
\nThe health check is designed to make sure that your containers survive agent restarts,\n\t\t\tupgrades, or temporary unavailability.
\nThe following describes the possible healthStatus
values for a\n\t\t\tcontainer:
\n HEALTHY
-The container health check has passed\n\t\t\t\t\tsuccessfully.
\n UNHEALTHY
-The container health check has failed.
\n UNKNOWN
-The container health check is being evaluated,\n\t\t\t\t\tthere's no container health check defined, or Amazon ECS doesn't have the health\n\t\t\t\t\tstatus of the container.
The following describes the possible healthStatus
values based on the\n\t\t\tcontainer health checker status of essential containers in the task with the following\n\t\t\tpriority order (high to low):
\n UNHEALTHY
-One or more essential containers have failed\n\t\t\t\t\ttheir health check.
\n UNKNOWN
-Any essential container running within the task is\n\t\t\t\t\tin an UNKNOWN
state and no other essential containers have an\n\t\t\t\t\t\tUNHEALTHY
state.
\n HEALTHY
-All essential containers within the task have\n\t\t\t\t\tpassed their health checks.
Consider the following task health example with 2 containers.
\nIf Container1 is UNHEALTHY
and Container2 is\n\t\t\t\t\tUNKNOWN
, the task health is UNHEALTHY
.
If Container1 is UNHEALTHY
and Container2 is\n\t\t\t\t\tHEALTHY
, the task health is UNHEALTHY
.
If Container1 is HEALTHY
and Container2 is UNKNOWN
,\n\t\t\t\t\tthe task health is UNKNOWN
.
If Container1 is HEALTHY
and Container2 is HEALTHY
,\n\t\t\t\t\tthe task health is HEALTHY
.
Consider the following task health example with 3 containers.
\nIf Container1 is UNHEALTHY
and Container2 is UNKNOWN
, and Container3\n\t\t\t\t\tis UNKNOWN
, the task health is UNHEALTHY
.
If Container1 is UNHEALTHY
and Container2 is UNKNOWN
, and Container3\n\t\t\t\t\tis HEALTHY
, the task health is UNHEALTHY
.
If Container1 is UNHEALTHY
and Container2 is HEALTHY
, and Container3\n\t\t\t\t\tis HEALTHY
, the task health is UNHEALTHY
.
If Container1 is HEALTHY
and Container2 is UNKNOWN
, and Container3\n\t\t\t\t\tis HEALTHY
, the task health is UNKNOWN
.
If Container1 is HEALTHY
and Container2 is UNKNOWN
,\n\t\t\t\t\tand Container3 is UNKNOWN
, the task health is\n\t\t\t\t\tUNKNOWN
.
If Container1 is HEALTHY
and Container2 is HEALTHY
,\n\t\t\t\t\tand Container3 is HEALTHY
, the task health is\n\t\t\t\t\tHEALTHY
.
If a task is run manually, and not as part of a service, the task will continue its\n\t\t\tlifecycle regardless of its health status. For tasks that are part of a service, if the\n\t\t\ttask reports as unhealthy then the task will be stopped and the service scheduler will\n\t\t\treplace it.
\nThe following are notes about container health check support:
\nWhen the Amazon ECS agent cannot connect to the Amazon ECS service, the service reports\n\t\t\t\t\tthe container as UNHEALTHY
.
The health check statuses are the \"last heard from\" response from the Amazon ECS\n\t\t\t\t\tagent. There are no assumptions made about the status of the container health\n\t\t\t\t\tchecks.
\nContainer health checks require version 1.17.0 or greater of the Amazon ECS\n\t\t\t\t\tcontainer agent. For more information, see Updating the\n\t\t\t\t\t\tAmazon ECS container agent.
\nContainer health checks are supported for Fargate tasks if\n\t\t\t\t\tyou're using platform version 1.1.0
or greater. For more\n\t\t\t\t\tinformation, see Fargate\n\t\t\t\t\t\tplatform versions.
Container health checks aren't supported for tasks that are part of a service\n\t\t\t\t\tthat's configured to use a Classic Load Balancer.
\nThe port number range on the container that's bound to the dynamically mapped host port\n\t\t\trange.
\nThe following rules apply when you specify a containerPortRange
:
You must use either the bridge
network mode or the awsvpc
\n\t\t\t\t\tnetwork mode.
This parameter is available for both the EC2 and Fargate launch types.
\nThis parameter is available for both the Linux and Windows operating systems.
\nThe container instance must have at least version 1.67.0 of the container agent\n\t\t\t\t\tand at least version 1.67.0-1 of the ecs-init
package
You can specify a maximum of 100 port ranges per container.
\nYou do not specify a hostPortRange
. The value of the hostPortRange
is set\n\t\t\t\t\tas follows:
For containers in a task with the awsvpc
network mode,\n\t\t\t\t\t\t\tthe hostPort
is set to the same value as the\n\t\t\t\t\t\t\t\tcontainerPort
. This is a static mapping\n\t\t\t\t\t\t\tstrategy.
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\n\t\t\t\t\t65535.
A port can only be included in one port mapping per container.
\nYou cannot specify overlapping port ranges.
\nThe first port in the range must be less than last port in the range.
\nDocker recommends that you turn off the docker-proxy in the Docker daemon config file when you have a large number of ports.
\nFor more information, see Issue #11185 on the Github website.
\nFor information about how to turn off the docker-proxy in the Docker daemon config file, see Docker daemon in the Amazon ECS Developer Guide.
\nYou can call \n DescribeTasks
\n to view the hostPortRange
which\n\t\t\tare the host ports that are bound to the container ports.
The port number range on the container that's bound to the dynamically mapped host port\n\t\t\trange.
\nThe following rules apply when you specify a containerPortRange
:
You must use either the bridge
network mode or the awsvpc
\n\t\t\t\t\tnetwork mode.
This parameter is available for both the EC2 and Fargate launch types.
\nThis parameter is available for both the Linux and Windows operating systems.
\nThe container instance must have at least version 1.67.0 of the container agent\n\t\t\t\t\tand at least version 1.67.0-1 of the ecs-init
package
You can specify a maximum of 100 port ranges per container.
\nYou do not specify a hostPortRange
. The value of the hostPortRange
is set\n\t\t\t\t\tas follows:
For containers in a task with the awsvpc
network mode,\n\t\t\t\t\t\t\tthe hostPortRange
is set to the same value as the\n\t\t\t\t\t\t\t\tcontainerPortRange
. This is a static mapping\n\t\t\t\t\t\t\tstrategy.
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\n\t\t\t\t\t65535.
A port can only be included in one port mapping per container.
\nYou cannot specify overlapping port ranges.
\nThe first port in the range must be less than last port in the range.
\nDocker recommends that you turn off the docker-proxy in the Docker daemon config file when you have a large number of ports.
\nFor more information, see Issue #11185 on the Github website.
\nFor information about how to turn off the docker-proxy in the Docker daemon config file, see Docker daemon in the Amazon ECS Developer Guide.
\nYou can call \n DescribeTasks
\n to view the hostPortRange
which\n\t\t\tare the host ports that are bound to the container ports.
The port number range on the container that's bound to the dynamically mapped host port\n\t\t\trange.
\nThe following rules apply when you specify a containerPortRange
:
You must use either the bridge
network mode or the awsvpc
\n\t\t\t\t\tnetwork mode.
This parameter is available for both the EC2 and Fargate launch types.
\nThis parameter is available for both the Linux and Windows operating systems.
\nThe container instance must have at least version 1.67.0 of the container agent\n\t\t\t\t\tand at least version 1.67.0-1 of the ecs-init
package
You can specify a maximum of 100 port ranges per container.
\nYou do not specify a hostPortRange
. The value of the hostPortRange
is set\n\t\t\t\t\tas follows:
For containers in a task with the awsvpc
network mode,\n\t\t\t\t\t\t\tthe hostPort
is set to the same value as the\n\t\t\t\t\t\t\t\tcontainerPort
. This is a static mapping\n\t\t\t\t\t\t\tstrategy.
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\n\t\t\t\t\t65535.
A port can only be included in one port mapping per container.
\nYou cannot specify overlapping port ranges.
\nThe first port in the range must be less than last port in the range.
\nDocker recommends that you turn off the docker-proxy in the Docker daemon config file when you have a large number of ports.
\nFor more information, see Issue #11185 on the Github website.
\nFor information about how to turn off the docker-proxy in the Docker daemon config file, see Docker daemon in the Amazon ECS Developer Guide.
\nYou can call \n DescribeTasks
\n to view the hostPortRange
which\n\t\t\tare the host ports that are bound to the container ports.
The port number range on the container that's bound to the dynamically mapped host port\n\t\t\trange.
\nThe following rules apply when you specify a containerPortRange
:
You must use either the bridge
network mode or the awsvpc
\n\t\t\t\t\tnetwork mode.
This parameter is available for both the EC2 and Fargate launch types.
\nThis parameter is available for both the Linux and Windows operating systems.
\nThe container instance must have at least version 1.67.0 of the container agent\n\t\t\t\t\tand at least version 1.67.0-1 of the ecs-init
package
You can specify a maximum of 100 port ranges per container.
\nYou do not specify a hostPortRange
. The value of the hostPortRange
is set\n\t\t\t\t\tas follows:
For containers in a task with the awsvpc
network mode,\n\t\t\t\t\t\t\tthe hostPortRange
is set to the same value as the\n\t\t\t\t\t\t\t\tcontainerPortRange
. This is a static mapping\n\t\t\t\t\t\t\tstrategy.
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\n\t\t\t\t\t65535.
A port can only be included in one port mapping per container.
\nYou cannot specify overlapping port ranges.
\nThe first port in the range must be less than last port in the range.
\nDocker recommends that you turn off the docker-proxy in the Docker daemon config file when you have a large number of ports.
\nFor more information, see Issue #11185 on the Github website.
\nFor information about how to turn off the docker-proxy in the Docker daemon config file, see Docker daemon in the Amazon ECS Developer Guide.
\nYou can call \n DescribeTasks
\n to view the hostPortRange
which\n\t\t\tare the host ports that are bound to the container ports.