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
Copy file name to clipboardExpand all lines: clients/client-ecs/src/ECS.ts
+20-30Lines changed: 20 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -322,8 +322,7 @@ export class ECS extends ECSClient {
322
322
* required resources in other Amazon Web Services services on your behalf. However, if the IAM user
323
323
* that makes the call doesn't have permissions to create the service-linked role, it
324
324
* isn't created. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
325
-
* service-linked roles for Amazon ECS</a> in the
326
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
325
+
* service-linked roles for Amazon ECS</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
327
326
* </note>
328
327
*/
329
328
publiccreateCluster(
@@ -363,8 +362,7 @@ export class ECS extends ECSClient {
363
362
* <p>In addition to maintaining the desired count of tasks in your service, you can
364
363
* optionally run your service behind one or more load balancers. The load balancers
365
364
* distribute traffic across the tasks that are associated with the service. For more
366
-
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the
367
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
365
+
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
368
366
* <p>Tasks for services that don't use a load balancer are considered healthy if they're in
369
367
* the <code>RUNNING</code> state. Tasks for services that use a load balancer are
370
368
* considered healthy if they're in the <code>RUNNING</code> state and are reported as
@@ -377,8 +375,7 @@ export class ECS extends ECSClient {
377
375
* maintains your desired number of tasks across your cluster. By default, the
378
376
* service scheduler spreads tasks across Availability Zones. You can use task
379
377
* placement strategies and constraints to customize task placement decisions. For
380
-
* more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the
381
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
378
+
* more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
382
379
* </li>
383
380
* <li>
384
381
* <p>
@@ -388,8 +385,7 @@ export class ECS extends ECSClient {
388
385
* evaluates the task placement constraints for running tasks. It also stops tasks
389
386
* that don't meet the placement constraints. When using this strategy, you don't
390
387
* need to specify a desired number of tasks, a task placement strategy, or use
391
-
* Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the
392
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
388
+
* Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
393
389
* </li>
394
390
* </ul>
395
391
* <p>You can optionally specify a deployment configuration for your service. The deployment
@@ -433,8 +429,9 @@ export class ECS extends ECSClient {
433
429
* <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
434
430
* can specify only parameters that aren't controlled at the task set level. The only
435
431
* 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>
436
-
* <p>When the service scheduler launches new tasks, it determines task placement. For information
437
-
* 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>
432
+
* <p>When the service scheduler launches new tasks, it determines task placement. For
433
+
* information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
434
+
* task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
438
435
*/
439
436
publiccreateService(
440
437
args: CreateServiceCommandInput,
@@ -1265,8 +1262,7 @@ export class ECS extends ECSClient {
1265
1262
/**
1266
1263
* <p>Returns a list of container instances in a specified cluster. You can filter the
1267
1264
* results of a <code>ListContainerInstances</code> operation with cluster query language
1268
-
* statements inside the <code>filter</code> parameter. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-query-language.html">Cluster Query Language</a> in the
1269
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1265
+
* statements inside the <code>filter</code> parameter. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-query-language.html">Cluster Query Language</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1270
1266
*/
1271
1267
publiclistContainerInstances(
1272
1268
args: ListContainerInstancesCommandInput,
@@ -1328,11 +1324,11 @@ export class ECS extends ECSClient {
1328
1324
}
1329
1325
1330
1326
/**
1331
-
* <p>This operation lists all of the services that are associated with a Cloud Map namespace. This list
1332
-
* might include services in different clusters. In contrast, <code>ListServices</code> can
1333
-
* only list services in one cluster at a time. If you need to filter the list of
1334
-
* services in a single cluster by various parameters, use <code>ListServices</code>.
1335
-
* For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1327
+
* <p>This operation lists all of the services that are associated with a Cloud Map
1328
+
* namespace. This list might include services in different clusters. In contrast,
1329
+
* <code>ListServices</code> can only list services in one cluster at a time. If you
1330
+
* need to filter the list of services in a single cluster by various parameters, use
1331
+
* <code>ListServices</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1336
1332
*/
1337
1333
publiclistServicesByNamespace(
1338
1334
args: ListServicesByNamespaceCommandInput,
@@ -1590,8 +1586,7 @@ export class ECS extends ECSClient {
1590
1586
* <p>Create or update an attribute on an Amazon ECS resource. If the attribute doesn't exist,
1591
1587
* it's created. If the attribute exists, its value is replaced with the specified value.
1592
1588
* To delete an attribute, use <a>DeleteAttributes</a>. For more information,
1593
-
* see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes">Attributes</a> in the
1594
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1589
+
* see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes">Attributes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1595
1590
*/
1596
1591
publicputAttributes(
1597
1592
args: PutAttributesCommandInput,
@@ -1756,8 +1751,7 @@ export class ECS extends ECSClient {
1756
1751
* <p>Starts a new task using the specified task definition.</p>
1757
1752
* <p>You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places
1758
1753
* tasks using placement constraints and placement strategies. For more information, see
1759
-
* <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the
1760
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1754
+
* <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>
1761
1755
* <p>Alternatively, you can use <a>StartTask</a> to use your own scheduler or
1762
1756
* place tasks manually on specific container instances.</p>
1763
1757
* <p>The Amazon ECS API follows an eventual consistency model. This is because of the
@@ -1810,8 +1804,7 @@ export class ECS extends ECSClient {
1810
1804
* <p>Starts a new task from the specified task definition on the specified container
1811
1805
* instance or instances.</p>
1812
1806
* <p>Alternatively, you can use <a>RunTask</a> to place tasks for you. For more
1813
-
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the
1814
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
1807
+
* 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>
@@ -2146,8 +2139,7 @@ export class ECS extends ECSClient {
2146
2139
* using the Amazon ECS-optimized Amazon Linux 2 (arm64) AMI. To update the container agent,
2147
2140
* you can update the <code>ecs-init</code> package. This updates the agent. For more
2148
2141
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/agent-update-ecs-ami.html">Updating the
2149
-
* Amazon ECS container agent</a> in the
2150
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
2142
+
* Amazon ECS container agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
2151
2143
* </note>
2152
2144
* <note>
2153
2145
* <p>Agent updates with the <code>UpdateContainerAgent</code> API operation do not
@@ -2156,8 +2148,7 @@ export class ECS extends ECSClient {
2156
2148
* </note>
2157
2149
* <p>The <code>UpdateContainerAgent</code> API requires an Amazon ECS-optimized AMI or Amazon
2158
2150
* Linux AMI with the <code>ecs-init</code> service installed and running. For help
2159
-
* updating the Amazon ECS container agent on other operating systems, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html#manually_update_agent">Manually updating the Amazon ECS container agent</a> in the
2160
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
2151
+
* updating the Amazon ECS container agent on other operating systems, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html#manually_update_agent">Manually updating the Amazon ECS container agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
2161
2152
*/
2162
2153
publicupdateContainerAgent(
2163
2154
args: UpdateContainerAgentCommandInput,
@@ -2379,8 +2370,7 @@ export class ECS extends ECSClient {
2379
2370
* <p>You must have a service-linked role when you update any of the following service
2380
2371
* properties. If you specified a custom IAM role when you created the service, Amazon ECS
2381
2372
* automatically replaces the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_Service.html#ECS-Type-Service-roleArn">roleARN</a> associated with the service with the ARN of your
2382
-
* service-linked role. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Service-linked roles</a> in the
2383
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
2373
+
* service-linked role. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Service-linked roles</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
* <p>In addition to maintaining the desired count of tasks in your service, you can
37
37
* optionally run your service behind one or more load balancers. The load balancers
38
38
* distribute traffic across the tasks that are associated with the service. For more
39
-
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the
40
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
39
+
* information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
41
40
* <p>Tasks for services that don't use a load balancer are considered healthy if they're in
42
41
* the <code>RUNNING</code> state. Tasks for services that use a load balancer are
43
42
* considered healthy if they're in the <code>RUNNING</code> state and are reported as
* maintains your desired number of tasks across your cluster. By default, the
51
50
* service scheduler spreads tasks across Availability Zones. You can use task
52
51
* placement strategies and constraints to customize task placement decisions. For
53
-
* more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the
54
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
52
+
* more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
* evaluates the task placement constraints for running tasks. It also stops tasks
62
60
* that don't meet the placement constraints. When using this strategy, you don't
63
61
* need to specify a desired number of tasks, a task placement strategy, or use
64
-
* Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the
65
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
62
+
* Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
66
63
* </li>
67
64
* </ul>
68
65
* <p>You can optionally specify a deployment configuration for your service. The deployment
* <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
107
104
* can specify only parameters that aren't controlled at the task set level. The only
108
105
* 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>
109
-
* <p>When the service scheduler launches new tasks, it determines task placement. For information
110
-
* 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>
106
+
* <p>When the service scheduler launches new tasks, it determines task placement. For
107
+
* information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
108
+
* task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
111
109
* @example
112
110
* Use a bare-bones client and the command you need to make an API call.
* <p>Returns a list of container instances in a specified cluster. You can filter the
33
33
* results of a <code>ListContainerInstances</code> operation with cluster query language
34
-
* statements inside the <code>filter</code> parameter. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-query-language.html">Cluster Query Language</a> in the
35
-
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
34
+
* statements inside the <code>filter</code> parameter. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-query-language.html">Cluster Query Language</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
36
35
* @example
37
36
* Use a bare-bones client and the command you need to make an API call.
0 commit comments