@aws-sdk/client-ecs 3.693.0 → 3.695.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.
Files changed (71) hide show
  1. package/README.md +11 -12
  2. package/dist-cjs/index.js +4 -2
  3. package/dist-es/protocols/Aws_json1_1.js +2 -0
  4. package/dist-types/ECS.d.ts +11 -12
  5. package/dist-types/ECSClient.d.ts +11 -12
  6. package/dist-types/commands/CreateCapacityProviderCommand.d.ts +17 -22
  7. package/dist-types/commands/CreateClusterCommand.d.ts +17 -19
  8. package/dist-types/commands/CreateServiceCommand.d.ts +89 -80
  9. package/dist-types/commands/CreateTaskSetCommand.d.ts +15 -19
  10. package/dist-types/commands/DeleteAccountSettingCommand.d.ts +9 -12
  11. package/dist-types/commands/DeleteAttributesCommand.d.ts +2 -4
  12. package/dist-types/commands/DeleteCapacityProviderCommand.d.ts +17 -21
  13. package/dist-types/commands/DeleteClusterCommand.d.ts +23 -27
  14. package/dist-types/commands/DeleteServiceCommand.d.ts +30 -29
  15. package/dist-types/commands/DeleteTaskDefinitionsCommand.d.ts +23 -28
  16. package/dist-types/commands/DeleteTaskSetCommand.d.ts +14 -17
  17. package/dist-types/commands/DeregisterContainerInstanceCommand.d.ts +19 -22
  18. package/dist-types/commands/DeregisterTaskDefinitionCommand.d.ts +23 -26
  19. package/dist-types/commands/DescribeCapacityProvidersCommand.d.ts +8 -10
  20. package/dist-types/commands/DescribeClustersCommand.d.ts +8 -10
  21. package/dist-types/commands/DescribeContainerInstancesCommand.d.ts +10 -12
  22. package/dist-types/commands/DescribeServiceDeploymentsCommand.d.ts +9 -12
  23. package/dist-types/commands/DescribeServiceRevisionsCommand.d.ts +16 -12
  24. package/dist-types/commands/DescribeServicesCommand.d.ts +15 -10
  25. package/dist-types/commands/DescribeTaskDefinitionCommand.d.ts +13 -16
  26. package/dist-types/commands/DescribeTaskSetsCommand.d.ts +13 -17
  27. package/dist-types/commands/DescribeTasksCommand.d.ts +11 -13
  28. package/dist-types/commands/DiscoverPollEndpointCommand.d.ts +7 -8
  29. package/dist-types/commands/ExecuteCommandCommand.d.ts +19 -23
  30. package/dist-types/commands/GetTaskProtectionCommand.d.ts +8 -10
  31. package/dist-types/commands/ListAccountSettingsCommand.d.ts +8 -10
  32. package/dist-types/commands/ListAttributesCommand.d.ts +6 -8
  33. package/dist-types/commands/ListClustersCommand.d.ts +8 -10
  34. package/dist-types/commands/ListContainerInstancesCommand.d.ts +12 -13
  35. package/dist-types/commands/ListServiceDeploymentsCommand.d.ts +9 -12
  36. package/dist-types/commands/ListServicesByNamespaceCommand.d.ts +12 -15
  37. package/dist-types/commands/ListServicesCommand.d.ts +10 -12
  38. package/dist-types/commands/ListTagsForResourceCommand.d.ts +8 -10
  39. package/dist-types/commands/ListTaskDefinitionFamiliesCommand.d.ts +13 -17
  40. package/dist-types/commands/ListTaskDefinitionsCommand.d.ts +11 -13
  41. package/dist-types/commands/ListTasksCommand.d.ts +12 -15
  42. package/dist-types/commands/PutAccountSettingCommand.d.ts +11 -14
  43. package/dist-types/commands/PutAccountSettingDefaultCommand.d.ts +10 -12
  44. package/dist-types/commands/PutAttributesCommand.d.ts +7 -11
  45. package/dist-types/commands/PutClusterCapacityProvidersCommand.d.ts +24 -29
  46. package/dist-types/commands/RegisterContainerInstanceCommand.d.ts +10 -12
  47. package/dist-types/commands/RegisterTaskDefinitionCommand.d.ts +21 -23
  48. package/dist-types/commands/RunTaskCommand.d.ts +33 -37
  49. package/dist-types/commands/StartTaskCommand.d.ts +16 -16
  50. package/dist-types/commands/StopTaskCommand.d.ts +18 -22
  51. package/dist-types/commands/SubmitAttachmentStateChangesCommand.d.ts +8 -10
  52. package/dist-types/commands/SubmitContainerStateChangeCommand.d.ts +7 -8
  53. package/dist-types/commands/SubmitTaskStateChangeCommand.d.ts +8 -10
  54. package/dist-types/commands/TagResourceCommand.d.ts +11 -14
  55. package/dist-types/commands/UntagResourceCommand.d.ts +8 -10
  56. package/dist-types/commands/UpdateCapacityProviderCommand.d.ts +10 -11
  57. package/dist-types/commands/UpdateClusterCommand.d.ts +8 -10
  58. package/dist-types/commands/UpdateClusterSettingsCommand.d.ts +8 -10
  59. package/dist-types/commands/UpdateContainerAgentCommand.d.ts +33 -37
  60. package/dist-types/commands/UpdateContainerInstancesStateCommand.d.ts +42 -48
  61. package/dist-types/commands/UpdateServiceCommand.d.ts +105 -101
  62. package/dist-types/commands/UpdateServicePrimaryTaskSetCommand.d.ts +15 -20
  63. package/dist-types/commands/UpdateTaskProtectionCommand.d.ts +20 -25
  64. package/dist-types/commands/UpdateTaskSetCommand.d.ts +15 -19
  65. package/dist-types/index.d.ts +11 -12
  66. package/dist-types/models/models_0.d.ts +2860 -3324
  67. package/dist-types/models/models_1.d.ts +150 -152
  68. package/dist-types/ts3.4/commands/UpdateCapacityProviderCommand.d.ts +2 -4
  69. package/dist-types/ts3.4/models/models_0.d.ts +8 -3
  70. package/dist-types/ts3.4/models/models_1.d.ts +6 -0
  71. package/package.json +1 -1
