You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Amazon ECS runs another copy of the task in the specified cluster. To update an existing
33
33
* service, see the <a>UpdateService</a> action.</p>
34
34
* <note>
35
-
* <p>Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. </p>
35
+
* <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
36
36
* </note>
37
37
* <p>In addition to maintaining the desired count of tasks in your service, you can
38
38
* optionally run your service behind one or more load balancers. The load balancers
* <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
108
108
* can specify only parameters that aren't controlled at the task set level. The only
109
109
* required parameter is the service name. You control your services using the <a>CreateTaskSet</a> operation. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
110
-
* <p>When the service scheduler launches new tasks, it determines task placement. For
111
-
* information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
112
-
* task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
110
+
* <p>When the service scheduler launches new tasks, it determines task placement. For information
111
+
* about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
112
+
* task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>
113
+
* </p>
114
+
* <p>Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. </p>
113
115
* @example
114
116
* Use a bare-bones client and the command you need to make an API call.
* types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
34
+
* <note>
35
+
* <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
36
+
* </note>
34
37
* <p>For information about the maximum number of task sets and otther quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
35
-
* service quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
38
+
* service quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
36
39
* @example
37
40
* Use a bare-bones client and the command you need to make an API call.
* <p>Starts a new task using the specified task definition.</p>
31
+
* <note>
32
+
* <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
33
+
* </note>
31
34
* <p>You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places
32
35
* tasks using placement constraints and placement strategies. For more information, see
33
36
* <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
34
37
* <p>Alternatively, you can use <a>StartTask</a> to use your own scheduler or
35
38
* place tasks manually on specific container instances.</p>
36
-
* <note>
37
-
* <p>Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. </p>
38
-
* </note>
39
+
* <p>Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. </p>
39
40
* <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or
40
41
* updating a service. For more infomation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
41
42
* <p>The Amazon ECS API follows an eventual consistency model. This is because of the
* <p>Starts a new task from the specified task definition on the specified container
31
31
* instance or instances.</p>
32
32
* <note>
33
-
* <p>Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. </p>
33
+
* <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
34
34
* </note>
35
+
* <p>Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. </p>
35
36
* <p>Alternatively, you can use <a>RunTask</a> to place tasks for you. For more
36
37
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
37
38
* <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or
* <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
33
+
* </note>
31
34
* <p>For services using the rolling update (<code>ECS</code>) you can update the desired
32
35
* count, deployment configuration, network configuration, load balancers, service
* <p>Fargate Spot infrastructure is available for use but a capacity provider
2610
2610
* strategy must be used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html">Fargate capacity providers</a> in the
2611
-
* <i>Amazon ECS User Guide for Fargate</i>.</p>
2611
+
* <i>Amazon ECS Developer Guide</i>.</p>
2612
2612
* </note>
2613
2613
* <p>The <code>EC2</code> launch type runs your tasks on Amazon EC2 instances registered to your
* versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
2639
+
* <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
* <p>If you do not use an Elastic Load Balancing, we recommend that you use the <code>startPeriod</code> in
2709
2708
* the task definition health check parameters. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_HealthCheck.html">Health
2710
2709
* check</a>.</p>
2711
-
* <p>If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you
2712
-
* can specify a health check grace period of up to
2713
-
* 2,147,483,647
2714
-
* seconds (about 69 years). During that time, the Amazon ECS service
2715
-
* scheduler ignores health check status. This grace period can prevent the service
2716
-
* scheduler from marking tasks as unhealthy and stopping them before they have time to
2717
-
* come up.</p>
2710
+
* <p>If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can
2711
+
* specify a health check grace period of up to 2,147,483,647 seconds (about 69 years).
2712
+
* During that time, the Amazon ECS service scheduler ignores health check status. This grace
2713
+
* period can prevent the service scheduler from marking tasks as unhealthy and stopping
* <p>Specifies whether to propagate the tags from the task definition to the task. If no
2813
2810
* value is specified, the tags aren't propagated. Tags can only be propagated to the task
2814
2811
* during task creation. To add tags to a task after task creation, use the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_TagResource.html">TagResource</a> API action.</p>
2812
+
* <p>You must set this to a value other than <code>NONE</code> when you use Cost Explorer. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/usage-reports.html">Amazon ECS usage reports</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
* parameter in a container definition, they take precedence over the variables contained
4478
4476
* within an environment file. If multiple environment files are specified that contain the
4479
4477
* same variable, they're processed from the top down. We recommend that you use unique
4480
-
* variable names. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html">Specifying environment
4481
-
* variables</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
4478
+
* variable names. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/use-environment-file.html">Use a file to pass environment variables to a container</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
4479
+
* <p>Environment variable files are objects in Amazon S3 and all Amazon S3 security considerations apply. </p>
4482
4480
* <p>You must use the following platforms for the Fargate launch type:</p>
* <p>The Linux capabilities for the container that are added to or dropped from the default
4786
-
* configuration provided by Docker. For more information about the default capabilities
4786
+
* <p>The Linux capabilities to add or remove from the default Docker configuration for a container defined in the task definition. For more information about the default capabilities
4787
4787
* and the non-default available capabilities, see <a href="https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities">Runtime privilege and Linux capabilities</a> in the <i>Docker run
4788
4788
* reference</i>. For more detailed information about these Linux capabilities,
4789
4789
* see the <a href="http://man7.org/linux/man-pages/man7/capabilities.7.html">capabilities(7)</a> Linux manual page.</p>
0 commit comments