Skip to content

Commit 0da530b

Browse files
author
awstools
committed
docs(client-ecs): This release supports new task definition sizes.
1 parent 5c92d80 commit 0da530b

File tree

4 files changed

+1244
-936
lines changed

4 files changed

+1244
-936
lines changed

‎clients/client-ecs/src/ECS.ts

Lines changed: 2 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -418,36 +418,8 @@ export class ECS extends ECSClient {
418418
* <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
419419
* can specify only parameters that aren't controlled at the task set level. The only
420420
* 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>
421-
* <p>When the service scheduler launches new tasks, it determines task placement in your
422-
* cluster using the following logic:</p>
423-
* <ul>
424-
* <li>
425-
* <p>Determine which of the container instances in your cluster can support the
426-
* task definition of your service. For example, they have the required CPU,
427-
* memory, ports, and container instance attributes.</p>
428-
* </li>
429-
* <li>
430-
* <p>By default, the service scheduler attempts to balance tasks across
431-
* Availability Zones in this manner. This is the case even if you can choose a
432-
* different placement strategy with the <code>placementStrategy</code>
433-
* parameter.</p>
434-
* <ul>
435-
* <li>
436-
* <p>Sort the valid container instances, giving priority to instances that
437-
* have the fewest number of running tasks for this service in their
438-
* respective Availability Zone. For example, if zone A has one running
439-
* service task and zones B and C each have zero, valid container instances
440-
* in either zone B or C are considered optimal for placement.</p>
441-
* </li>
442-
* <li>
443-
* <p>Place the new service task on a valid container instance in an optimal
444-
* Availability Zone based on the previous steps, favoring container
445-
* instances with the fewest number of running tasks for this
446-
* service.</p>
447-
* </li>
448-
* </ul>
449-
* </li>
450-
* </ul>
421+
* <p>When the service scheduler launches new tasks, it determines task placement. For information
422+
* about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
451423
*/
452424
public createService(
453425
args: CreateServiceCommandInput,

‎clients/client-ecs/src/commands/CreateServiceCommand.ts

Lines changed: 2 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -105,36 +105,8 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
105105
* <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
106106
* can specify only parameters that aren't controlled at the task set level. The only
107107
* 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>
108-
* <p>When the service scheduler launches new tasks, it determines task placement in your
109-
* cluster using the following logic:</p>
110-
* <ul>
111-
* <li>
112-
* <p>Determine which of the container instances in your cluster can support the
113-
* task definition of your service. For example, they have the required CPU,
114-
* memory, ports, and container instance attributes.</p>
115-
* </li>
116-
* <li>
117-
* <p>By default, the service scheduler attempts to balance tasks across
118-
* Availability Zones in this manner. This is the case even if you can choose a
119-
* different placement strategy with the <code>placementStrategy</code>
120-
* parameter.</p>
121-
* <ul>
122-
* <li>
123-
* <p>Sort the valid container instances, giving priority to instances that
124-
* have the fewest number of running tasks for this service in their
125-
* respective Availability Zone. For example, if zone A has one running
126-
* service task and zones B and C each have zero, valid container instances
127-
* in either zone B or C are considered optimal for placement.</p>
128-
* </li>
129-
* <li>
130-
* <p>Place the new service task on a valid container instance in an optimal
131-
* Availability Zone based on the previous steps, favoring container
132-
* instances with the fewest number of running tasks for this
133-
* service.</p>
134-
* </li>
135-
* </ul>
136-
* </li>
137-
* </ul>
108+
* <p>When the service scheduler launches new tasks, it determines task placement. For information
109+
* about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
138110
* @example
139111
* Use a bare-bones client and the command you need to make an API call.
140112
* ```javascript

‎clients/client-ecs/src/models/models_0.ts

Lines changed: 82 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -3476,9 +3476,9 @@ export interface FirelensConfiguration {
34763476
export interface HealthCheck {
34773477
/**
34783478
* <p>A string array representing the command that the container runs to determine if it is
3479-
* healthy. The string array must start with <code>CMD</code> to execute the command
3480-
* arguments directly, or <code>CMD-SHELL</code> to run the command with the container's
3481-
* default shell. </p>
3479+
* healthy. The string array must start with <code>CMD</code> to run the command arguments
3480+
* directly, or <code>CMD-SHELL</code> to run the command with the container's default
3481+
* shell. </p>
34823482
* <p> When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, enclose the list
34833483
* of commands in brackets.</p>
34843484
* <p>
@@ -4246,8 +4246,10 @@ export interface ContainerDefinition {
42464246
* 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory
42474247
* from the remaining resources on the container instance, but also allow the container to
42484248
* consume more memory resources when needed.</p>
4249-
* <p>The Docker daemon reserves a minimum of 4 MiB of memory for a container. Therefore, we
4250-
* recommend that you specify fewer than 4 MiB of memory for your containers. </p>
4249+
* <p>The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a
4250+
* container. So, don't specify less than 6 MiB of memory for your containers. </p>
4251+
* <p>The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a
4252+
* container. So, don't specify less than 4 MiB of memory for your containers.</p>
42514253
*/
42524254
memoryReservation?: number;
42534255

@@ -4400,7 +4402,7 @@ export interface ContainerDefinition {
44004402

44014403
/**
44024404
* <p>The dependencies defined for container startup and shutdown. A container can contain
4403-
* multiple dependencies. When a dependency is defined for container startup, for container
4405+
* multiple dependencies on other containers in a task definition. When a dependency is defined for container startup, for container
44044406
* shutdown it is reversed.</p>
44054407
* <p>For tasks using the EC2 launch type, the container instances require at
44064408
* least version 1.26.0 of the container agent to turn on container dependencies. However,
@@ -4943,7 +4945,7 @@ export enum OSFamily {
49434945

49444946
/**
49454947
* <p>Information about the platform for the Amazon ECS service or task.</p>
4946-
* <p>For more informataion about <code>RuntimePlatform</code>, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#runtime-platform">RuntimePlatform</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
4948+
* <p>For more information about <code>RuntimePlatform</code>, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#runtime-platform">RuntimePlatform</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
49474949
*/
49484950
export interface RuntimePlatform {
49494951
/**
@@ -5389,10 +5391,21 @@ export interface TaskDefinition {
53895391
* <p>1024 (1 vCPU) - Available <code>memory</code> values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)</p>
53905392
* </li>
53915393
* <li>
5392-
* <p>2048 (2 vCPU) - Available <code>memory</code> values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
5394+
* <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
5395+
* </li>
5396+
* <li>
5397+
* <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
5398+
* </li>
5399+
* <li>
5400+
* <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p>
5401+
*
5402+
* <p>This option requires Linux platform <code>1.4.0</code> or
5403+
* later.</p>
53935404
* </li>
53945405
* <li>
5395-
* <p>4096 (4 vCPU) - Available <code>memory</code> values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
5406+
* <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p>
5407+
* <p>This option requires Linux platform <code>1.4.0</code> or
5408+
* later.</p>
53965409
* </li>
53975410
* </ul>
53985411
*/
@@ -5424,6 +5437,16 @@ export interface TaskDefinition {
54245437
* <li>
54255438
* <p>Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available <code>cpu</code> values: 4096 (4 vCPU)</p>
54265439
* </li>
5440+
* <li>
5441+
* <p>Between 16 GB and 60 GB in 4 GB increments - Available <code>cpu</code> values: 8192 (8 vCPU)</p>
5442+
* <p>This option requires Linux platform <code>1.4.0</code> or
5443+
* later.</p>
5444+
* </li>
5445+
* <li>
5446+
* <p>Between 32GB and 120 GB in 8 GB increments - Available <code>cpu</code> values: 16384 (16 vCPU)</p>
5447+
* <p>This option requires Linux platform <code>1.4.0</code> or
5448+
* later.</p>
5449+
* </li>
54275450
* </ul>
54285451
*/
54295452
memory?: string;
@@ -6235,10 +6258,21 @@ export interface Task {
62356258
* <p>1024 (1 vCPU) - Available <code>memory</code> values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)</p>
62366259
* </li>
62376260
* <li>
6238-
* <p>2048 (2 vCPU) - Available <code>memory</code> values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
6261+
* <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
6262+
* </li>
6263+
* <li>
6264+
* <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
6265+
* </li>
6266+
* <li>
6267+
* <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p>
6268+
*
6269+
* <p>This option requires Linux platform <code>1.4.0</code> or
6270+
* later.</p>
62396271
* </li>
62406272
* <li>
6241-
* <p>4096 (4 vCPU) - Available <code>memory</code> values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
6273+
* <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p>
6274+
* <p>This option requires Linux platform <code>1.4.0</code> or
6275+
* later.</p>
62426276
* </li>
62436277
* </ul>
62446278
*/
@@ -6333,6 +6367,16 @@ export interface Task {
63336367
* <li>
63346368
* <p>Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available <code>cpu</code> values: 4096 (4 vCPU)</p>
63356369
* </li>
6370+
* <li>
6371+
* <p>Between 16 GB and 60 GB in 4 GB increments - Available <code>cpu</code> values: 8192 (8 vCPU)</p>
6372+
* <p>This option requires Linux platform <code>1.4.0</code> or
6373+
* later.</p>
6374+
* </li>
6375+
* <li>
6376+
* <p>Between 32GB and 120 GB in 8 GB increments - Available <code>cpu</code> values: 16384 (16 vCPU)</p>
6377+
* <p>This option requires Linux platform <code>1.4.0</code> or
6378+
* later.</p>
6379+
* </li>
63366380
* </ul>
63376381
*/
63386382
memory?: string;
@@ -7676,9 +7720,10 @@ export interface RegisterTaskDefinitionRequest {
76767720
* <p>Task-level CPU and memory parameters are ignored for Windows containers. We
76777721
* recommend specifying container-level resources for Windows containers.</p>
76787722
* </note>
7679-
* <p>If you're using the EC2 launch type, this field is optional. Supported
7680-
* values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and
7681-
* <code>10240</code> CPU units (<code>10</code> vCPUs).</p>
7723+
* <p>If you're using the EC2 launch type, this field is optional. Supported values
7724+
* are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>10240</code>
7725+
* CPU units (<code>10</code> vCPUs). If you do not specify a value, the parameter is
7726+
* ignored.</p>
76827727
* <p>If you're using the Fargate launch type, this field is required and you
76837728
* must use one of the following values, which determines your range of supported values
76847729
* for the <code>memory</code> parameter:</p>
@@ -7695,10 +7740,21 @@ export interface RegisterTaskDefinitionRequest {
76957740
* <p>1024 (1 vCPU) - Available <code>memory</code> values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)</p>
76967741
* </li>
76977742
* <li>
7698-
* <p>2048 (2 vCPU) - Available <code>memory</code> values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
7743+
* <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
7744+
* </li>
7745+
* <li>
7746+
* <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
7747+
* </li>
7748+
* <li>
7749+
* <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p>
7750+
*
7751+
* <p>This option requires Linux platform <code>1.4.0</code> or
7752+
* later.</p>
76997753
* </li>
77007754
* <li>
7701-
* <p>4096 (4 vCPU) - Available <code>memory</code> values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
7755+
* <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p>
7756+
* <p>This option requires Linux platform <code>1.4.0</code> or
7757+
* later.</p>
77027758
* </li>
77037759
* </ul>
77047760
*/
@@ -7736,6 +7792,16 @@ export interface RegisterTaskDefinitionRequest {
77367792
* <li>
77377793
* <p>Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available <code>cpu</code> values: 4096 (4 vCPU)</p>
77387794
* </li>
7795+
* <li>
7796+
* <p>Between 16 GB and 60 GB in 4 GB increments - Available <code>cpu</code> values: 8192 (8 vCPU)</p>
7797+
* <p>This option requires Linux platform <code>1.4.0</code> or
7798+
* later.</p>
7799+
* </li>
7800+
* <li>
7801+
* <p>Between 32GB and 120 GB in 8 GB increments - Available <code>cpu</code> values: 16384 (16 vCPU)</p>
7802+
* <p>This option requires Linux platform <code>1.4.0</code> or
7803+
* later.</p>
7804+
* </li>
77397805
* </ul>
77407806
*/
77417807
memory?: string;

0 commit comments

Comments
 (0)