@aws-sdk/client-ecs 3.703.0 → 3.709.0

package/README.md

@@ -8,17 +8,18 @@ AWS SDK for JavaScript ECS Client for Node.js, Browser and React Native.
 
 <fullname>Amazon Elastic Container Service</fullname>
 
-<p>Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes it easy to run,
-stop, and manage Docker containers. You can host your cluster on a serverless infrastructure that's
-managed by Amazon ECS by launching your services or tasks on Fargate. For more control, you can host your
-tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2) or External (on-premises) instances that you manage.</p>
-<p>Amazon ECS makes it easy to launch and stop container-based applications with simple API calls. This makes
-it easy to get the state of your cluster from a centralized service, and gives you access to many
-familiar Amazon EC2 features.</p>
-<p>You can use Amazon ECS to schedule the placement of containers across your cluster based on your resource
-needs, isolation policies, and availability requirements. With Amazon ECS, you don't need to operate your
-own cluster management and configuration management systems. You also don't need to worry about scaling
-your management infrastructure. </p>
+<p>Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes
+it easy to run, stop, and manage Docker containers. You can host your cluster on a
+serverless infrastructure that's managed by Amazon ECS by launching your services or tasks on
+Fargate. For more control, you can host your tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2)
+or External (on-premises) instances that you manage.</p>
+<p>Amazon ECS makes it easy to launch and stop container-based applications with simple API
+calls. This makes it easy to get the state of your cluster from a centralized service,
+and gives you access to many familiar Amazon EC2 features.</p>
+<p>You can use Amazon ECS to schedule the placement of containers across your cluster based on
+your resource needs, isolation policies, and availability requirements. With Amazon ECS, you
+don't need to operate your own cluster management and configuration management systems.
+You also don't need to worry about scaling your management infrastructure. </p>
 
 ## Installing
 

package/dist-types/ECS.d.ts

