@aws-sdk/client-ecs 3.40.0 → 3.45.0

package/dist-types/ECSClient.d.ts

@@ -175,18 +175,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 that makes
+ * 		       <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 on a cluster. You can host your
- * 			cluster on a serverless infrastructure that is managed by Amazon ECS by launching 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) instances that you manage.</p>
  * 		       <p>Amazon ECS makes it easy to launch and stop container-based applications with simple API
- * 			calls, allows you to get the state of your cluster from a centralized service, and gives
- * 			you access to many familiar Amazon EC2 features.</p>
+ * 			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. Amazon ECS eliminates
- * 			the need for you to operate your own cluster management and configuration management
- * 			systems or worry about scaling your management infrastructure.</p>
+ * 			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>
  */
 export declare class ECSClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, ECSClientResolvedConfig> {
     /**

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

@@ -10,10 +10,10 @@ export interface CreateCapacityProviderCommandOutput extends CreateCapacityProvi
  * <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 using an Auto Scaling group can be created. Amazon ECS tasks on
- * 			Fargate use the <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers
- * 			which are already created and available to all accounts in Regions supported by
- * 			Fargate.</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
@@ -26,7 +26,7 @@ export interface CreateCapacityProviderCommandOutput extends CreateCapacityProvi
  *
  * @see {@link CreateCapacityProviderCommandInput} for command's `input` shape.
  * @see {@link CreateCapacityProviderCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class CreateCapacityProviderCommand extends $Command<CreateCapacityProviderCommandInput, CreateCapacityProviderCommandOutput, ECSClientResolvedConfig> {

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

@@ -12,10 +12,10 @@ export interface CreateClusterCommandOutput extends CreateClusterResponse, __Met
  * 			cluster with a unique name with the <code>CreateCluster</code> action.</p>
  * 		       <note>
  * 			         <p>When you call the <a>CreateCluster</a> API operation, Amazon ECS attempts to
- * 				create the Amazon ECS service-linked role for your account so that required resources in
- * 				other Amazon Web Services services can be managed on your behalf. However, if the IAM user that
- * 				makes the call does not have permissions to create the service-linked role, it is
- * 				not created. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
+ * 				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 IAM 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>
@@ -31,7 +31,7 @@ export interface CreateClusterCommandOutput extends CreateClusterResponse, __Met
  *
  * @see {@link CreateClusterCommandInput} for command's `input` shape.
  * @see {@link CreateClusterCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class CreateClusterCommand extends $Command<CreateClusterCommandInput, CreateClusterCommandOutput, ECSClientResolvedConfig> {

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

@@ -7,26 +7,25 @@ export interface CreateServiceCommandInput extends CreateServiceRequest {
 export interface CreateServiceCommandOutput extends CreateServiceResponse, __MetadataBearer {
 }
 /**
- * <p>Runs and maintains a 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,
- * 			see the UpdateService action.</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, see the UpdateService action.</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>Tasks for services that <i>do not</i> use a load balancer are considered
- * 			healthy if they're in the <code>RUNNING</code> state. Tasks for services that
- * 				<i>do</i> use a load balancer are considered healthy if they're in the
- * 				<code>RUNNING</code> state and the container instance that they're hosted on is
- * 			reported as healthy by the load balancer.</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 the container
+ * 			instance that they're hosted on is 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 the desired number of tasks across your cluster. By default, the
+ * 					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
@@ -37,50 +36,51 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  *                   <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 and will stop tasks
- * 					that do not meet the placement constraints. When using this strategy, you don't
+ * 					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 triggered by changing properties, such as the task definition or the desired count of
- * 			a service, with an <a>UpdateService</a> operation. 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 is using the <code>ECS</code> deployment controller, the minimum healthy
+ * 			is initiated by changing properties. For example, the deployment might be initiated by
+ * 			the task definition or by your desired count of a service. This is done with an <a>UpdateService</a> operation. 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, as a percentage of the desired
- * 			number of tasks (rounded up to the nearest integer), and while any container instances
- * 			are in the <code>DRAINING</code> state if the service contains tasks using the
- * 			EC2 launch type. This parameter enables you to deploy without using
- * 			additional cluster capacity. For example, if your service has a 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. Tasks for services that
- * 				<i>do not</i> use a load balancer are considered healthy if they're in
- * 			the <code>RUNNING</code> state. Tasks for services that <i>do</i> use a
- * 			load balancer are considered healthy if they're in the <code>RUNNING</code> state and
- * 			they're reported as healthy by the load balancer. The default value for minimum healthy
- * 			percent is 100%.</p>
- * 		       <p>If a service is using the <code>ECS</code> deployment controller, the <b>maximum percent</b> parameter represents an upper limit on the
+ * 			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, as a percentage of the desired
- * 			number of tasks (rounded down to the nearest integer), and while any container instances
- * 			are in the <code>DRAINING</code> state if the service contains tasks using the
- * 			EC2 launch type. This parameter enables you to 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 is using either the <code>CODE_DEPLOY</code> or <code>EXTERNAL</code>
+ * 				<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
- * 			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, although they're currently visible when describing
- * 			your service.</p>
+ * 			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>CreateTaskSet</a> operation. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS Deployment Types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
@@ -88,14 +88,15 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 			cluster using 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 the
+ * 					task definition of your service. 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 (although you can choose a different placement
- * 					strategy) with the <code>placementStrategy</code> parameter):</p>
+ * 					Availability Zones in this manner. This is the case even if you can choose a
+ * 					different placement strategy with the <code>placementStrategy</code>
+ * 					parameter.</p>
  * 				           <ul>
  *                   <li>
  * 						               <p>Sort the valid container instances, giving priority to instances that
@@ -106,7 +107,7 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 					             </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
+ * 							Availability Zone based on the previous steps, favoring container
  * 							instances with the fewest number of running tasks for this
  * 							service.</p>
  * 					             </li>
@@ -125,7 +126,7 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  *
  * @see {@link CreateServiceCommandInput} for command's `input` shape.
  * @see {@link CreateServiceCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class CreateServiceCommand extends $Command<CreateServiceCommandInput, CreateServiceCommandOutput, ECSClientResolvedConfig> {

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

@@ -23,7 +23,7 @@ export interface CreateTaskSetCommandOutput extends CreateTaskSetResponse, __Met
  *
  * @see {@link CreateTaskSetCommandInput} for command's `input` shape.
  * @see {@link CreateTaskSetCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class CreateTaskSetCommand extends $Command<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, ECSClientResolvedConfig> {

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

@@ -21,7 +21,7 @@ export interface DeleteAccountSettingCommandOutput extends DeleteAccountSettingR
  *
  * @see {@link DeleteAccountSettingCommandInput} for command's `input` shape.
  * @see {@link DeleteAccountSettingCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeleteAccountSettingCommand extends $Command<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface DeleteAttributesCommandOutput extends DeleteAttributesResponse,
  *
  * @see {@link DeleteAttributesCommandInput} for command's `input` shape.
  * @see {@link DeleteAttributesCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeleteAttributesCommand extends $Command<DeleteAttributesCommandInput, DeleteAttributesCommandOutput, ECSClientResolvedConfig> {

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

@@ -10,8 +10,8 @@ export interface DeleteCapacityProviderCommandOutput extends DeleteCapacityProvi
  * <p>Deletes the specified capacity provider.</p>
  * 		       <note>
  * 			         <p>The <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers are
- * 				reserved and cannot be deleted. You can disassociate them from a cluster using
- * 				either the <a>PutClusterCapacityProviders</a> API or by deleting the
+ * 				reserved and can't be deleted. You can disassociate them from a cluster using either
+ * 				the <a>PutClusterCapacityProviders</a> API or by deleting the
  * 				cluster.</p>
  * 		       </note>
  * 		       <p>Prior to a capacity provider being deleted, the capacity provider must be removed from
@@ -20,7 +20,7 @@ export interface DeleteCapacityProviderCommandOutput extends DeleteCapacityProvi
  * 			strategy. When updating a service, the <code>forceNewDeployment</code> option can be
  * 			used to ensure that any tasks using the Amazon EC2 instance capacity provided by the capacity
  * 			provider are transitioned to use the capacity from the remaining capacity providers.
- * 			Only capacity providers that are not associated with a cluster can be deleted. To remove
+ * 			Only capacity providers that aren't associated with a cluster can be deleted. To remove
  * 			a capacity provider from a cluster, you can either use <a>PutClusterCapacityProviders</a> or delete the cluster.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -34,7 +34,7 @@ export interface DeleteCapacityProviderCommandOutput extends DeleteCapacityProvi
  *
  * @see {@link DeleteCapacityProviderCommandInput} for command's `input` shape.
  * @see {@link DeleteCapacityProviderCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeleteCapacityProviderCommand extends $Command<DeleteCapacityProviderCommandInput, DeleteCapacityProviderCommandOutput, ECSClientResolvedConfig> {

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

@@ -7,11 +7,10 @@ export interface DeleteClusterCommandInput extends DeleteClusterRequest {
 export interface DeleteClusterCommandOutput extends DeleteClusterResponse, __MetadataBearer {
 }
 /**
- * <p>Deletes the specified cluster. The cluster will transition to the
- * 				<code>INACTIVE</code> state. Clusters with an <code>INACTIVE</code> status may
- * 			remain discoverable in your account for a period of time. However, this behavior is
- * 			subject to change in the future, so you should not rely on <code>INACTIVE</code>
- * 			clusters persisting.</p>
+ * <p>Deletes the specified cluster. The cluster transitions to the <code>INACTIVE</code>
+ * 			state. Clusters with an <code>INACTIVE</code> status might remain discoverable in your
+ * 			account for a period of time. However, this behavior is subject to change in the future.
+ * 			We don't recommend that you rely on <code>INACTIVE</code> clusters persisting.</p>
  * 		       <p>You must deregister all container instances from this cluster before you may delete
  * 			it. You can list the container instances in a cluster with <a>ListContainerInstances</a> and deregister them with <a>DeregisterContainerInstance</a>.</p>
  * @example
@@ -26,7 +25,7 @@ export interface DeleteClusterCommandOutput extends DeleteClusterResponse, __Met
  *
  * @see {@link DeleteClusterCommandInput} for command's `input` shape.
  * @see {@link DeleteClusterCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeleteClusterCommand extends $Command<DeleteClusterCommandInput, DeleteClusterCommandOutput, ECSClientResolvedConfig> {

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

@@ -9,7 +9,7 @@ export interface DeleteServiceCommandOutput extends DeleteServiceResponse, __Met
 /**
  * <p>Deletes a specified service within a cluster. You can delete a service if you have no
  * 			running tasks in it and the desired task count is zero. If the service is actively
- * 			maintaining tasks, you cannot delete it, and you must update the service to a desired
+ * 			maintaining tasks, you can't delete it, and you must update the service to a desired
  * 			task count of zero. For more information, see <a>UpdateService</a>.</p>
  * 		       <note>
  * 			         <p>When you delete a service, if there are still running tasks that require cleanup,
@@ -40,7 +40,7 @@ export interface DeleteServiceCommandOutput extends DeleteServiceResponse, __Met
  *
  * @see {@link DeleteServiceCommandInput} for command's `input` shape.
  * @see {@link DeleteServiceCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeleteServiceCommand extends $Command<DeleteServiceCommandInput, DeleteServiceCommandOutput, ECSClientResolvedConfig> {

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

@@ -21,7 +21,7 @@ export interface DeleteTaskSetCommandOutput extends DeleteTaskSetResponse, __Met
  *
  * @see {@link DeleteTaskSetCommandInput} for command's `input` shape.
  * @see {@link DeleteTaskSetCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeleteTaskSetCommand extends $Command<DeleteTaskSetCommandInput, DeleteTaskSetCommandOutput, ECSClientResolvedConfig> {

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

@@ -10,15 +10,16 @@ export interface DeregisterContainerInstanceCommandOutput extends DeregisterCont
  * <p>Deregisters an Amazon ECS container instance from the specified cluster. This instance is
  * 			no longer available to run tasks.</p>
  * 		       <p>If you intend to use the container instance for some other purpose after
- * 			deregistration, you should stop all of the tasks running on the container instance
- * 			before deregistration. That prevents any orphaned tasks from consuming resources.</p>
- * 		       <p>Deregistering a container instance removes the instance from a cluster, but it does
- * 			not terminate the EC2 instance. If you are finished using the instance, be sure to
- * 			terminate it in the Amazon EC2 console to stop billing.</p>
+ * 			deregistration, we recommend that you stop all of the tasks running on the container
+ * 			instance before deregistration. That prevents any orphaned tasks from consuming
+ * 			resources.</p>
+ * 		       <p>Deregistering a container instance removes the instance from a cluster, but it doesn't
+ * 			terminate the EC2 instance. If you are finished using the instance, be sure to terminate
+ * 			it in the Amazon EC2 console to stop billing.</p>
  * 		       <note>
  * 			         <p>If you terminate a running container instance, Amazon ECS automatically deregisters the
  * 				instance from your cluster (stopped container instances or instances with
- * 				disconnected agents are not automatically deregistered when terminated).</p>
+ * 				disconnected agents aren't automatically deregistered when terminated).</p>
  * 		       </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -32,7 +33,7 @@ export interface DeregisterContainerInstanceCommandOutput extends DeregisterCont
  *
  * @see {@link DeregisterContainerInstanceCommandInput} for command's `input` shape.
  * @see {@link DeregisterContainerInstanceCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeregisterContainerInstanceCommand extends $Command<DeregisterContainerInstanceCommandInput, DeregisterContainerInstanceCommandOutput, ECSClientResolvedConfig> {

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

@@ -12,16 +12,15 @@ export interface DeregisterTaskDefinitionCommandOutput extends DeregisterTaskDef
  * 			reference an <code>INACTIVE</code> task definition continue to run without disruption.
  * 			Existing services that reference an <code>INACTIVE</code> task definition can still
  * 			scale up or down by modifying the service's desired count.</p>
- * 		       <p>You cannot use an <code>INACTIVE</code> task definition to run new tasks or create new
- * 			services, and you cannot update an existing service to reference an
- * 				<code>INACTIVE</code> task definition. However, there may be up to a 10-minute
- * 			window following deregistration where these restrictions have not yet taken
- * 			effect.</p>
+ * 		       <p>You can't use an <code>INACTIVE</code> task definition to run new tasks or create new
+ * 			services, and you can't update an existing service to reference an <code>INACTIVE</code>
+ * 			task definition. However, there may be up to a 10-minute window following deregistration
+ * 			where these restrictions have not yet taken effect.</p>
  * 		       <note>
  * 			         <p>At this time, <code>INACTIVE</code> task definitions remain discoverable in your
- * 				account indefinitely. However, this behavior is subject to change in the future, so
- * 				you should not rely on <code>INACTIVE</code> task definitions persisting beyond the
- * 				lifecycle of any associated tasks and services.</p>
+ * 				account indefinitely. However, this behavior is subject to change in the future. We
+ * 				don't recommend that you rely on <code>INACTIVE</code> task definitions persisting
+ * 				beyond the lifecycle of any associated tasks and services.</p>
  * 		       </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -35,7 +34,7 @@ export interface DeregisterTaskDefinitionCommandOutput extends DeregisterTaskDef
  *
  * @see {@link DeregisterTaskDefinitionCommandInput} for command's `input` shape.
  * @see {@link DeregisterTaskDefinitionCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DeregisterTaskDefinitionCommand extends $Command<DeregisterTaskDefinitionCommandInput, DeregisterTaskDefinitionCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface DescribeCapacityProvidersCommandOutput extends DescribeCapacity
  *
  * @see {@link DescribeCapacityProvidersCommandInput} for command's `input` shape.
  * @see {@link DescribeCapacityProvidersCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeCapacityProvidersCommand extends $Command<DescribeCapacityProvidersCommandInput, DescribeCapacityProvidersCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface DescribeClustersCommandOutput extends DescribeClustersResponse,
  *
  * @see {@link DescribeClustersCommandInput} for command's `input` shape.
  * @see {@link DescribeClustersCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeClustersCommand extends $Command<DescribeClustersCommandInput, DescribeClustersCommandOutput, ECSClientResolvedConfig> {

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

@@ -21,7 +21,7 @@ export interface DescribeContainerInstancesCommandOutput extends DescribeContain
  *
  * @see {@link DescribeContainerInstancesCommandInput} for command's `input` shape.
  * @see {@link DescribeContainerInstancesCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeContainerInstancesCommand extends $Command<DescribeContainerInstancesCommandInput, DescribeContainerInstancesCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface DescribeServicesCommandOutput extends DescribeServicesResponse,
  *
  * @see {@link DescribeServicesCommandInput} for command's `input` shape.
  * @see {@link DescribeServicesCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeServicesCommand extends $Command<DescribeServicesCommandInput, DescribeServicesCommandOutput, ECSClientResolvedConfig> {

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

@@ -27,7 +27,7 @@ export interface DescribeTaskDefinitionCommandOutput extends DescribeTaskDefinit
  *
  * @see {@link DescribeTaskDefinitionCommandInput} for command's `input` shape.
  * @see {@link DescribeTaskDefinitionCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeTaskDefinitionCommand extends $Command<DescribeTaskDefinitionCommandInput, DescribeTaskDefinitionCommandOutput, ECSClientResolvedConfig> {

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

@@ -23,7 +23,7 @@ export interface DescribeTaskSetsCommandOutput extends DescribeTaskSetsResponse,
  *
  * @see {@link DescribeTaskSetsCommandInput} for command's `input` shape.
  * @see {@link DescribeTaskSetsCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeTaskSetsCommand extends $Command<DescribeTaskSetsCommandInput, DescribeTaskSetsCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface DescribeTasksCommandOutput extends DescribeTasksResponse, __Met
  *
  * @see {@link DescribeTasksCommandInput} for command's `input` shape.
  * @see {@link DescribeTasksCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DescribeTasksCommand extends $Command<DescribeTasksCommandInput, DescribeTasksCommandOutput, ECSClientResolvedConfig> {

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

@@ -10,8 +10,7 @@ export interface DiscoverPollEndpointCommandOutput extends DiscoverPollEndpointR
  * <note>
  *             <p>This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.</p>
  *          </note>
- *          <p>Returns an endpoint for
- * 			the Amazon ECS agent to poll for updates.</p>
+ * 		       <p>Returns an endpoint for the Amazon ECS agent to poll for updates.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -24,7 +23,7 @@ export interface DiscoverPollEndpointCommandOutput extends DiscoverPollEndpointR
  *
  * @see {@link DiscoverPollEndpointCommandInput} for command's `input` shape.
  * @see {@link DiscoverPollEndpointCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class DiscoverPollEndpointCommand extends $Command<DiscoverPollEndpointCommandInput, DiscoverPollEndpointCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface ExecuteCommandCommandOutput extends ExecuteCommandResponse, __M
  *
  * @see {@link ExecuteCommandCommandInput} for command's `input` shape.
  * @see {@link ExecuteCommandCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class ExecuteCommandCommand extends $Command<ExecuteCommandCommandInput, ExecuteCommandCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface ListAccountSettingsCommandOutput extends ListAccountSettingsRes
  *
  * @see {@link ListAccountSettingsCommandInput} for command's `input` shape.
  * @see {@link ListAccountSettingsCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class ListAccountSettingsCommand extends $Command<ListAccountSettingsCommandInput, ListAccountSettingsCommandOutput, ECSClientResolvedConfig> {

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

@@ -11,9 +11,9 @@ export interface ListAttributesCommandOutput extends ListAttributesResponse, __M
  * 			When you specify a target type and cluster, <code>ListAttributes</code> returns a list
  * 			of attribute objects, one for each attribute on each resource. You can filter the list
  * 			of results to a single attribute name to only return results that have that name. You
- * 			can also filter the results by attribute name and value, for example, to see which
- * 			container instances in a cluster are running a Linux AMI
- * 			(<code>ecs.os-type=linux</code>). </p>
+ * 			can also filter the results by attribute name and value. You can do this, for example,
+ * 			to see which container instances in a cluster are running a Linux AMI
+ * 				(<code>ecs.os-type=linux</code>). </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -26,7 +26,7 @@ export interface ListAttributesCommandOutput extends ListAttributesResponse, __M
  *
  * @see {@link ListAttributesCommandInput} for command's `input` shape.
  * @see {@link ListAttributesCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class ListAttributesCommand extends $Command<ListAttributesCommandInput, ListAttributesCommandOutput, ECSClientResolvedConfig> {

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

@@ -20,7 +20,7 @@ export interface ListClustersCommandOutput extends ListClustersResponse, __Metad
  *
  * @see {@link ListClustersCommandInput} for command's `input` shape.
  * @see {@link ListClustersCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class ListClustersCommand extends $Command<ListClustersCommandInput, ListClustersCommandOutput, ECSClientResolvedConfig> {

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

@@ -23,7 +23,7 @@ export interface ListContainerInstancesCommandOutput extends ListContainerInstan
  *
  * @see {@link ListContainerInstancesCommandInput} for command's `input` shape.
  * @see {@link ListContainerInstancesCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class ListContainerInstancesCommand extends $Command<ListContainerInstancesCommandInput, ListContainerInstancesCommandOutput, ECSClientResolvedConfig> {

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

@@ -21,7 +21,7 @@ export interface ListServicesCommandOutput extends ListServicesResponse, __Metad
  *
  * @see {@link ListServicesCommandInput} for command's `input` shape.
  * @see {@link ListServicesCommandOutput} for command's `response` shape.
- * @see {@link ECSClientResolvedConfig | config} for command's `input` shape.
+ * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  */
 export declare class ListServicesCommand extends $Command<ListServicesCommandInput, ListServicesCommandOutput, ECSClientResolvedConfig> {