@aws-sdk/client-ecs 3.693.0 → 3.696.0

package/dist-types/commands/UpdateContainerInstancesStateCommand.d.ts

@@ -28,54 +28,50 @@ declare const UpdateContainerInstancesStateCommand_base: {
 };
 /**
  * <p>Modifies the status of an Amazon ECS container instance.</p>
- *          <p>Once a container instance has reached an <code>ACTIVE</code> state, you can change the
- * 			status of a container instance to <code>DRAINING</code> to manually remove an instance
- * 			from a cluster, for example to perform system updates, update the Docker daemon, or
- * 			scale down the cluster size.</p>
+ *          <p>Once a container instance has reached an <code>ACTIVE</code> state, you can change the status of a
+ * 			container instance to <code>DRAINING</code> to manually remove an instance from a cluster, for example
+ * 			to perform system updates, update the Docker daemon, or scale down the cluster size.</p>
  *          <important>
- *             <p>A container instance can't be changed to <code>DRAINING</code> until it has
- * 				reached an <code>ACTIVE</code> status. If the instance is in any other status, an
- * 				error will be received.</p>
+ *             <p>A container instance can't be changed to <code>DRAINING</code> until it has reached an
+ * 					<code>ACTIVE</code> status. If the instance is in any other status, an error will be
+ * 				received.</p>
  *          </important>
- *          <p>When you set a container instance to <code>DRAINING</code>, Amazon ECS prevents new tasks
- * 			from being scheduled for placement on the container instance and replacement service
- * 			tasks are started on other container instances in the cluster if the resources are
- * 			available. Service tasks on the container instance that are in the <code>PENDING</code>
- * 			state are stopped immediately.</p>
- *          <p>Service tasks on the container instance that are in the <code>RUNNING</code> state are
- * 			stopped and replaced according to the service's deployment configuration parameters,
- * 				<code>minimumHealthyPercent</code> and <code>maximumPercent</code>. You can change
- * 			the deployment configuration of your service using <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p>
+ *          <p>When you set a container instance to <code>DRAINING</code>, Amazon ECS prevents new tasks from being
+ * 			scheduled for placement on the container instance and replacement service tasks are started on other
+ * 			container instances in the cluster if the resources are available. Service tasks on the container
+ * 			instance that are in the <code>PENDING</code> state are stopped immediately.</p>
+ *          <p>Service tasks on the container instance that are in the <code>RUNNING</code> state are stopped and
+ * 			replaced according to the service's deployment configuration parameters,
+ * 				<code>minimumHealthyPercent</code> and <code>maximumPercent</code>. You can change the deployment
+ * 			configuration of your service using <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p>
  *          <ul>
  *             <li>
  *                <p>If <code>minimumHealthyPercent</code> is below 100%, the scheduler can ignore
  * 						<code>desiredCount</code> temporarily during task replacement. For example,
- * 						<code>desiredCount</code> is four tasks, a minimum of 50% allows the
- * 					scheduler to stop two existing tasks before starting two new tasks. If the
- * 					minimum is 100%, the service scheduler can't remove existing tasks until the
- * 					replacement tasks are considered healthy. Tasks for services that do not use a
- * 					load balancer are considered healthy if they're in the <code>RUNNING</code>
- * 					state. Tasks for services that use a load balancer are considered healthy if
- * 					they're in the <code>RUNNING</code> state and are reported as healthy by the
- * 					load balancer.</p>
+ * 						<code>desiredCount</code> is four tasks, a minimum of 50% allows the scheduler to stop two
+ * 					existing tasks before starting two new tasks. If the minimum is 100%, the service scheduler
+ * 					can't remove existing tasks until the replacement tasks are considered healthy. Tasks for
+ * 					services that do not use a load balancer are considered healthy if they're in the
+ * 						<code>RUNNING</code> state. Tasks for services that use a load balancer are considered
+ * 					healthy if they're in the <code>RUNNING</code> state and are reported as healthy by the load
+ * 					balancer.</p>
  *             </li>
  *             <li>
- *                <p>The <code>maximumPercent</code> parameter represents an upper limit on the
- * 					number of running tasks during task replacement. You can use this to define the
- * 					replacement batch size. For example, if <code>desiredCount</code> is four tasks,
- * 					a maximum of 200% starts four new tasks before stopping the four tasks to be
- * 					drained, provided that the cluster resources required to do this are available.
- * 					If the maximum is 100%, then replacement tasks can't start until the draining
- * 					tasks have stopped.</p>
+ *                <p>The <code>maximumPercent</code> parameter represents an upper limit on the number of running
+ * 					tasks during task replacement. You can use this to define the replacement batch size. For
+ * 					example, if <code>desiredCount</code> is four tasks, a maximum of 200% starts four new tasks
+ * 					before stopping the four tasks to be drained, provided that the cluster resources required to
+ * 					do this are available. If the maximum is 100%, then replacement tasks can't start until the
+ * 					draining tasks have stopped.</p>
  *             </li>
  *          </ul>
- *          <p>Any <code>PENDING</code> or <code>RUNNING</code> tasks that do not belong to a service
- * 			aren't affected. You must wait for them to finish or stop them manually.</p>
- *          <p>A container instance has completed draining when it has no more <code>RUNNING</code>
- * 			tasks. You can verify this using <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListTasks.html">ListTasks</a>.</p>
- *          <p>When a container instance has been drained, you can set a container instance to
- * 				<code>ACTIVE</code> status and once it has reached that status the Amazon ECS scheduler
- * 			can begin scheduling tasks on the instance again.</p>
+ *          <p>Any <code>PENDING</code> or <code>RUNNING</code> tasks that do not belong to a service aren't
+ * 			affected. You must wait for them to finish or stop them manually.</p>
+ *          <p>A container instance has completed draining when it has no more <code>RUNNING</code> tasks. You can
+ * 			verify this using <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListTasks.html">ListTasks</a>.</p>
+ *          <p>When a container instance has been drained, you can set a container instance to <code>ACTIVE</code>
+ * 			status and once it has reached that status the Amazon ECS scheduler can begin scheduling tasks on the
+ * 			instance again.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -192,17 +188,16 @@ declare const UpdateContainerInstancesStateCommand_base: {
  * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or
+ * 			resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might
+ * 			be specifying an identifier that isn't valid.</p>
  *          <p>The following list includes additional causes for the error:</p>
  *          <ul>
  *             <li>
- *                <p>The <code>RunTask</code> could not be processed because you use managed
- * 					scaling and there is a capacity error because the quota of tasks in the
- * 					<code>PROVISIONING</code> per cluster has been reached. For information
- * 					about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
- * 						service quotas</a>.</p>
+ *                <p>The <code>RunTask</code> could not be processed because you use managed scaling and there is
+ * 					a capacity error because the quota of tasks in the <code>PROVISIONING</code> per cluster has
+ * 					been reached. For information about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service
+ * 						quotas</a>.</p>
  *             </li>
  *          </ul>
  *
@@ -210,8 +205,7 @@ declare const UpdateContainerInstancesStateCommand_base: {
  *  <p>The specified cluster wasn't found. You can view your available clusters with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html">ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API
- * 			request.</p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/dist-types/commands/UpdateServiceCommand.d.ts

@@ -31,117 +31,111 @@ declare const UpdateServiceCommand_base: {
  *          <note>
  *             <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p>
  *          </note>
- *          <p>For services using the rolling update (<code>ECS</code>) you can update the desired
- * 			count, deployment configuration, network configuration, load balancers, service
- * 			registries, enable ECS managed tags option, propagate tags option, task placement
- * 			constraints and strategies, and task definition. When you update any of these
- * 			parameters, Amazon ECS starts new tasks with the new configuration. </p>
- *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or
- * 			running a task, or when creating or updating a service. For more infomation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. You can update
- * 			your volume configurations and trigger a new deployment.
- * 				<code>volumeConfigurations</code> is only supported for REPLICA service and not
- * 			DAEMON service. If you leave <code>volumeConfigurations</code>
- *             <code>null</code>, it doesn't trigger a new deployment. For more infomation on volumes,
- * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- *          <p>For services using the blue/green (<code>CODE_DEPLOY</code>) deployment controller,
- * 			only the desired count, deployment configuration, health check grace period, task
- * 			placement constraints and strategies, enable ECS managed tags option, and propagate tags
- * 			can be updated using this API. If the network configuration, platform version, task
- * 			definition, or load balancer need to be updated, create a new CodeDeploy deployment. For more
- * 			information, see <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html">CreateDeployment</a> in the <i>CodeDeploy API Reference</i>.</p>
- *          <p>For services using an external deployment controller, you can update only the desired
- * 			count, task placement constraints and strategies, health check grace period, enable ECS
- * 			managed tags option, and propagate tags option, using this API. If the launch type, load
- * 			balancer, network configuration, platform version, or task definition need to be
- * 			updated, create a new task set For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>.</p>
- *          <p>You can add to or subtract from the number of instantiations of a task definition in a
- * 			service by specifying the cluster that the service is running in and a new
- * 				<code>desiredCount</code> parameter.</p>
- *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or
- * 			running a task, or when creating or updating a service. For more infomation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- *          <p>If you have updated the container image of your application, you can create a new task
- * 			definition with that image and deploy it to your service. The service scheduler uses the
- * 			minimum healthy percent and maximum percent parameters (in the service's deployment
- * 			configuration) to determine the deployment strategy.</p>
+ *          <p>For services using the rolling update (<code>ECS</code>) you can update the desired count, deployment
+ * 			configuration, network configuration, load balancers, service registries, enable ECS managed tags
+ * 			option, propagate tags option, task placement constraints and strategies, and task definition. When you
+ * 			update any of these parameters, Amazon ECS starts new tasks with the new configuration. </p>
+ *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or running a
+ * 			task, or when creating or updating a service. For more infomation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS
+ * 				volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. You can update your volume configurations and trigger a new
+ * 			deployment. <code>volumeConfigurations</code> is only supported for REPLICA service and not DAEMON
+ * 			service. If you leave <code>volumeConfigurations</code>
+ *             <code>null</code>, it doesn't trigger a new deployment. For more infomation on volumes, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS
+ * 				volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <p>For services using the blue/green (<code>CODE_DEPLOY</code>) deployment controller, only the desired
+ * 			count, deployment configuration, health check grace period, task placement constraints and strategies,
+ * 			enable ECS managed tags option, and propagate tags can be updated using this API. If the network
+ * 			configuration, platform version, task definition, or load balancer need to be updated, create a new
+ * 			CodeDeploy deployment. For more information, see <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html">CreateDeployment</a> in the
+ * 			<i>CodeDeploy API Reference</i>.</p>
+ *          <p>For services using an external deployment controller, you can update only the desired count, task
+ * 			placement constraints and strategies, health check grace period, enable ECS managed tags option, and
+ * 			propagate tags option, using this API. If the launch type, load balancer, network configuration,
+ * 			platform version, or task definition need to be updated, create a new task set For more information,
+ * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>.</p>
+ *          <p>You can add to or subtract from the number of instantiations of a task definition in a service by
+ * 			specifying the cluster that the service is running in and a new <code>desiredCount</code>
+ * 			parameter.</p>
+ *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or running a
+ * 			task, or when creating or updating a service. For more infomation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS
+ * 				volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <p>If you have updated the container image of your application, you can create a new task definition
+ * 			with that image and deploy it to your service. The service scheduler uses the minimum healthy percent
+ * 			and maximum percent parameters (in the service's deployment configuration) to determine the deployment
+ * 			strategy.</p>
  *          <note>
- *             <p>If your updated Docker image uses the same tag as what is in the existing task
- * 				definition for your service (for example, <code>my_image:latest</code>), you don't
- * 				need to create a new revision of your task definition. You can update the service
- * 				using the <code>forceNewDeployment</code> option. The new tasks launched by the
- * 				deployment pull the current image/tag combination from your repository when they
- * 				start.</p>
+ *             <p>If your updated Docker image uses the same tag as what is in the existing task definition for
+ * 				your service (for example, <code>my_image:latest</code>), you don't need to create a new revision
+ * 				of your task definition. You can update the service using the <code>forceNewDeployment</code>
+ * 				option. The new tasks launched by the deployment pull the current image/tag combination from your
+ * 				repository when they start.</p>
  *          </note>
- *          <p>You can also update the deployment configuration of a service. When a deployment is
- * 			triggered by updating the task definition of a service, the service scheduler uses the
- * 			deployment configuration parameters, <code>minimumHealthyPercent</code> and
- * 				<code>maximumPercent</code>, to determine the deployment strategy.</p>
+ *          <p>You can also update the deployment configuration of a service. When a deployment is triggered by
+ * 			updating the task definition of a service, the service scheduler uses the deployment configuration
+ * 			parameters, <code>minimumHealthyPercent</code> and <code>maximumPercent</code>, to determine the
+ * 			deployment strategy.</p>
  *          <ul>
  *             <li>
  *                <p>If <code>minimumHealthyPercent</code> is below 100%, the scheduler can ignore
  * 						<code>desiredCount</code> temporarily during a deployment. For example, if
- * 						<code>desiredCount</code> is four tasks, a minimum of 50% allows the
- * 					scheduler to stop two existing tasks before starting two new tasks. Tasks for
- * 					services that don't use a load balancer are considered healthy if they're in the
- * 						<code>RUNNING</code> state. Tasks for services that use a load balancer are
- * 					considered healthy if they're in the <code>RUNNING</code> state and are reported
- * 					as healthy by the load balancer.</p>
+ * 						<code>desiredCount</code> is four tasks, a minimum of 50% allows the scheduler to stop two
+ * 					existing tasks before starting two new tasks. Tasks for services that don't use a load balancer
+ * 					are considered healthy if they're in the <code>RUNNING</code> state. Tasks for services that
+ * 					use a load balancer are considered healthy if they're in the <code>RUNNING</code> state and are
+ * 					reported as healthy by the load balancer.</p>
  *             </li>
  *             <li>
- *                <p>The <code>maximumPercent</code> parameter represents an upper limit on the
- * 					number of running tasks during a deployment. You can use it to define the
- * 					deployment batch size. For example, if <code>desiredCount</code> is four tasks,
- * 					a maximum of 200% starts four new tasks before stopping the four older tasks
- * 					(provided that the cluster resources required to do this are available).</p>
+ *                <p>The <code>maximumPercent</code> parameter represents an upper limit on the number of running
+ * 					tasks during a deployment. You can use it to define the deployment batch size. For example, if
+ * 						<code>desiredCount</code> is four tasks, a maximum of 200% starts four new tasks before
+ * 					stopping the four older tasks (provided that the cluster resources required to do this are
+ * 					available).</p>
  *             </li>
  *          </ul>
- *          <p>When <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a> stops a task during a deployment, the equivalent
- * 			of <code>docker stop</code> is issued to the containers running in the task. This
- * 			results in a <code>SIGTERM</code> and a 30-second timeout. After this,
- * 				<code>SIGKILL</code> is sent and the containers are forcibly stopped. If the
- * 			container handles the <code>SIGTERM</code> gracefully and exits within 30 seconds from
- * 			receiving it, no <code>SIGKILL</code> is sent.</p>
- *          <p>When the service scheduler launches new tasks, it determines task placement in your
- * 			cluster with the following logic.</p>
+ *          <p>When <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a> stops a task during a deployment, the equivalent of <code>docker stop</code>
+ * 			is issued to the containers running in the task. This results in a <code>SIGTERM</code> and a 30-second
+ * 			timeout. After this, <code>SIGKILL</code> is sent and the containers are forcibly stopped. If the
+ * 			container handles the <code>SIGTERM</code> gracefully and exits within 30 seconds from receiving it, no
+ * 				<code>SIGKILL</code> is sent.</p>
+ *          <p>When the service scheduler launches new tasks, it determines task placement in your cluster with the
+ * 			following logic.</p>
  *          <ul>
  *             <li>
- *                <p>Determine which of the container instances in your cluster can support your
- * 					service's task definition. For example, they have the required CPU, memory,
- * 					ports, and container instance attributes.</p>
+ *                <p>Determine which of the container instances in your cluster can support your service's task
+ * 					definition. For example, they have the required CPU, memory, ports, and container instance
+ * 					attributes.</p>
  *             </li>
  *             <li>
- *                <p>By default, the service scheduler attempts to balance tasks across
- * 					Availability Zones in this manner even though you can choose a different
- * 					placement strategy.</p>
+ *                <p>By default, the service scheduler attempts to balance tasks across Availability Zones in this
+ * 					manner even though you can choose a different placement strategy.</p>
  *                <ul>
  *                   <li>
- *                      <p>Sort the valid container instances by the fewest number of running
- * 							tasks for this service in the same Availability Zone as the instance.
- * 							For example, if zone A has one running service task and zones B and C
- * 							each have zero, valid container instances in either zone B or C are
- * 							considered optimal for placement.</p>
+ *                      <p>Sort the valid container instances by the fewest number of running tasks for this
+ * 							service in the same Availability Zone as the instance. For example, if zone A has one
+ * 							running service task and zones B and C each have zero, valid container instances in
+ * 							either zone B or C are considered optimal for placement.</p>
  *                   </li>
  *                   <li>
- *                      <p>Place the new service task on a valid container instance in an optimal
- * 							Availability Zone (based on the previous steps), favoring container
- * 							instances with the fewest number of running tasks for this
- * 							service.</p>
+ *                      <p>Place the new service task on a valid container instance in an optimal Availability
+ * 							Zone (based on the previous steps), favoring container instances with the fewest number
+ * 							of running tasks for this service.</p>
  *                   </li>
  *                </ul>
  *             </li>
  *          </ul>
- *          <p>When the service scheduler stops running tasks, it attempts to maintain balance across
- * 			the Availability Zones in your cluster using the following logic: </p>
+ *          <p>When the service scheduler stops running tasks, it attempts to maintain balance across the
+ * 			Availability Zones in your cluster using the following logic: </p>
  *          <ul>
  *             <li>
- *                <p>Sort the container instances by the largest number of running tasks for this
- * 					service in the same Availability Zone as the instance. For example, if zone A
- * 					has one running service task and zones B and C each have two, container
- * 					instances in either zone B or C are considered optimal for termination.</p>
+ *                <p>Sort the container instances by the largest number of running tasks for this service in the
+ * 					same Availability Zone as the instance. For example, if zone A has one running service task and
+ * 					zones B and C each have two, container instances in either zone B or C are considered optimal
+ * 					for termination.</p>
  *             </li>
  *             <li>
- *                <p>Stop the task on a container instance in an optimal Availability Zone (based
- * 					on the previous steps), favoring container instances with the largest number of
- * 					running tasks for this service.</p>
+ *                <p>Stop the task on a container instance in an optimal Availability Zone (based on the previous
+ * 					steps), favoring container instances with the largest number of running tasks for this
+ * 					service.</p>
  *             </li>
  *          </ul>
  *          <note>
@@ -158,8 +152,7 @@ declare const UpdateServiceCommand_base: {
  *                   </p>
  *                </li>
  *             </ul>
- *             <p>For more information about the role see the <code>CreateService</code> request
- * 				parameter <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-role">
+ *             <p>For more information about the role see the <code>CreateService</code> request parameter <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-role">
  *                   <code>role</code>
  *                </a>. </p>
  *          </note>
@@ -309,6 +302,13 @@ declare const UpdateServiceCommand_base: {
  *       },
  *     },
  *   ],
+ *   vpcLatticeConfigurations: [ // VpcLatticeConfigurations
+ *     { // VpcLatticeConfiguration
+ *       roleArn: "STRING_VALUE", // required
+ *       targetGroupArn: "STRING_VALUE", // required
+ *       portName: "STRING_VALUE", // required
+ *     },
+ *   ],
  * };
  * const command = new UpdateServiceCommand(input);
  * const response = await client.send(command);
@@ -543,6 +543,13 @@ declare const UpdateServiceCommand_base: {
  * //         fargateEphemeralStorage: {
  * //           kmsKeyId: "STRING_VALUE",
  * //         },
+ * //         vpcLatticeConfigurations: [ // VpcLatticeConfigurations
+ * //           { // VpcLatticeConfiguration
+ * //             roleArn: "STRING_VALUE", // required
+ * //             targetGroupArn: "STRING_VALUE", // required
+ * //             portName: "STRING_VALUE", // required
+ * //           },
+ * //         ],
  * //       },
  * //     ],
  * //     roleArn: "STRING_VALUE",
@@ -598,17 +605,16 @@ declare const UpdateServiceCommand_base: {
  *  <p>You don't have authorization to perform the requested action.</p>
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or
+ * 			resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might
+ * 			be specifying an identifier that isn't valid.</p>
  *          <p>The following list includes additional causes for the error:</p>
  *          <ul>
  *             <li>
- *                <p>The <code>RunTask</code> could not be processed because you use managed
- * 					scaling and there is a capacity error because the quota of tasks in the
- * 					<code>PROVISIONING</code> per cluster has been reached. For information
- * 					about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
- * 						service quotas</a>.</p>
+ *                <p>The <code>RunTask</code> could not be processed because you use managed scaling and there is
+ * 					a capacity error because the quota of tasks in the <code>PROVISIONING</code> per cluster has
+ * 					been reached. For information about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service
+ * 						quotas</a>.</p>
  *             </li>
  *          </ul>
  *
@@ -616,8 +622,7 @@ declare const UpdateServiceCommand_base: {
  *  <p>The specified cluster wasn't found. You can view your available clusters with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html">ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API
- * 			request.</p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p>
  *
  * @throws {@link NamespaceNotFoundException} (client fault)
  *  <p>The specified namespace wasn't found.</p>
@@ -633,12 +638,11 @@ declare const UpdateServiceCommand_base: {
  *  <p>These errors are usually caused by a server issue.</p>
  *
  * @throws {@link ServiceNotActiveException} (client fault)
- *  <p>The specified service isn't active. You can't update a service that's inactive. If you
- * 			have previously deleted a service, you can re-create it with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html">CreateService</a>.</p>
+ *  <p>The specified service isn't active. You can't update a service that's inactive. If you have
+ * 			previously deleted a service, you can re-create it with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html">CreateService</a>.</p>
  *
  * @throws {@link ServiceNotFoundException} (client fault)
- *  <p>The specified service wasn't found. You can view your available services with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a>. Amazon ECS services are cluster specific and Region
- * 			specific.</p>
+ *  <p>The specified service wasn't found. You can view your available services with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a>. Amazon ECS services are cluster specific and Region specific.</p>
  *
  * @throws {@link UnsupportedFeatureException} (client fault)
  *  <p>The specified task isn't supported in this Region.</p>

package/dist-types/commands/UpdateServicePrimaryTaskSetCommand.d.ts

@@ -27,10 +27,9 @@ declare const UpdateServicePrimaryTaskSetCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Modifies which task set in a service is the primary task set. Any parameters that are
- * 			updated on the primary task set in a service will transition to the service. This is
- * 			used when a service uses the <code>EXTERNAL</code> deployment controller type. For more
- * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS Deployment
+ * <p>Modifies which task set in a service is the primary task set. Any parameters that are updated on the
+ * 			primary task set in a service will transition to the service. This is used when a service uses the
+ * 				<code>EXTERNAL</code> deployment controller type. 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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -127,17 +126,16 @@ declare const UpdateServicePrimaryTaskSetCommand_base: {
  *  <p>You don't have authorization to perform the requested action.</p>
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or
+ * 			resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might
+ * 			be specifying an identifier that isn't valid.</p>
  *          <p>The following list includes additional causes for the error:</p>
  *          <ul>
  *             <li>
- *                <p>The <code>RunTask</code> could not be processed because you use managed
- * 					scaling and there is a capacity error because the quota of tasks in the
- * 					<code>PROVISIONING</code> per cluster has been reached. For information
- * 					about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
- * 						service quotas</a>.</p>
+ *                <p>The <code>RunTask</code> could not be processed because you use managed scaling and there is
+ * 					a capacity error because the quota of tasks in the <code>PROVISIONING</code> per cluster has
+ * 					been reached. For information about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service
+ * 						quotas</a>.</p>
  *             </li>
  *          </ul>
  *
@@ -145,23 +143,20 @@ declare const UpdateServicePrimaryTaskSetCommand_base: {
  *  <p>The specified cluster wasn't found. You can view your available clusters with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html">ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API
- * 			request.</p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>
  *
  * @throws {@link ServiceNotActiveException} (client fault)
- *  <p>The specified service isn't active. You can't update a service that's inactive. If you
- * 			have previously deleted a service, you can re-create it with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html">CreateService</a>.</p>
+ *  <p>The specified service isn't active. You can't update a service that's inactive. If you have
+ * 			previously deleted a service, you can re-create it with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html">CreateService</a>.</p>
  *
  * @throws {@link ServiceNotFoundException} (client fault)
- *  <p>The specified service wasn't found. You can view your available services with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a>. Amazon ECS services are cluster specific and Region
- * 			specific.</p>
+ *  <p>The specified service wasn't found. You can view your available services with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a>. Amazon ECS services are cluster specific and Region specific.</p>
  *
  * @throws {@link TaskSetNotFoundException} (client fault)
- *  <p>The specified task set wasn't found. You can view your available task sets with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTaskSets.html">DescribeTaskSets</a>. Task sets are specific to each cluster, service and
- * 			Region.</p>
+ *  <p>The specified task set wasn't found. You can view your available task sets with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTaskSets.html">DescribeTaskSets</a>. Task sets are specific to each cluster, service and Region.</p>
  *
  * @throws {@link UnsupportedFeatureException} (client fault)
  *  <p>The specified task isn't supported in this Region.</p>

package/dist-types/commands/UpdateTaskProtectionCommand.d.ts

@@ -28,31 +28,28 @@ declare const UpdateTaskProtectionCommand_base: {
 };
 /**
  * <p>Updates the protection status of a task. You can set <code>protectionEnabled</code> to
- * 				<code>true</code> to protect your task from termination during scale-in events from
- * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html">Service
+ * 				<code>true</code> to protect your task from termination during scale-in events from <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html">Service
  * 				Autoscaling</a> or <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">deployments</a>.</p>
  *          <p>Task-protection, by default, expires after 2 hours at which point Amazon ECS clears the
- * 				<code>protectionEnabled</code> property making the task eligible for termination by
- * 			a subsequent scale-in event.</p>
- *          <p>You can specify a custom expiration period for task protection from 1 minute to up to
- * 			2,880 minutes (48 hours). To specify the custom expiration period, set the
- * 				<code>expiresInMinutes</code> property. The <code>expiresInMinutes</code> property
- * 			is always reset when you invoke this operation for a task that already has
- * 				<code>protectionEnabled</code> set to <code>true</code>. You can keep extending the
+ * 				<code>protectionEnabled</code> property making the task eligible for termination by a subsequent
+ * 			scale-in event.</p>
+ *          <p>You can specify a custom expiration period for task protection from 1 minute to up to 2,880 minutes
+ * 			(48 hours). To specify the custom expiration period, set the <code>expiresInMinutes</code> property.
+ * 			The <code>expiresInMinutes</code> property is always reset when you invoke this operation for a task
+ * 			that already has <code>protectionEnabled</code> set to <code>true</code>. You can keep extending the
  * 			protection expiration period of a task by invoking this operation repeatedly.</p>
  *          <p>To learn more about Amazon ECS task protection, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection.html">Task scale-in
  * 				protection</a> in the <i>
  *                <i>Amazon Elastic Container Service Developer Guide</i>
  *             </i>.</p>
  *          <note>
- *             <p>This operation is only supported for tasks belonging to an Amazon ECS service. Invoking
- * 				this operation for a standalone task will result in an <code>TASK_NOT_VALID</code>
- * 				failure. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/api_failures_messages.html">API failure
- * 					reasons</a>.</p>
+ *             <p>This operation is only supported for tasks belonging to an Amazon ECS service. Invoking this operation
+ * 				for a standalone task will result in an <code>TASK_NOT_VALID</code> failure. For more information,
+ * 				see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/api_failures_messages.html">API failure reasons</a>.</p>
  *          </note>
  *          <important>
- *             <p>If you prefer to set task protection from within the container, we recommend using
- * 				the <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection-endpoint.html">Task scale-in protection endpoint</a>.</p>
+ *             <p>If you prefer to set task protection from within the container, we recommend using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection-endpoint.html">Task scale-in
+ * 					protection endpoint</a>.</p>
  *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -99,17 +96,16 @@ declare const UpdateTaskProtectionCommand_base: {
  *  <p>You don't have authorization to perform the requested action.</p>
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or
+ * 			resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might
+ * 			be specifying an identifier that isn't valid.</p>
  *          <p>The following list includes additional causes for the error:</p>
  *          <ul>
  *             <li>
- *                <p>The <code>RunTask</code> could not be processed because you use managed
- * 					scaling and there is a capacity error because the quota of tasks in the
- * 					<code>PROVISIONING</code> per cluster has been reached. For information
- * 					about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
- * 						service quotas</a>.</p>
+ *                <p>The <code>RunTask</code> could not be processed because you use managed scaling and there is
+ * 					a capacity error because the quota of tasks in the <code>PROVISIONING</code> per cluster has
+ * 					been reached. For information about the service quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service
+ * 						quotas</a>.</p>
  *             </li>
  *          </ul>
  *
@@ -117,8 +113,7 @@ declare const UpdateTaskProtectionCommand_base: {
  *  <p>The specified cluster wasn't found. You can view your available clusters with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html">ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API
- * 			request.</p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p>
  *
  * @throws {@link ResourceNotFoundException} (client fault)
  *  <p>The specified resource wasn't found.</p>