@@ -1,6 +1,16 @@
1
1
  import { ExceptionOptionType as __ExceptionOptionType } from "@smithy/smithy-client";
2
2
  import { ECSServiceException as __BaseException } from "./ECSServiceException";
3
- import { CapacityProviderStrategyItem, Cluster, ClusterConfiguration, ClusterServiceConnectDefaultsRequest, ClusterSetting, ContainerInstance, ContainerInstanceStatus, DeploymentConfiguration, Failure, LoadBalancer, NetworkConfiguration, PlacementConstraint, PlacementStrategy, PropagateTags, ProtectedTask, Scale, Service, ServiceConnectConfiguration, ServiceRegistry, ServiceVolumeConfiguration, TaskSet } from "./models_0";
3
+ import { CapacityProvider, CapacityProviderStrategyItem, Cluster, ClusterConfiguration, ClusterServiceConnectDefaultsRequest, ClusterSetting, ContainerInstance, ContainerInstanceStatus, DeploymentConfiguration, Failure, LoadBalancer, NetworkConfiguration, PlacementConstraint, PlacementStrategy, PropagateTags, ProtectedTask, Scale, Service, ServiceConnectConfiguration, ServiceRegistry, ServiceVolumeConfiguration, TaskSet, VpcLatticeConfiguration } from "./models_0";
4
+ /**
5
+ * @public
6
+ */
7
+ export interface UpdateCapacityProviderResponse {
8
+ /**
9
+ * <p>Details about the capacity provider.</p>
10
+ * @public
11
+ */
12
+ capacityProvider?: CapacityProvider | undefined;
13
+ }
4
14
  /**
5
15
  * @public
6
16
  */
