@aws-sdk/client-ecs 3.171.0 → 3.173.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -3,6 +3,14 @@
3
3
  All notable changes to this project will be documented in this file.
4
4
  See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
5
5
 
6
+ # [3.173.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.172.0...v3.173.0) (2022-09-16)
7
+
8
+ **Note:** Version bump only for package @aws-sdk/client-ecs
9
+
10
+
11
+
12
+
13
+
6
14
  # [3.171.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.170.0...v3.171.0) (2022-09-14)
7
15
 
8
16
  **Note:** Version bump only for package @aws-sdk/client-ecs
@@ -175,36 +175,8 @@ export declare class ECS extends ECSClient {
175
175
  * <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
176
176
  * can specify only parameters that aren't controlled at the task set level. The only
177
177
  * 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>
178
- * <p>When the service scheduler launches new tasks, it determines task placement in your
179
- * cluster using the following logic:</p>
180
- * <ul>
181
- * <li>
182
- * <p>Determine which of the container instances in your cluster can support the
183
- * task definition of your service. For example, they have the required CPU,
184
- * memory, ports, and container instance attributes.</p>
185
- * </li>
186
- * <li>
187
- * <p>By default, the service scheduler attempts to balance tasks across
188
- * Availability Zones in this manner. This is the case even if you can choose a
189
- * different placement strategy with the <code>placementStrategy</code>
190
- * parameter.</p>
191
- * <ul>
192
- * <li>
193
- * <p>Sort the valid container instances, giving priority to instances that
194
- * have the fewest number of running tasks for this service in their
195
- * respective Availability Zone. For example, if zone A has one running
196
- * service task and zones B and C each have zero, valid container instances
197
- * in either zone B or C are considered optimal for placement.</p>
198
- * </li>
199
- * <li>
200
- * <p>Place the new service task on a valid container instance in an optimal
201
- * Availability Zone based on the previous steps, favoring container
202
- * instances with the fewest number of running tasks for this
203
- * service.</p>
204
- * </li>
205
- * </ul>
206
- * </li>
207
- * </ul>
178
+ * <p>When the service scheduler launches new tasks, it determines task placement. For information
179
+ * 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>
208
180
  */
209
181
  createService(args: CreateServiceCommandInput, options?: __HttpHandlerOptions): Promise<CreateServiceCommandOutput>;
210
182
  createService(args: CreateServiceCommandInput, cb: (err: any, data?: CreateServiceCommandOutput) => void): void;
@@ -84,36 +84,8 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
84
84
  * <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
85
85
  * can specify only parameters that aren't controlled at the task set level. The only
86
86
  * 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>
87
- * <p>When the service scheduler launches new tasks, it determines task placement in your
88
- * cluster using the following logic:</p>
89
- * <ul>
90
- * <li>
91
- * <p>Determine which of the container instances in your cluster can support the
92
- * task definition of your service. For example, they have the required CPU,
93
- * memory, ports, and container instance attributes.</p>
94
- * </li>
95
- * <li>
96
- * <p>By default, the service scheduler attempts to balance tasks across
97
- * Availability Zones in this manner. This is the case even if you can choose a
98
- * different placement strategy with the <code>placementStrategy</code>
99
- * parameter.</p>
100
- * <ul>
101
- * <li>
102
- * <p>Sort the valid container instances, giving priority to instances that
103
- * have the fewest number of running tasks for this service in their
104
- * respective Availability Zone. For example, if zone A has one running
105
- * service task and zones B and C each have zero, valid container instances
106
- * in either zone B or C are considered optimal for placement.</p>
107
- * </li>
108
- * <li>
109
- * <p>Place the new service task on a valid container instance in an optimal
110
- * Availability Zone based on the previous steps, favoring container
111
- * instances with the fewest number of running tasks for this
112
- * service.</p>
113
- * </li>
114
- * </ul>
115
- * </li>
116
- * </ul>
87
+ * <p>When the service scheduler launches new tasks, it determines task placement. For information
88
+ * 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>
117
89
  * @example
118
90
  * Use a bare-bones client and the command you need to make an API call.
119
91
  * ```javascript
@@ -3042,9 +3042,9 @@ export interface FirelensConfiguration {
3042
3042
  export interface HealthCheck {
3043
3043
  /**
3044
3044
  * <p>A string array representing the command that the container runs to determine if it is
3045
- * healthy. The string array must start with <code>CMD</code> to execute the command
3046
- * arguments directly, or <code>CMD-SHELL</code> to run the command with the container's
3047
- * default shell. </p>
3045
+ * healthy. The string array must start with <code>CMD</code> to run the command arguments
3046
+ * directly, or <code>CMD-SHELL</code> to run the command with the container's default
3047
+ * shell. </p>
3048
3048
  * <p> When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, enclose the list
3049
3049
  * of commands in brackets.</p>
3050
3050
  * <p>
@@ -3761,8 +3761,10 @@ export interface ContainerDefinition {
3761
3761
  * 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory
3762
3762
  * from the remaining resources on the container instance, but also allow the container to
3763
3763
  * consume more memory resources when needed.</p>
3764
- * <p>The Docker daemon reserves a minimum of 4 MiB of memory for a container. Therefore, we
3765
- * recommend that you specify fewer than 4 MiB of memory for your containers. </p>
3764
+ * <p>The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a
3765
+ * container. So, don't specify less than 6 MiB of memory for your containers. </p>
3766
+ * <p>The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a
3767
+ * container. So, don't specify less than 4 MiB of memory for your containers.</p>
3766
3768
  */
3767
3769
  memoryReservation?: number;
3768
3770
  /**
@@ -3903,7 +3905,7 @@ export interface ContainerDefinition {
3903
3905
  secrets?: Secret[];
3904
3906
  /**
3905
3907
  * <p>The dependencies defined for container startup and shutdown. A container can contain
3906
- * multiple dependencies. When a dependency is defined for container startup, for container
3908
+ * multiple dependencies on other containers in a task definition. When a dependency is defined for container startup, for container
3907
3909
  * shutdown it is reversed.</p>
3908
3910
  * <p>For tasks using the EC2 launch type, the container instances require at
3909
3911
  * least version 1.26.0 of the container agent to turn on container dependencies. However,
@@ -4409,7 +4411,7 @@ export declare enum OSFamily {
4409
4411
  }
4410
4412
  /**
4411
4413
  * <p>Information about the platform for the Amazon ECS service or task.</p>
4412
- * <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>
4414
+ * <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>
4413
4415
  */
4414
4416
  export interface RuntimePlatform {
4415
4417
  /**
@@ -4812,10 +4814,21 @@ export interface TaskDefinition {
4812
4814
  * <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>
4813
4815
  * </li>
4814
4816
  * <li>
4815
- * <p>2048 (2 vCPU) - Available <code>memory</code> values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
4817
+ * <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
4818
+ * </li>
4819
+ * <li>
4820
+ * <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
4821
+ * </li>
4822
+ * <li>
4823
+ * <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p>
4824
+ *
4825
+ * <p>This option requires Linux platform <code>1.4.0</code> or
4826
+ * later.</p>
4816
4827
  * </li>
4817
4828
  * <li>
4818
- * <p>4096 (4 vCPU) - Available <code>memory</code> values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
4829
+ * <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p>
4830
+ * <p>This option requires Linux platform <code>1.4.0</code> or
4831
+ * later.</p>
4819
4832
  * </li>
4820
4833
  * </ul>
4821
4834
  */
@@ -4846,6 +4859,16 @@ export interface TaskDefinition {
4846
4859
  * <li>
4847
4860
  * <p>Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available <code>cpu</code> values: 4096 (4 vCPU)</p>
4848
4861
  * </li>
4862
+ * <li>
4863
+ * <p>Between 16 GB and 60 GB in 4 GB increments - Available <code>cpu</code> values: 8192 (8 vCPU)</p>
4864
+ * <p>This option requires Linux platform <code>1.4.0</code> or
4865
+ * later.</p>
4866
+ * </li>
4867
+ * <li>
4868
+ * <p>Between 32GB and 120 GB in 8 GB increments - Available <code>cpu</code> values: 16384 (16 vCPU)</p>
4869
+ * <p>This option requires Linux platform <code>1.4.0</code> or
4870
+ * later.</p>
4871
+ * </li>
4849
4872
  * </ul>
4850
4873
  */
4851
4874
  memory?: string;
@@ -5552,10 +5575,21 @@ export interface Task {
5552
5575
  * <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>
5553
5576
  * </li>
5554
5577
  * <li>
5555
- * <p>2048 (2 vCPU) - Available <code>memory</code> values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
5578
+ * <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
5579
+ * </li>
5580
+ * <li>
5581
+ * <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
5582
+ * </li>
5583
+ * <li>
5584
+ * <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p>
5585
+ *
5586
+ * <p>This option requires Linux platform <code>1.4.0</code> or
5587
+ * later.</p>
5556
5588
  * </li>
5557
5589
  * <li>
5558
- * <p>4096 (4 vCPU) - Available <code>memory</code> values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
5590
+ * <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p>
5591
+ * <p>This option requires Linux platform <code>1.4.0</code> or
5592
+ * later.</p>
5559
5593
  * </li>
5560
5594
  * </ul>
5561
5595
  */
@@ -5640,6 +5674,16 @@ export interface Task {
5640
5674
  * <li>
5641
5675
  * <p>Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available <code>cpu</code> values: 4096 (4 vCPU)</p>
5642
5676
  * </li>
5677
+ * <li>
5678
+ * <p>Between 16 GB and 60 GB in 4 GB increments - Available <code>cpu</code> values: 8192 (8 vCPU)</p>
5679
+ * <p>This option requires Linux platform <code>1.4.0</code> or
5680
+ * later.</p>
5681
+ * </li>
5682
+ * <li>
5683
+ * <p>Between 32GB and 120 GB in 8 GB increments - Available <code>cpu</code> values: 16384 (16 vCPU)</p>
5684
+ * <p>This option requires Linux platform <code>1.4.0</code> or
5685
+ * later.</p>
5686
+ * </li>
5643
5687
  * </ul>
5644
5688
  */
5645
5689
  memory?: string;
@@ -6816,9 +6860,10 @@ export interface RegisterTaskDefinitionRequest {
6816
6860
  * <p>Task-level CPU and memory parameters are ignored for Windows containers. We
6817
6861
  * recommend specifying container-level resources for Windows containers.</p>
6818
6862
  * </note>
6819
- * <p>If you're using the EC2 launch type, this field is optional. Supported
6820
- * values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and
6821
- * <code>10240</code> CPU units (<code>10</code> vCPUs).</p>
6863
+ * <p>If you're using the EC2 launch type, this field is optional. Supported values
6864
+ * are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>10240</code>
6865
+ * CPU units (<code>10</code> vCPUs). If you do not specify a value, the parameter is
6866
+ * ignored.</p>
6822
6867
  * <p>If you're using the Fargate launch type, this field is required and you
6823
6868
  * must use one of the following values, which determines your range of supported values
6824
6869
  * for the <code>memory</code> parameter:</p>
@@ -6835,10 +6880,21 @@ export interface RegisterTaskDefinitionRequest {
6835
6880
  * <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>
6836
6881
  * </li>
6837
6882
  * <li>
6838
- * <p>2048 (2 vCPU) - Available <code>memory</code> values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
6883
+ * <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p>
6884
+ * </li>
6885
+ * <li>
6886
+ * <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
6887
+ * </li>
6888
+ * <li>
6889
+ * <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p>
6890
+ *
6891
+ * <p>This option requires Linux platform <code>1.4.0</code> or
6892
+ * later.</p>
6839
6893
  * </li>
6840
6894
  * <li>
6841
- * <p>4096 (4 vCPU) - Available <code>memory</code> values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p>
6895
+ * <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p>
6896
+ * <p>This option requires Linux platform <code>1.4.0</code> or
6897
+ * later.</p>
6842
6898
  * </li>
6843
6899
  * </ul>
6844
6900
  */
@@ -6875,6 +6931,16 @@ export interface RegisterTaskDefinitionRequest {
6875
6931
  * <li>
6876
6932
  * <p>Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available <code>cpu</code> values: 4096 (4 vCPU)</p>
6877
6933
  * </li>
6934
+ * <li>
6935
+ * <p>Between 16 GB and 60 GB in 4 GB increments - Available <code>cpu</code> values: 8192 (8 vCPU)</p>
6936
+ * <p>This option requires Linux platform <code>1.4.0</code> or
6937
+ * later.</p>
6938
+ * </li>
6939
+ * <li>
6940
+ * <p>Between 32GB and 120 GB in 8 GB increments - Available <code>cpu</code> values: 16384 (16 vCPU)</p>
6941
+ * <p>This option requires Linux platform <code>1.4.0</code> or
6942
+ * later.</p>
6943
+ * </li>
6878
6944
  * </ul>
6879
6945
  */
6880
6946
  memory?: string;
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-ecs",
3
3
  "description": "AWS SDK for JavaScript Ecs Client for Node.js, Browser and React Native",
4
- "version": "3.171.0",
4
+ "version": "3.173.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",