@@ -431,17 +431,18 @@ export interface ECS {
 }
 /**
  * <fullname>Amazon Elastic Container Service</fullname>
- *          <p>Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes it easy to run,
- * 			stop, and manage Docker containers. You can host your cluster on a serverless infrastructure that's
- * 			managed by Amazon ECS by launching your services or tasks on Fargate. For more control, you can host your
- * 			tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2) or External (on-premises) instances that you manage.</p>
- *          <p>Amazon ECS makes it easy to launch and stop container-based applications with simple API calls. This makes
- * 			it easy to get the state of your cluster from a centralized service, and gives you access to many
- * 			familiar Amazon EC2 features.</p>
- *          <p>You can use Amazon ECS to schedule the placement of containers across your cluster based on your resource
- * 			needs, isolation policies, and availability requirements. With Amazon ECS, you don't need to operate your
- * 			own cluster management and configuration management systems. You also don't need to worry about scaling
- * 			your management infrastructure. </p>
+ *          <p>Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes
+ * 			it easy to run, stop, and manage Docker containers. You can host your cluster on a
+ * 			serverless infrastructure that's managed by Amazon ECS by launching your services or tasks on
+ * 			Fargate. For more control, you can host your tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2)
+ * 			or External (on-premises) instances that you manage.</p>
+ *          <p>Amazon ECS makes it easy to launch and stop container-based applications with simple API
+ * 			calls. This makes it easy to get the state of your cluster from a centralized service,
+ * 			and gives you access to many familiar Amazon EC2 features.</p>
+ *          <p>You can use Amazon ECS to schedule the placement of containers across your cluster based on
+ * 			your resource needs, isolation policies, and availability requirements. With Amazon ECS, you
+ * 			don't need to operate your own cluster management and configuration management systems.
+ * 			You also don't need to worry about scaling your management infrastructure. </p>
  * @public
  */
 export declare class ECS extends ECSClient implements ECS {

package/dist-types/ECSClient.d.ts

@@ -211,17 +211,18 @@ export interface ECSClientResolvedConfig extends ECSClientResolvedConfigType {
 }
 /**
  * <fullname>Amazon Elastic Container Service</fullname>
- *          <p>Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes it easy to run,
- * 			stop, and manage Docker containers. You can host your cluster on a serverless infrastructure that's
- * 			managed by Amazon ECS by launching your services or tasks on Fargate. For more control, you can host your
- * 			tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2) or External (on-premises) instances that you manage.</p>
- *          <p>Amazon ECS makes it easy to launch and stop container-based applications with simple API calls. This makes
- * 			it easy to get the state of your cluster from a centralized service, and gives you access to many
- * 			familiar Amazon EC2 features.</p>
- *          <p>You can use Amazon ECS to schedule the placement of containers across your cluster based on your resource
- * 			needs, isolation policies, and availability requirements. With Amazon ECS, you don't need to operate your
- * 			own cluster management and configuration management systems. You also don't need to worry about scaling
- * 			your management infrastructure. </p>
+ *          <p>Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes
+ * 			it easy to run, stop, and manage Docker containers. You can host your cluster on a
+ * 			serverless infrastructure that's managed by Amazon ECS by launching your services or tasks on
+ * 			Fargate. For more control, you can host your tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2)
+ * 			or External (on-premises) instances that you manage.</p>
+ *          <p>Amazon ECS makes it easy to launch and stop container-based applications with simple API
+ * 			calls. This makes it easy to get the state of your cluster from a centralized service,
+ * 			and gives you access to many familiar Amazon EC2 features.</p>
+ *          <p>You can use Amazon ECS to schedule the placement of containers across your cluster based on
+ * 			your resource needs, isolation policies, and availability requirements. With Amazon ECS, you
+ * 			don't need to operate your own cluster management and configuration management systems.
+ * 			You also don't need to worry about scaling your management infrastructure. </p>
  * @public
  */
 export declare class ECSClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, ECSClientResolvedConfig> {

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

@@ -27,11 +27,13 @@ declare const CreateCapacityProviderCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a new capacity provider. Capacity providers are associated with an Amazon ECS cluster and are used
- * 			in capacity provider strategies to facilitate cluster auto scaling.</p>
- *          <p>Only capacity providers that use an Auto Scaling group can be created. Amazon ECS tasks on Fargate use
- * 			the <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers. These providers are
- * 			available to all accounts in the Amazon Web Services Regions that Fargate supports.</p>
+ * <p>Creates a new capacity provider. Capacity providers are associated with an Amazon ECS
+ * 			cluster and are used in capacity provider strategies to facilitate cluster auto
+ * 			scaling.</p>
+ *          <p>Only capacity providers that use an Auto Scaling group can be created. Amazon ECS tasks on
+ * 			Fargate use the <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers.
+ * 			These providers are available to all accounts in the Amazon Web Services Regions that Fargate
+ * 			supports.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -98,21 +100,23 @@ declare const CreateCapacityProviderCommand_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>
  *
  * @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 LimitExceededException} (client fault)
  *  <p>The limit for the resource was exceeded.</p>
@@ -121,10 +125,11 @@ declare const CreateCapacityProviderCommand_base: {
  *  <p>These errors are usually caused by a server issue.</p>
  *
  * @throws {@link UpdateInProgressException} (client fault)
- *  <p>There's already a current Amazon ECS container agent update in progress on the container instance that's
- * 			specified. If the container agent becomes disconnected while it's in a transitional stage, such as
- * 				<code>PENDING</code> or <code>STAGING</code>, the update process can get stuck in that state.
- * 			However, when the agent reconnects, it resumes where it stopped previously.</p>
+ *  <p>There's already a current Amazon ECS container agent update in progress on the container
+ * 			instance that's specified. If the container agent becomes disconnected while it's in a
+ * 			transitional stage, such as <code>PENDING</code> or <code>STAGING</code>, the update
+ * 			process can get stuck in that state. However, when the agent reconnects, it resumes
+ * 			where it stopped previously.</p>
  *
  * @throws {@link ECSServiceException}
  * <p>Base exception class for all service exceptions from ECS service.</p>

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

@@ -27,16 +27,16 @@ declare const CreateClusterCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a new Amazon ECS cluster. By default, your account receives a <code>default</code> cluster when
- * 			you launch your first container instance. However, you can create your own cluster with a unique
- * 			name.</p>
+ * <p>Creates a new Amazon ECS cluster. By default, your account receives a <code>default</code>
+ * 			cluster when you launch your first container instance. However, you can create your own
+ * 			cluster with a unique name.</p>
  *          <note>
- *             <p>When you call the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html">CreateCluster</a> API operation,
- * 				Amazon ECS attempts to create the Amazon ECS service-linked role for your account. This is so that it can
- * 				manage required resources in other Amazon Web Services services on your behalf. However, if the user that makes
- * 				the call doesn't have permissions to create the service-linked role, it isn't created. For more
- * 				information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using service-linked
- * 					roles for Amazon ECS</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *             <p>When you call the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html">CreateCluster</a>
+ * 				API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your
+ * 				account. This is so that it can manage required resources in other Amazon Web Services services on
+ * 				your behalf. However, if the user that makes the call doesn't have permissions to
+ * 				create the service-linked role, it isn't created. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
+ * 					service-linked roles for Amazon ECS</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -174,21 +174,23 @@ declare const CreateClusterCommand_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>
  *
  * @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>

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

@@ -27,89 +27,92 @@ declare const CreateServiceCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Runs and maintains your desired number of tasks from a specified task definition. If the number of
- * 			tasks running in a service drops below the <code>desiredCount</code>, Amazon ECS runs another copy of the
- * 			task in the specified cluster. To update an existing service, use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p>
+ * <p>Runs and maintains your desired number of tasks from a specified task definition. If
+ * 			the number of tasks running in a service drops below the <code>desiredCount</code>,
+ * 			Amazon ECS runs another copy of the task in the specified cluster. To update an existing
+ * 			service, use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p>
  *          <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>
  *          <note>
  *             <p>Amazon Elastic Inference (EI) is no longer available to customers.</p>
  *          </note>
- *          <p>In addition to maintaining the desired count of tasks in your service, you can optionally run your
- * 			service behind one or more load balancers. The load balancers distribute traffic across the tasks that
- * 			are associated with the service. For more 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>
- *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a
- * 			service. <code>volumeConfigurations</code> is only supported for REPLICA service and not DAEMON
- * 			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>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>
+ *          <p>In addition to maintaining the desired count of tasks in your service, you can
+ * 			optionally run your service behind one or more load balancers. The load balancers
+ * 			distribute traffic across the tasks that are associated with the service. For more
+ * 			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>
+ *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or
+ * 			updating a service. <code>volumeConfigurations</code> is only supported for REPLICA
+ * 			service and not DAEMON 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>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>
  *          <p>There are two service scheduler strategies available:</p>
  *          <ul>
  *             <li>
  *                <p>
- *                   <code>REPLICA</code> - The replica scheduling strategy places and maintains your
- * 					desired number of tasks across your cluster. By default, the service scheduler spreads tasks
- * 					across Availability Zones. You can use task placement strategies and constraints to customize
- * 					task placement decisions. 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>
+ *                   <code>REPLICA</code> - The replica scheduling strategy places and
+ * 					maintains your desired number of tasks across your cluster. By default, the
+ * 					service scheduler spreads tasks across Availability Zones. You can use task
+ * 					placement strategies and constraints to customize task placement decisions. 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>
  *             </li>
  *             <li>
  *                <p>
- *                   <code>DAEMON</code> - The daemon scheduling strategy deploys exactly one task on each
- * 					active container instance that meets all of the task placement constraints that you specify in
- * 					your cluster. The service scheduler also evaluates the task placement constraints for running
- * 					tasks. It also stops tasks that don't meet the placement constraints. When using this strategy,
- * 					you don't need to specify a desired number of tasks, a task placement strategy, or use 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>
+ *                   <code>DAEMON</code> - The daemon scheduling strategy deploys exactly one
+ * 					task on each active container instance that meets all of the task placement
+ * 					constraints that you specify in your cluster. The service scheduler also
+ * 					evaluates the task placement constraints for running tasks. It also stops tasks
+ * 					that don't meet the placement constraints. When using this strategy, you don't
+ * 					need to specify a desired number of tasks, a task placement strategy, or use
+ * 					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>
  *             </li>
  *          </ul>
- *          <p>You can optionally specify a deployment configuration for your service. The deployment is initiated
- * 			by changing properties. For example, the deployment might be initiated by the task definition or by
- * 			your desired count of a service. You can use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>. The default value for a replica service for
- * 				<code>minimumHealthyPercent</code> is 100%. The default value for a daemon service for
- * 				<code>minimumHealthyPercent</code> is 0%.</p>
- *          <p>If a service uses the <code>ECS</code> deployment controller, the minimum healthy percent represents
- * 			a lower limit on the number of tasks in a service that must remain in the <code>RUNNING</code> state
- * 			during a deployment. Specifically, it represents it as a percentage of your desired number of tasks
- * 			(rounded up to the nearest integer). This happens when any of your container instances are in the
- * 				<code>DRAINING</code> state if the service contains tasks using the EC2 launch type.
- * 			Using this parameter, you can deploy without using additional cluster capacity. For example, if you set
- * 			your service to have desired number of four tasks and a minimum healthy percent of 50%, the scheduler
- * 			might stop two existing tasks to free up cluster capacity before starting two new tasks. If they're in
- * 			the <code>RUNNING</code> state, tasks for services that don't use a load balancer are considered
- * 			healthy . If they're in the <code>RUNNING</code> state and reported as healthy by the load balancer,
- * 			tasks for services that <i>do</i> use a load balancer are considered healthy . The
+ *          <p>You can optionally specify a deployment configuration for your service. The deployment
+ * 			is initiated by changing properties. For example, the deployment might be initiated by
+ * 			the task definition or by your desired count of a service. You can use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>. The default value for a replica service for
+ * 				<code>minimumHealthyPercent</code> is 100%. The default value for a daemon service
+ * 			for <code>minimumHealthyPercent</code> is 0%.</p>
+ *          <p>If a service uses the <code>ECS</code> deployment controller, the minimum healthy
+ * 			percent represents a lower limit on the number of tasks in a service that must remain in
+ * 			the <code>RUNNING</code> state during a deployment. Specifically, it represents it as a
+ * 			percentage of your desired number of tasks (rounded up to the nearest integer). This
+ * 			happens when any of your container instances are in the <code>DRAINING</code> state if
+ * 			the service contains tasks using the EC2 launch type. Using this
+ * 			parameter, you can deploy without using additional cluster capacity. For example, if you
+ * 			set your service to have desired number of four tasks and a minimum healthy percent of
+ * 			50%, the scheduler might stop two existing tasks to free up cluster capacity before
+ * 			starting two new tasks. If they're in the <code>RUNNING</code> state, tasks for services
+ * 			that don't use a load balancer are considered healthy . If they're in the
+ * 				<code>RUNNING</code> state and reported as healthy by the load balancer, tasks for
+ * 			services that <i>do</i> use a load balancer are considered healthy . The
  * 			default value for minimum healthy percent is 100%.</p>
- *          <p>If a service uses the <code>ECS</code> deployment controller, the <b>maximum
- * 				percent</b> parameter represents an upper limit on the number of tasks in a service that are
- * 			allowed in the <code>RUNNING</code> or <code>PENDING</code> state during a deployment. Specifically, it
- * 			represents it as a percentage of the desired number of tasks (rounded down to the nearest integer).
- * 			This happens when any of your container instances are in the <code>DRAINING</code> state if the service
- * 			contains tasks using the EC2 launch type. Using this parameter, you can define the
- * 			deployment batch size. For example, if your service has a desired number of four tasks and a maximum
- * 			percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks
- * 			(provided that the cluster resources required to do this are available). The default value for maximum
- * 			percent is 200%.</p>
- *          <p>If a service uses either the <code>CODE_DEPLOY</code> or <code>EXTERNAL</code> deployment controller
- * 			types and tasks that use the EC2 launch type, the <b>minimum healthy
- * 				percent</b> and <b>maximum percent</b> values are used only to
- * 			define the lower and upper limit on the number of the tasks in the service that remain in the
- * 				<code>RUNNING</code> state. This is while the container instances are in the <code>DRAINING</code>
- * 			state. If the tasks in the service use the Fargate launch type, the minimum healthy
- * 			percent and maximum percent values aren't used. This is the case even if they're currently visible when
- * 			describing your service.</p>
- *          <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you can specify
- * 			only parameters that aren't controlled at the task set level. The only required parameter is the
- * 			service name. You control your services using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. 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>
- *          <p>When the service scheduler launches new tasks, it determines task placement. For information 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>If a service uses the <code>ECS</code> deployment controller, the <b>maximum percent</b> parameter represents an upper limit on the
+ * 			number of tasks in a service that are allowed in the <code>RUNNING</code> or
+ * 				<code>PENDING</code> state during a deployment. Specifically, it represents it as a
+ * 			percentage of the desired number of tasks (rounded down to the nearest integer). This
+ * 			happens when any of your container instances are in the <code>DRAINING</code> state if
+ * 			the service contains tasks using the EC2 launch type. Using this
+ * 			parameter, you can define the deployment batch size. For example, if your service has a
+ * 			desired number of four tasks and a maximum percent value of 200%, the scheduler may
+ * 			start four new tasks before stopping the four older tasks (provided that the cluster
+ * 			resources required to do this are available). The default value for maximum percent is
+ * 			200%.</p>
+ *          <p>If a service uses either the <code>CODE_DEPLOY</code> or <code>EXTERNAL</code>
+ * 			deployment controller types and tasks that use the EC2 launch type, the
+ * 				<b>minimum healthy percent</b> and <b>maximum percent</b> values are used only to define the lower and upper limit
+ * 			on the number of the tasks in the service that remain in the <code>RUNNING</code> state.
+ * 			This is while the container instances are in the <code>DRAINING</code> state. If the
+ * 			tasks in the service use the Fargate launch type, the minimum healthy
+ * 			percent and maximum percent values aren't used. This is the case even if they're
+ * 			currently visible when describing your service.</p>
+ *          <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
+ * 			can specify only parameters that aren't controlled at the task set level. The only
+ * 			required parameter is the service name. You control your services using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. 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>
+ *          <p>When the service scheduler launches new tasks, it determines task placement. For
+ * 			information 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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -574,16 +577,17 @@ declare const CreateServiceCommand_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>
  *
@@ -591,7 +595,8 @@ declare const CreateServiceCommand_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>

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

@@ -27,14 +27,15 @@ declare const CreateTaskSetCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Create a task set in the specified cluster and 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>Create a task set in the specified cluster and 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>
  *          <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 information about the maximum number of task sets and other quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service
- * 				quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <p>For information about the maximum number of task sets and other quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
+ * 				service quotas</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.
  * ```javascript
@@ -178,16 +179,17 @@ declare const CreateTaskSetCommand_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>
  *
@@ -195,7 +197,8 @@ declare const CreateTaskSetCommand_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>
@@ -211,11 +214,12 @@ declare const CreateTaskSetCommand_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/DeleteAccountSettingCommand.d.ts

@@ -27,7 +27,8 @@ declare const DeleteAccountSettingCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Disables an account setting for a specified user, role, or the root user for an account.</p>
+ * <p>Disables an account setting for a specified user, role, or the root user for an
+ * 			account.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -58,21 +59,23 @@ declare const DeleteAccountSettingCommand_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>
  *
  * @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/DeleteAttributesCommand.d.ts

@@ -70,10 +70,12 @@ declare const DeleteAttributesCommand_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 TargetNotFoundException} (client fault)
- *  <p>The specified target wasn't found. You can view your available container instances with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html">ListContainerInstances</a>. Amazon ECS container instances are cluster-specific and
+ *  <p>The specified target wasn't found. You can view your available container instances
+ * 			with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html">ListContainerInstances</a>. Amazon ECS container instances are cluster-specific and
  * 			Region-specific.</p>
  *
  * @throws {@link ECSServiceException}