@@ -57,16 +67,14 @@ export interface UpdateClusterSettingsRequest {
57
67
  */
58
68
  cluster: string | undefined;
59
69
  /**
60
- * <p>The setting to use by default for a cluster. This parameter is used to turn on CloudWatch
61
- * Container Insights for a cluster. If this value is specified, it overrides the
62
- * <code>containerInsights</code> value set with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSetting.html">PutAccountSetting</a> or
63
- * <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSettingDefault.html">PutAccountSettingDefault</a>.</p>
70
+ * <p>The setting to use by default for a cluster. This parameter is used to turn on CloudWatch Container
71
+ * Insights for a cluster. If this value is specified, it overrides the <code>containerInsights</code>
72
+ * value set with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSetting.html">PutAccountSetting</a> or <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSettingDefault.html">PutAccountSettingDefault</a>.</p>
64
73
  * <important>
65
- * <p>Currently, if you delete an existing cluster that does not have Container Insights
66
- * turned on, and then create a new cluster with the same name with Container Insights
67
- * tuned on, Container Insights will not actually be turned on. If you want to preserve
68
- * the same name for your existing cluster and turn on Container Insights, you must
69
- * wait 7 days before you can re-create it.</p>
74
+ * <p>Currently, if you delete an existing cluster that does not have Container Insights turned on, and
75
+ * then create a new cluster with the same name with Container Insights tuned on, Container Insights
76
+ * will not actually be turned on. If you want to preserve the same name for your existing cluster and
77
+ * turn on Container Insights, you must wait 7 days before you can re-create it.</p>
70
78
  * </important>
71
79
  * @public
72
80
  */
@@ -83,10 +91,9 @@ export interface UpdateClusterSettingsResponse {
83
91
  cluster?: Cluster | undefined;
84
92
  }
85
93
  /**
86
- * <p>Amazon ECS can't determine the current version of the Amazon ECS container agent on the
87
- * container instance and doesn't have enough information to proceed with an update. This
88
- * could be because the agent running on the container instance is a previous or custom
89
- * version that doesn't use our version information.</p>
94
+ * <p>Amazon ECS can't determine the current version of the Amazon ECS container agent on the container instance and
95
+ * doesn't have enough information to proceed with an update. This could be because the agent running on
96
+ * the container instance is a previous or custom version that doesn't use our version information.</p>
90
97
  * @public
91
98
  */
92
99
  export declare class MissingVersionException extends __BaseException {
@@ -98,9 +105,9 @@ export declare class MissingVersionException extends __BaseException {
98
105
  constructor(opts: __ExceptionOptionType<MissingVersionException, __BaseException>);
99
106
  }
100
107
  /**
101
- * <p>There's no update available for this Amazon ECS container agent. This might be because the
102
- * agent is already running the latest version or because it's so old that there's no
103
- * update path to the current version.</p>
108
+ * <p>There's no update available for this Amazon ECS container agent. This might be because the agent is
109
+ * already running the latest version or because it's so old that there's no update path to the current
110
+ * version.</p>
104
111
  * @public
105
112
  */
106
113
  export declare class NoUpdateAvailableException extends __BaseException {
@@ -116,14 +123,14 @@ export declare class NoUpdateAvailableException extends __BaseException {
116
123
  */
117
124
  export interface UpdateContainerAgentRequest {
118
125
  /**
119
- * <p>The short name or full Amazon Resource Name (ARN) of the cluster that your container instance is
120
- * running on. If you do not specify a cluster, the default cluster is assumed.</p>
126
+ * <p>The short name or full Amazon Resource Name (ARN) of the cluster that your container instance is running on.
127
+ * If you do not specify a cluster, the default cluster is assumed.</p>
121
128
  * @public
122
129
  */
123
130
  cluster?: string | undefined;
124
131
  /**
125
- * <p>The container instance ID or full ARN entries for the container instance where you
126
- * would like to update the Amazon ECS container agent.</p>
132
+ * <p>The container instance ID or full ARN entries for the container instance where you would like to
133
+ * update the Amazon ECS container agent.</p>
127
134
  * @public
128
135
  */
129
136
  containerInstance: string | undefined;
@@ -143,8 +150,8 @@ export interface UpdateContainerAgentResponse {
143
150
  */
144
151
  export interface UpdateContainerInstancesStateRequest {
145
152
  /**
146
- * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the container instance to
147
- * update. If you do not specify a cluster, the default cluster is assumed.</p>
153
+ * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the container instance to update.
154
+ * If you do not specify a cluster, the default cluster is assumed.</p>
148
155
  * @public
149
156
  */
150
157
  cluster?: string | undefined;
@@ -154,12 +161,12 @@ export interface UpdateContainerInstancesStateRequest {
154
161
  */
155
162
  containerInstances: string[] | undefined;
156
163
  /**
157
- * <p>The container instance state to update the container instance with. The only valid
158
- * values for this action are <code>ACTIVE</code> and <code>DRAINING</code>. A container
159
- * instance can only be updated to <code>DRAINING</code> status once it has reached an
160
- * <code>ACTIVE</code> state. If a container instance is in <code>REGISTERING</code>,
161
- * <code>DEREGISTERING</code>, or <code>REGISTRATION_FAILED</code> state you can
162
- * describe the container instance but can't update the container instance state.</p>
164
+ * <p>The container instance state to update the container instance with. The only valid values for this
165
+ * action are <code>ACTIVE</code> and <code>DRAINING</code>. A container instance can only be updated to
166
+ * <code>DRAINING</code> status once it has reached an <code>ACTIVE</code> state. If a container
167
+ * instance is in <code>REGISTERING</code>, <code>DEREGISTERING</code>, or
168
+ * <code>REGISTRATION_FAILED</code> state you can describe the container instance but can't update the
169
+ * container instance state.</p>
163
170
  * @public
164
171
  */
165
172
  status: ContainerInstanceStatus | undefined;
@@ -195,48 +202,43 @@ export interface UpdateServiceRequest {
195
202
  */
196
203
  service: string | undefined;
197
204
  /**
198
- * <p>The number of instantiations of the task to place and keep running in your
199
- * service.</p>
205
+ * <p>The number of instantiations of the task to place and keep running in your service.</p>
200
206
  * @public
201
207
  */
202
208
  desiredCount?: number | undefined;
203
209
  /**
204
- * <p>The <code>family</code> and <code>revision</code> (<code>family:revision</code>) or
205
- * full ARN of the task definition to run in your service. If a <code>revision</code> is
206
- * not specified, the latest <code>ACTIVE</code> revision is used. If you modify the task
207
- * definition with <code>UpdateService</code>, Amazon ECS spawns a task with the new version of
208
- * the task definition and then stops an old task after the new version is running.</p>
210
+ * <p>The <code>family</code> and <code>revision</code> (<code>family:revision</code>) or full ARN of the
211
+ * task definition to run in your service. If a <code>revision</code> is not specified, the latest
212
+ * <code>ACTIVE</code> revision is used. If you modify the task definition with
213
+ * <code>UpdateService</code>, Amazon ECS spawns a task with the new version of the task definition and
214
+ * then stops an old task after the new version is running.</p>
209
215
  * @public
210
216
  */
211
217
  taskDefinition?: string | undefined;
212
218
  /**
213
219
  * <p>The capacity provider strategy to update the service to use.</p>
214
- * <p>if the service uses the default capacity provider strategy for the cluster, the
215
- * service can be updated to use one or more capacity providers as opposed to the default
216
- * capacity provider strategy. However, when a service is using a capacity provider
217
- * strategy that's not the default capacity provider strategy, the service can't be updated
218
- * to use the cluster's default capacity provider strategy.</p>
220
+ * <p>if the service uses the default capacity provider strategy for the cluster, the service can be
221
+ * updated to use one or more capacity providers as opposed to the default capacity provider strategy.
222
+ * However, when a service is using a capacity provider strategy that's not the default capacity provider
223
+ * strategy, the service can't be updated to use the cluster's default capacity provider strategy.</p>
219
224
  * <p>A capacity provider strategy consists of one or more capacity providers along with the
220
- * <code>base</code> and <code>weight</code> to assign to them. A capacity provider
221
- * must be associated with the cluster to be used in a capacity provider strategy. The
222
- * <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html">PutClusterCapacityProviders</a> API is used to associate a capacity
223
- * provider with a cluster. Only capacity providers with an <code>ACTIVE</code> or
224
- * <code>UPDATING</code> status can be used.</p>
225
- * <p>If specifying a capacity provider that uses an Auto Scaling group, the capacity
226
- * provider must already be created. New capacity providers can be created with the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html">CreateClusterCapacityProvider</a> API operation.</p>
225
+ * <code>base</code> and <code>weight</code> to assign to them. A capacity provider must be associated
226
+ * with the cluster to be used in a capacity provider strategy. The <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html">PutClusterCapacityProviders</a> API is used to associate a capacity provider with a cluster.
227
+ * Only capacity providers with an <code>ACTIVE</code> or <code>UPDATING</code> status can be used.</p>
228
+ * <p>If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already
229
+ * be created. New capacity providers can be created with the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html">CreateClusterCapacityProvider</a> API operation.</p>
227
230
  * <p>To use a Fargate capacity provider, specify either the <code>FARGATE</code> or
228
- * <code>FARGATE_SPOT</code> capacity providers. The Fargate capacity providers are
229
- * available to all accounts and only need to be associated with a cluster to be
230
- * used.</p>
231
- * <p>The <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html">PutClusterCapacityProviders</a>API operation is used to update the
232
- * list of available capacity providers for a cluster after the cluster is created.</p>
231
+ * <code>FARGATE_SPOT</code> capacity providers. The Fargate capacity providers are available to all
232
+ * accounts and only need to be associated with a cluster to be used.</p>
233
+ * <p>The <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html">PutClusterCapacityProviders</a>API operation is used to update the list of available capacity
234
+ * providers for a cluster after the cluster is created.</p>
233
235
  * <p></p>
234
236
  * @public
235
237
  */
236
238
  capacityProviderStrategy?: CapacityProviderStrategyItem[] | undefined;
237
239
  /**
238
- * <p>Optional deployment parameters that control how many tasks run during the deployment and the
239
- * failure detection methods.</p>
240
+ * <p>Optional deployment parameters that control how many tasks run during the deployment and the ordering
241
+ * of stopping and starting tasks.</p>
240
242
  * @public
241
243
  */
242
244
  deploymentConfiguration?: DeploymentConfiguration | undefined;
@@ -246,116 +248,109 @@ export interface UpdateServiceRequest {
246
248
  */
247
249
  networkConfiguration?: NetworkConfiguration | undefined;
248
250
  /**
249
- * <p>An array of task placement constraint objects to update the service to use. If no
250
- * value is specified, the existing placement constraints for the service will remain
251
- * unchanged. If this value is specified, it will override any existing placement
252
- * constraints defined for the service. To remove all existing placement constraints,
253
- * specify an empty array.</p>
254
- * <p>You can specify a maximum of 10 constraints for each task. This limit includes
255
- * constraints in the task definition and those specified at runtime.</p>
251
+ * <p>An array of task placement constraint objects to update the service to use. If no value is specified,
252
+ * the existing placement constraints for the service will remain unchanged. If this value is specified,
253
+ * it will override any existing placement constraints defined for the service. To remove all existing
254
+ * placement constraints, specify an empty array.</p>
255
+ * <p>You can specify a maximum of 10 constraints for each task. This limit includes constraints in the
256
+ * task definition and those specified at runtime.</p>
256
257
  * @public
257
258
  */
258
259
  placementConstraints?: PlacementConstraint[] | undefined;
259
260
  /**
260
- * <p>The task placement strategy objects to update the service to use. If no value is
261
- * specified, the existing placement strategy for the service will remain unchanged. If
262
- * this value is specified, it will override the existing placement strategy defined for
263
- * the service. To remove an existing placement strategy, specify an empty object.</p>
261
+ * <p>The task placement strategy objects to update the service to use. If no value is specified, the
262
+ * existing placement strategy for the service will remain unchanged. If this value is specified, it will
263
+ * override the existing placement strategy defined for the service. To remove an existing placement
264
+ * strategy, specify an empty object.</p>
264
265
  * <p>You can specify a maximum of five strategy rules for each service.</p>
265
266
  * @public
266
267
  */
267
268
  placementStrategy?: PlacementStrategy[] | undefined;
268
269
  /**
269
- * <p>The platform version that your tasks in the service run on. A platform version is only
270
- * specified for tasks using the Fargate launch type. If a platform version
271
- * is not specified, the <code>LATEST</code> platform version is used. For more
272
- * information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
273
- * Versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
270
+ * <p>The platform version that your tasks in the service run on. A platform version is only specified for
271
+ * tasks using the Fargate launch type. If a platform version is not specified, the
272
+ * <code>LATEST</code> platform version is used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform Versions</a> in
273
+ * the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
274
274
  * @public
275
275
  */
276
276
  platformVersion?: string | undefined;
277
277
  /**
278
- * <p>Determines whether to force a new deployment of the service. By default, deployments
279
- * aren't forced. You can use this option to start a new deployment with no service
280
- * definition changes. For example, you can update a service's tasks to use a newer Docker
281
- * image with the same image/tag combination (<code>my_image:latest</code>) or to roll
282
- * Fargate tasks onto a newer platform version.</p>
278
+ * <p>Determines whether to force a new deployment of the service. By default, deployments aren't forced.
279
+ * You can use this option to start a new deployment with no service definition changes. For example, you
280
+ * can update a service's tasks to use a newer Docker image with the same image/tag combination
281
+ * (<code>my_image:latest</code>) or to roll Fargate tasks onto a newer platform version.</p>
283
282
  * @public
284
283
  */
285
284
  forceNewDeployment?: boolean | undefined;
286
285
  /**
287
- * <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy
288
- * Elastic Load Balancing target health checks after a task has first started. This is only valid if your
289
- * service is configured to use a load balancer. If your service's tasks take a while to
290
- * start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of
291
- * up to 2,147,483,647 seconds. During that time, the Amazon ECS service scheduler ignores
292
- * the Elastic Load Balancing health check status. This grace period can prevent the ECS service scheduler
293
- * from marking tasks as unhealthy and stopping them before they have time to come
294
- * up.</p>
286
+ * <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container
287
+ * health checks after a task has first started. If you don't specify a health check grace
288
+ * period value, the default value of <code>0</code> is used. If you don't use any of the health checks,
289
+ * then <code>healthCheckGracePeriodSeconds</code> is unused.</p>
290
+ * <p>If your service's tasks take a while to start and respond to health checks, you can specify a
291
+ * health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS
292
+ * service scheduler ignores health check status. This grace period can prevent the service scheduler from
293
+ * marking tasks as unhealthy and stopping them before they have time to come up.</p>
295
294
  * @public
296
295
  */
297
296
  healthCheckGracePeriodSeconds?: number | undefined;
298
297
  /**
299
- * <p>If <code>true</code>, this enables execute command functionality on all task
300
- * containers.</p>
301
- * <p>If you do not want to override the value that was set when the service was created,
302
- * you can set this to <code>null</code> when performing this action.</p>
298
+ * <p>If <code>true</code>, this enables execute command functionality on all task containers.</p>
299
+ * <p>If you do not want to override the value that was set when the service was created, you can set this
300
+ * to <code>null</code> when performing this action.</p>
303
301
  * @public
304
302
  */
305
303
  enableExecuteCommand?: boolean | undefined;
306
304
  /**
307
- * <p>Determines whether to turn on Amazon ECS managed tags for the tasks in the service. For
308
- * more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html">Tagging Your Amazon ECS
309
- * Resources</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
310
- * <p>Only tasks launched after the update will reflect the update. To update the tags on
311
- * all tasks, set <code>forceNewDeployment</code> to <code>true</code>, so that Amazon ECS
312
- * starts new tasks with the updated tags.</p>
305
+ * <p>Determines whether to turn on Amazon ECS managed tags for the tasks in the service. For more information,
306
+ * see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html">Tagging Your
307
+ * Amazon ECS Resources</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
308
+ * <p>Only tasks launched after the update will reflect the update. To update the tags on all tasks, set
309
+ * <code>forceNewDeployment</code> to <code>true</code>, so that Amazon ECS starts new tasks with the
310
+ * updated tags.</p>
313
311
  * @public
314
312
  */
315
313
  enableECSManagedTags?: boolean | undefined;
316
314
  /**
317
- * <p>A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the
318
- * container name, and the container port to access from the load balancer. The container
319
- * name is as it appears in a container definition.</p>
320
- * <p>When you add, update, or remove a load balancer configuration, Amazon ECS starts new tasks
321
- * with the updated Elastic Load Balancing configuration, and then stops the old tasks when the new tasks
322
- * are running.</p>
323
- * <p>For services that use rolling updates, you can add, update, or remove Elastic Load Balancing target
324
- * groups. You can update from a single target group to multiple target groups and from
325
- * multiple target groups to a single target group.</p>
326
- * <p>For services that use blue/green deployments, you can update Elastic Load Balancing target groups by
327
- * using <code>
315
+ * <p>A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the container name, and
316
+ * the container port to access from the load balancer. The container name is as it appears in a container
317
+ * definition.</p>
318
+ * <p>When you add, update, or remove a load balancer configuration, Amazon ECS starts new tasks with the
319
+ * updated Elastic Load Balancing configuration, and then stops the old tasks when the new tasks are running.</p>
320
+ * <p>For services that use rolling updates, you can add, update, or remove Elastic Load Balancing target groups. You can
321
+ * update from a single target group to multiple target groups and from multiple target groups to a single
322
+ * target group.</p>
323
+ * <p>For services that use blue/green deployments, you can update Elastic Load Balancing target groups by using
324
+ * <code>
328
325
  * <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html">CreateDeployment</a>
329
- * </code> through CodeDeploy. Note that multiple target groups
330
- * are not supported for blue/green deployments. For more information see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html">Register
331
- * multiple target groups with a service</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. </p>
332
- * <p>For services that use the external deployment controller, you can add, update, or
333
- * remove load balancers by using <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>.
334
- * Note that multiple target groups are not supported for external deployments. For more
335
- * information see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html">Register
336
- * multiple target groups with a service</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. </p>
326
+ * </code>
327
+ * through CodeDeploy. Note that multiple target groups are not supported for blue/green deployments. For more
328
+ * information see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html">Register multiple target
329
+ * groups with a service</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. </p>
330
+ * <p>For services that use the external deployment controller, you can add, update, or remove load
331
+ * balancers by using <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. Note that
332
+ * multiple target groups are not supported for external deployments. For more information see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html">Register multiple target groups with a service</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. </p>
337
333
  * <p>You can remove existing <code>loadBalancers</code> by passing an empty list.</p>
338
334
  * @public
339
335
  */
340
336
  loadBalancers?: LoadBalancer[] | undefined;
341
337
  /**
342
- * <p>Determines whether to propagate the tags from the task definition or the service to
343
- * the task. If no value is specified, the tags aren't propagated.</p>
344
- * <p>Only tasks launched after the update will reflect the update. To update the tags on
345
- * all tasks, set <code>forceNewDeployment</code> to <code>true</code>, so that Amazon ECS
346
- * starts new tasks with the updated tags.</p>
338
+ * <p>Determines whether to propagate the tags from the task definition or the service to the task. If no
339
+ * value is specified, the tags aren't propagated.</p>
340
+ * <p>Only tasks launched after the update will reflect the update. To update the tags on all tasks, set
341
+ * <code>forceNewDeployment</code> to <code>true</code>, so that Amazon ECS starts new tasks with the
342
+ * updated tags.</p>
347
343
  * @public
348
344
  */
349
345
  propagateTags?: PropagateTags | undefined;
350
346
  /**
351
- * <p>The details for the service discovery registries to assign to this service. For more
352
- * information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
347
+ * <p>The details for the service discovery registries to assign to this service. For more information, see
348
+ * <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
353
349
  * Discovery</a>.</p>
354
- * <p>When you add, update, or remove the service registries configuration, Amazon ECS starts new
355
- * tasks with the updated service registries configuration, and then stops the old tasks
356
- * when the new tasks are running.</p>
357
- * <p>You can remove existing <code>serviceRegistries</code> by passing an empty
358
- * list.</p>
350
+ * <p>When you add, update, or remove the service registries configuration, Amazon ECS starts new tasks with the
351
+ * updated service registries configuration, and then stops the old tasks when the new tasks are
352
+ * running.</p>
353
+ * <p>You can remove existing <code>serviceRegistries</code> by passing an empty list.</p>
359
354
  * @public
360
355
  */
361
356
  serviceRegistries?: ServiceRegistry[] | undefined;
@@ -372,14 +367,18 @@ export interface UpdateServiceRequest {
372
367
  */
373
368
  serviceConnectConfiguration?: ServiceConnectConfiguration | undefined;
374
369
  /**
375
- * <p>The details of the volume that was <code>configuredAtLaunch</code>. You can configure
376
- * the size, volumeType, IOPS, throughput, snapshot and encryption in <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ServiceManagedEBSVolumeConfiguration.html">ServiceManagedEBSVolumeConfiguration</a>. The <code>name</code> of the volume
377
- * must match the <code>name</code> from the task definition. If set to null, no new
378
- * deployment is triggered. Otherwise, if this configuration differs from the existing one,
379
- * it triggers a new deployment.</p>
370
+ * <p>The details of the volume that was <code>configuredAtLaunch</code>. You can configure the size,
371
+ * volumeType, IOPS, throughput, snapshot and encryption in <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ServiceManagedEBSVolumeConfiguration.html">ServiceManagedEBSVolumeConfiguration</a>. The <code>name</code> of the volume must match the
372
+ * <code>name</code> from the task definition. If set to null, no new deployment is triggered.
373
+ * Otherwise, if this configuration differs from the existing one, it triggers a new deployment.</p>
380
374
  * @public
381
375
  */
382
376
  volumeConfigurations?: ServiceVolumeConfiguration[] | undefined;
377
+ /**
378
+ * <p>An object representing the VPC Lattice configuration for the service being updated.</p>
379
+ * @public
380
+ */
381
+ vpcLatticeConfigurations?: VpcLatticeConfiguration[] | undefined;
383
382
  }
384
383
  /**
385
384
  * @public
@@ -396,8 +395,8 @@ export interface UpdateServiceResponse {
396
395
  */
397
396
  export interface UpdateServicePrimaryTaskSetRequest {
398
397
  /**
399
- * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task
400
- * set exists in.</p>
398
+ * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task set exists
399
+ * in.</p>
401
400
  * @public
402
401
  */
403
402
  cluster: string | undefined;
@@ -428,8 +427,8 @@ export interface UpdateServicePrimaryTaskSetResponse {
428
427
  */
429
428
  export interface UpdateTaskProtectionRequest {
430
429
  /**
431
- * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task
432
- * sets exist in.</p>
430
+ * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task sets exist
431
+ * in.</p>
433
432
  * @public
434
433
  */
435
434
  cluster: string | undefined;
@@ -439,19 +438,19 @@ export interface UpdateTaskProtectionRequest {
439
438
  */
440
439
  tasks: string[] | undefined;
441
440
  /**
442
- * <p>Specify <code>true</code> to mark a task for protection and <code>false</code> to
443
- * unset protection, making it eligible for termination.</p>
441
+ * <p>Specify <code>true</code> to mark a task for protection and <code>false</code> to unset protection,
442
+ * making it eligible for termination.</p>
444
443
  * @public
445
444
  */
446
445
  protectionEnabled: boolean | undefined;
447
446
  /**
448
- * <p>If you set <code>protectionEnabled</code> to <code>true</code>, you can specify the
449
- * duration for task protection in minutes. You can specify a value from 1 minute to up to
450
- * 2,880 minutes (48 hours). During this time, your task will not be terminated by scale-in
451
- * events from Service Auto Scaling or deployments. After this time period lapses,
452
- * <code>protectionEnabled</code> will be reset to <code>false</code>.</p>
453
- * <p>If you don’t specify the time, then the task is automatically protected for 120
454
- * minutes (2 hours).</p>
447
+ * <p>If you set <code>protectionEnabled</code> to <code>true</code>, you can specify the duration for task
448
+ * protection in minutes. You can specify a value from 1 minute to up to 2,880 minutes (48 hours). During
449
+ * this time, your task will not be terminated by scale-in events from Service Auto Scaling or
450
+ * deployments. After this time period lapses, <code>protectionEnabled</code> will be reset to
451
+ * <code>false</code>.</p>
452
+ * <p>If you don’t specify the time, then the task is automatically protected for 120 minutes (2
453
+ * hours).</p>
455
454
  * @public
456
455
  */
457
456
  expiresInMinutes?: number | undefined;
@@ -469,14 +468,13 @@ export interface UpdateTaskProtectionResponse {
469
468
  * </li>
470
469
  * <li>
471
470
  * <p>
472
- * <code>protectionEnabled</code>: The protection status of the task. If scale-in
473
- * protection is turned on for a task, the value is <code>true</code>. Otherwise,
474
- * it is <code>false</code>.</p>
471
+ * <code>protectionEnabled</code>: The protection status of the task. If scale-in protection is
472
+ * turned on for a task, the value is <code>true</code>. Otherwise, it is
473
+ * <code>false</code>.</p>
475
474
  * </li>
476
475
  * <li>
477
476
  * <p>
478
- * <code>expirationDate</code>: The epoch time when protection for the task will
479
- * expire.</p>
477
+ * <code>expirationDate</code>: The epoch time when protection for the task will expire.</p>
480
478
  * </li>
481
479
  * </ul>
482
480
  * @public
@@ -493,8 +491,8 @@ export interface UpdateTaskProtectionResponse {
493
491
  */
494
492
  export interface UpdateTaskSetRequest {
495
493
  /**
496
- * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task
497
- * set is found in.</p>
494
+ * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task set is found
495
+ * in.</p>
498
496
  * @public
499
497
  */
500
498
  cluster: string | undefined;
@@ -509,8 +507,8 @@ export interface UpdateTaskSetRequest {
509
507
  */
510
508
  taskSet: string | undefined;
511
509
  /**
512
- * <p>A floating-point percentage of the desired number of tasks to place and keep running
513
- * in the task set.</p>
510
+ * <p>A floating-point percentage of the desired number of tasks to place and keep running in the task
511
+ * set.</p>
514
512
  * @public
515
513
  */
516
514
  scale: Scale | undefined;
@@ -5,10 +5,8 @@ import {
5
5
  ServiceInputTypes,
6
6
  ServiceOutputTypes,
7
7
  } from "../ECSClient";
8
- import {
9
- UpdateCapacityProviderRequest,
10
- UpdateCapacityProviderResponse,
11
- } from "../models/models_0";
8
+ import { UpdateCapacityProviderRequest } from "../models/models_0";
9
+ import { UpdateCapacityProviderResponse } from "../models/models_1";
12
10
  export { __MetadataBearer };
13
11
  export { $Command };
14
12
  export interface UpdateCapacityProviderCommandInput
@@ -391,6 +391,11 @@ export interface ServiceVolumeConfiguration {
391
391
  name: string | undefined;
392
392
  managedEBSVolume?: ServiceManagedEBSVolumeConfiguration | undefined;
393
393
  }
394
+ export interface VpcLatticeConfiguration {
395
+ roleArn: string | undefined;
396
+ targetGroupArn: string | undefined;
397
+ portName: string | undefined;
398
+ }
394
399
  export interface CreateServiceRequest {
395
400
  cluster?: string | undefined;
396
401
  serviceName: string | undefined;
@@ -416,6 +421,7 @@ export interface CreateServiceRequest {
416
421
  enableExecuteCommand?: boolean | undefined;
417
422
  serviceConnectConfiguration?: ServiceConnectConfiguration | undefined;
418
423
  volumeConfigurations?: ServiceVolumeConfiguration[] | undefined;
424
+ vpcLatticeConfigurations?: VpcLatticeConfiguration[] | undefined;
419
425
  }
420
426
  export interface DeploymentEphemeralStorage {
421
427
  kmsKeyId?: string | undefined;
@@ -452,6 +458,7 @@ export interface Deployment {
452
458
  serviceConnectResources?: ServiceConnectServiceResource[] | undefined;
453
459
  volumeConfigurations?: ServiceVolumeConfiguration[] | undefined;
454
460
  fargateEphemeralStorage?: DeploymentEphemeralStorage | undefined;
461
+ vpcLatticeConfigurations?: VpcLatticeConfiguration[] | undefined;
455
462
  }
456
463
  export interface ServiceEvent {
457
464
  id?: string | undefined;
@@ -1279,6 +1286,7 @@ export interface ServiceRevision {
1279
1286
  volumeConfigurations?: ServiceVolumeConfiguration[] | undefined;
1280
1287
  fargateEphemeralStorage?: DeploymentEphemeralStorage | undefined;
1281
1288
  createdAt?: Date | undefined;
1289
+ vpcLatticeConfigurations?: VpcLatticeConfiguration[] | undefined;
1282
1290
  }
1283
1291
  export interface DescribeServiceRevisionsResponse {
1284
1292
  serviceRevisions?: ServiceRevision[] | undefined;
@@ -1930,9 +1938,6 @@ export interface UpdateCapacityProviderRequest {
1930
1938
  name: string | undefined;
1931
1939
  autoScalingGroupProvider: AutoScalingGroupProviderUpdate | undefined;
1932
1940
  }
1933
- export interface UpdateCapacityProviderResponse {
1934
- capacityProvider?: CapacityProvider | undefined;
1935
- }
1936
1941
  export declare const SessionFilterSensitiveLog: (obj: Session) => any;
1937
1942
  export declare const ExecuteCommandResponseFilterSensitiveLog: (
1938
1943
  obj: ExecuteCommandResponse
@@ -1,6 +1,7 @@
1
1
  import { ExceptionOptionType as __ExceptionOptionType } from "@smithy/smithy-client";
2
2
  import { ECSServiceException as __BaseException } from "./ECSServiceException";
3
3
  import {
4
+ CapacityProvider,
4
5
  CapacityProviderStrategyItem,
5
6
  Cluster,
6
7
  ClusterConfiguration,
@@ -22,7 +23,11 @@ import {
22
23
  ServiceRegistry,
23
24
  ServiceVolumeConfiguration,
24
25
  TaskSet,
26
+ VpcLatticeConfiguration,
25
27
  } from "./models_0";
28
+ export interface UpdateCapacityProviderResponse {
29
+ capacityProvider?: CapacityProvider | undefined;
30
+ }
26
31
  export interface UpdateClusterRequest {
27
32
  cluster: string | undefined;
28
33
  settings?: ClusterSetting[] | undefined;
@@ -89,6 +94,7 @@ export interface UpdateServiceRequest {
89
94
  serviceRegistries?: ServiceRegistry[] | undefined;
90
95
  serviceConnectConfiguration?: ServiceConnectConfiguration | undefined;
91
96
  volumeConfigurations?: ServiceVolumeConfiguration[] | undefined;
97
+ vpcLatticeConfigurations?: VpcLatticeConfiguration[] | undefined;
92
98
  }
93
99
  export interface UpdateServiceResponse {
94
100
  service?: Service | undefined;
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.693.0",
4
+ "version": "3.695.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "node ../../scripts/compilation/inline client-ecs",