@aws-sdk/client-ecs 3.231.0 → 3.232.0

package/dist-types/ECSClient.d.ts

@@ -179,15 +179,15 @@ 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
+ *          <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
+ *          <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
+ *          <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>

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

@@ -11,7 +11,7 @@ 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 that use an Auto Scaling group can be created. Amazon ECS tasks on
+ *          <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>

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

@@ -11,14 +11,14 @@ export interface CreateClusterCommandOutput extends CreateClusterResponse, __Met
  * <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 with the <code>CreateCluster</code> action.</p>
- * 		       <note>
- * 			         <p>When you call the <a>CreateCluster</a> API operation, Amazon ECS attempts to
+ *          <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. 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>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -12,26 +12,26 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 			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 <a>UpdateService</a> action.</p>
- * 		       <p>In addition to maintaining the desired count of tasks in your service, you can
+ *          <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 don't use a load balancer are considered healthy if they're in
+ *          <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>
+ *          <p>There are two service scheduler strategies available:</p>
+ *          <ul>
  *             <li>
- * 				           <p>
+ *                <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>
  *             <li>
- * 				           <p>
+ *                <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
@@ -39,14 +39,14 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 					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>
+ *             </li>
  *          </ul>
- * 		       <p>You can optionally specify a deployment configuration for your service. The deployment
+ *          <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. 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
+ *          <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
@@ -60,7 +60,7 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 				<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
+ *          <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
@@ -71,7 +71,7 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 			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>
+ *          <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.
@@ -79,10 +79,10 @@ export interface CreateServiceCommandOutput extends CreateServiceResponse, __Met
  * 			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
+ *          <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>
- * 		       <p>When the service scheduler launches new tasks, it determines task placement. For
+ *          <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

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

@@ -9,13 +9,13 @@ 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
+ *          <note>
+ *             <p>The <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers are
  * 				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
+ *          </note>
+ *          <p>Prior to a capacity provider being deleted, the capacity provider must be removed from
  * 			the capacity provider strategy from all services. The <a>UpdateService</a>
  * 			API can be used to remove a capacity provider from a service's capacity provider
  * 			strategy. When updating a service, the <code>forceNewDeployment</code> option can be

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

@@ -12,7 +12,7 @@ export interface DeleteClusterCommandOutput extends DeleteClusterResponse, __Met
  * 			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
+ *          <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
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -12,8 +12,8 @@ export interface DeleteServiceCommandOutput extends DeleteServiceResponse, __Met
  * 			running tasks in it and the desired task count is zero. If the service is actively
  * 			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,
+ *          <note>
+ *             <p>When you delete a service, if there are still running tasks that require cleanup,
  * 				the service status moves from <code>ACTIVE</code> to <code>DRAINING</code>, and the
  * 				service is no longer visible in the console or in the <a>ListServices</a>
  * 				API operation. After all tasks have transitioned to either <code>STOPPING</code> or
@@ -23,12 +23,12 @@ export interface DeleteServiceCommandOutput extends DeleteServiceResponse, __Met
  * 					<code>INACTIVE</code> services may be cleaned up and purged from Amazon ECS record
  * 				keeping, and <a>DescribeServices</a> calls on those services return a
  * 					<code>ServiceNotFoundException</code> error.</p>
- * 		       </note>
- * 		       <important>
- * 			         <p>If you attempt to create a new service with the same name as an existing service
+ *          </note>
+ *          <important>
+ *             <p>If you attempt to create a new service with the same name as an existing service
  * 				in either <code>ACTIVE</code> or <code>DRAINING</code> status, you receive an
  * 				error.</p>
- * 		       </important>
+ *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -10,18 +10,18 @@ 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
+ *          <p>If you intend to use the container instance for some other purpose after
  * 			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
+ *          <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
+ *          <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 aren't automatically deregistered when terminated).</p>
- * 		       </note>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -13,16 +13,16 @@ 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 can't use an <code>INACTIVE</code> task definition to run new tasks or create new
+ *          <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
+ *          <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. 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>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -12,10 +12,10 @@ export interface DescribeTaskDefinitionCommandOutput extends DescribeTaskDefinit
  * 				<code>revision</code> to find information about a specific task definition, or you
  * 			can simply specify the family to find the latest <code>ACTIVE</code> revision in that
  * 			family.</p>
- * 		       <note>
- * 			         <p>You can only describe <code>INACTIVE</code> task definitions while an active task
+ *          <note>
+ *             <p>You can only describe <code>INACTIVE</code> task definitions while an active task
  * 				or service references them.</p>
- * 		       </note>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -9,7 +9,7 @@ export interface DescribeTasksCommandOutput extends DescribeTasksResponse, __Met
 }
 /**
  * <p>Describes a specified task or tasks.</p>
- * 		       <p>Currently, stopped tasks appear in the returned results for at least one hour.</p>
+ *          <p>Currently, stopped tasks appear in the returned results for at least one hour.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -11,7 +11,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

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

@@ -9,10 +9,12 @@ export interface ExecuteCommandCommandOutput extends ExecuteCommandResponse, __M
 }
 /**
  * <p>Runs a command remotely on a container within a task.</p>
- * 		       <p>If you use a condition key in your IAM policy to refine the conditions for the policy
+ *          <p>If you use a condition key in your IAM policy to refine the conditions for the policy
  * 			statement, for example limit the actions to a specific cluster, you receive an
  * 				<code>AccessDeniedException</code> when there is a mismatch between the condition
  * 			key value and the corresponding parameter value.</p>
+ *          <p>For information about required permissions and considerations, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.htm">Using Amazon ECS Exec for
+ * 			debugging</a> in the <i>Amazon ECS Developer Guide</i>. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -11,7 +11,7 @@ export interface ListTaskDefinitionFamiliesCommandOutput extends ListTaskDefinit
  * <p>Returns a list of task definition families that are registered to your account. This
  * 			list includes task definition families that no longer have any <code>ACTIVE</code> task
  * 			definition revisions.</p>
- * 		       <p>You can filter out task definition families that don't contain any <code>ACTIVE</code>
+ *          <p>You can filter out task definition families that don't contain any <code>ACTIVE</code>
  * 			task definition revisions by setting the <code>status</code> parameter to
  * 				<code>ACTIVE</code>. You can also filter the results with the
  * 				<code>familyPrefix</code> parameter.</p>

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

@@ -11,7 +11,7 @@ export interface ListTasksCommandOutput extends ListTasksResponse, __MetadataBea
  * <p>Returns a list of tasks. You can filter the results by cluster, task definition
  * 			family, container instance, launch type, what IAM principal started the task, or by the
  * 			desired status of the task.</p>
- * 		       <p>Recently stopped tasks might appear in the returned results. Currently, stopped tasks
+ *          <p>Recently stopped tasks might appear in the returned results. Currently, stopped tasks
  * 			appear in the returned results for at least one hour.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -9,24 +9,24 @@ export interface PutAccountSettingCommandOutput extends PutAccountSettingRespons
 }
 /**
  * <p>Modifies an account setting. Account settings are set on a per-Region basis.</p>
- * 		       <p>If you change the account setting for the root user, the default settings for all of
+ *          <p>If you change the account setting for the root user, the default settings for all of
  * 			the IAM users and roles that no individual account setting was specified are reset for.
  * 			For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html">Account
  * 				Settings</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       <p>When <code>serviceLongArnFormat</code>, <code>taskLongArnFormat</code>, or
+ *          <p>When <code>serviceLongArnFormat</code>, <code>taskLongArnFormat</code>, or
  * 				<code>containerInstanceLongArnFormat</code> are specified, the Amazon Resource Name
  * 			(ARN) and resource ID format of the resource type for a specified IAM user, IAM role, or
  * 			the root user for an account is affected. The opt-in and opt-out account setting must be
  * 			set for each Amazon ECS resource separately. The ARN and resource ID format of a resource
  * 			is defined by the opt-in status of the IAM user or role that created the resource. You
  * 			must turn on this setting to use Amazon ECS features such as resource tagging.</p>
- * 		       <p>When <code>awsvpcTrunking</code> is specified, the elastic network interface (ENI)
+ *          <p>When <code>awsvpcTrunking</code> is specified, the elastic network interface (ENI)
  * 			limit for any new container instances that support the feature is changed. If
  * 				<code>awsvpcTrunking</code> is enabled, any new container instances that support the
  * 			feature are launched have the increased ENI limits available to them. For more
  * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-instance-eni.html">Elastic Network
  * 				Interface Trunking</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       <p>When <code>containerInsights</code> is specified, the default setting indicating
+ *          <p>When <code>containerInsights</code> is specified, the default setting indicating
  * 			whether CloudWatch Container Insights is enabled for your clusters is changed. If
  * 				<code>containerInsights</code> is enabled, any new clusters that are created will
  * 			have Container Insights enabled unless you disable it during cluster creation. For more

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

@@ -10,14 +10,14 @@ export interface PutClusterCapacityProvidersCommandOutput extends PutClusterCapa
 /**
  * <p>Modifies the available capacity providers and the default capacity provider strategy
  * 			for a cluster.</p>
- * 		       <p>You must specify both the available capacity providers and a default capacity provider
+ *          <p>You must specify both the available capacity providers and a default capacity provider
  * 			strategy for the cluster. If the specified cluster has existing capacity providers
  * 			associated with it, you must specify all existing capacity providers in addition to any
  * 			new ones you want to add. Any existing capacity providers that are associated with a
  * 			cluster that are omitted from a <a>PutClusterCapacityProviders</a> API call
  * 			will be disassociated with the cluster. You can only disassociate an existing capacity
  * 			provider from a cluster if it's not being used by any existing tasks.</p>
- * 		       <p>When creating a service or running a task on a cluster, if no capacity provider or
+ *          <p>When creating a service or running a task on a cluster, if no capacity provider or
  * 			launch type is specified, then the cluster's default capacity provider strategy is used.
  * 			We recommend that you define a default capacity provider strategy for your cluster.
  * 			However, you must specify an empty array (<code>[]</code>) to bypass defining a default

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

@@ -11,7 +11,7 @@ export interface RegisterContainerInstanceCommandOutput extends RegisterContaine
  * <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>Registers an EC2 instance into the specified cluster. This instance becomes available
+ *          <p>Registers an EC2 instance into the specified cluster. This instance becomes available
  * 			to place containers on.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -13,12 +13,12 @@ export interface RegisterTaskDefinitionCommandOutput extends RegisterTaskDefinit
  * 			containers with the <code>volumes</code> parameter. For more information about task
  * 			definition parameters and defaults, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html">Amazon ECS Task
  * 				Definitions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       <p>You can specify an IAM role for your task with the <code>taskRoleArn</code> parameter.
+ *          <p>You can specify an IAM role for your task with the <code>taskRoleArn</code> parameter.
  * 			When you specify an IAM role for a task, its containers can then use the latest versions
  * 			of the CLI or SDKs to make API requests to the Amazon Web Services services that are specified in
  * 			the IAM policy that's associated with the role. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html">IAM
  * 				Roles for Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       <p>You can specify a Docker networking mode for the containers in your task definition
+ *          <p>You can specify a Docker networking mode for the containers in your task definition
  * 			with the <code>networkMode</code> parameter. The available network modes correspond to
  * 			those described in <a href="https://docs.docker.com/engine/reference/run/#/network-settings">Network
  * 				settings</a> in the Docker run reference. If you specify the <code>awsvpc</code>

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

@@ -9,32 +9,32 @@ export interface RunTaskCommandOutput extends RunTaskResponse, __MetadataBearer
 }
 /**
  * <p>Starts a new task using the specified task definition.</p>
- * 		       <p>You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places
+ *          <p>You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places
  * 			tasks using placement constraints and placement strategies. For more information, see
  * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       <p>Alternatively, you can use <a>StartTask</a> to use your own scheduler or
+ *          <p>Alternatively, you can use <a>StartTask</a> to use your own scheduler or
  * 			place tasks manually on specific container instances.</p>
- * 		       <p>The Amazon ECS API follows an eventual consistency model. This is because of the
+ *          <p>The Amazon ECS API follows an eventual consistency model. This is because of the
  * 			distributed nature of the system supporting the API. This means that the result of an
  * 			API command you run that affects your Amazon ECS resources might not be immediately visible
  * 			to all subsequent commands you run. Keep this in mind when you carry out an API command
  * 			that immediately follows a previous API command.</p>
- * 		       <p>To manage eventual consistency, you can do the following:</p>
- * 		       <ul>
+ *          <p>To manage eventual consistency, you can do the following:</p>
+ *          <ul>
  *             <li>
- * 				           <p>Confirm the state of the resource before you run a command to modify it. Run
+ *                <p>Confirm the state of the resource before you run a command to modify it. Run
  * 					the DescribeTasks command using an exponential backoff algorithm to ensure that
  * 					you allow enough time for the previous command to propagate through the system.
  * 					To do this, run the DescribeTasks command repeatedly, starting with a couple of
  * 					seconds of wait time and increasing gradually up to five minutes of wait
  * 					time.</p>
- * 			         </li>
+ *             </li>
  *             <li>
- * 				           <p>Add wait time between subsequent commands, even if the DescribeTasks command
+ *                <p>Add wait time between subsequent commands, even if the DescribeTasks command
  * 					returns an accurate response. Apply an exponential backoff algorithm starting
  * 					with a couple of seconds of wait time, and increase gradually up to about five
  * 					minutes of wait time.</p>
- * 			         </li>
+ *             </li>
  *          </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -10,7 +10,7 @@ export interface StartTaskCommandOutput extends StartTaskResponse, __MetadataBea
 /**
  * <p>Starts a new task from the specified task definition on the specified container
  * 			instance or instances.</p>
- * 		       <p>Alternatively, you can use <a>RunTask</a> to place tasks for you. For more
+ *          <p>Alternatively, you can use <a>RunTask</a> to place tasks for you. For more
  * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -9,18 +9,18 @@ export interface StopTaskCommandOutput extends StopTaskResponse, __MetadataBeare
 }
 /**
  * <p>Stops a running task. Any tags associated with the task will be deleted.</p>
- * 		       <p>When <a>StopTask</a> is called on a task, the equivalent of <code>docker
+ *          <p>When <a>StopTask</a> is called on a task, the equivalent of <code>docker
  * 				stop</code> is issued to the containers running in the task. This results in a
  * 				<code>SIGTERM</code> value and a default 30-second timeout, after which the
  * 				<code>SIGKILL</code> value is sent and the containers are forcibly stopped. If the
  * 			container handles the <code>SIGTERM</code> value gracefully and exits within 30 seconds
  * 			from receiving it, no <code>SIGKILL</code> value is sent.</p>
- * 		       <note>
- * 			         <p>The default 30-second timeout can be configured on the Amazon ECS container agent with
+ *          <note>
+ *             <p>The default 30-second timeout can be configured on the Amazon ECS container agent with
  * 				the <code>ECS_CONTAINER_STOP_TIMEOUT</code> variable. For more information, see
  * 					<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html">Amazon ECS Container Agent Configuration</a> in the
  * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       </note>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -11,7 +11,7 @@ export interface SubmitAttachmentStateChangesCommandOutput extends SubmitAttachm
  * <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>Sent to acknowledge that an attachment changed states.</p>
+ *          <p>Sent to acknowledge that an attachment changed states.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -11,7 +11,7 @@ export interface SubmitContainerStateChangeCommandOutput extends SubmitContainer
  * <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>Sent to acknowledge that a container changed states.</p>
+ *          <p>Sent to acknowledge that a container changed states.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -11,7 +11,7 @@ export interface SubmitTaskStateChangeCommandOutput extends SubmitTaskStateChang
  * <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>Sent to acknowledge that a task changed states.</p>
+ *          <p>Sent to acknowledge that a task changed states.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -12,19 +12,19 @@ export interface UpdateContainerAgentCommandOutput extends UpdateContainerAgentR
  * 			Amazon ECS container agent doesn't interrupt running tasks or services on the container
  * 			instance. The process for updating the agent differs depending on whether your container
  * 			instance was launched with the Amazon ECS-optimized AMI or another operating system.</p>
- * 		       <note>
- * 			         <p>The <code>UpdateContainerAgent</code> API isn't supported for container instances
+ *          <note>
+ *             <p>The <code>UpdateContainerAgent</code> API isn't supported for container instances
  * 				using the Amazon ECS-optimized Amazon Linux 2 (arm64) AMI. To update the container agent,
  * 				you can update the <code>ecs-init</code> package. This updates the agent. For more
  * 				information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/agent-update-ecs-ami.html">Updating the
  * 					Amazon ECS container agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       </note>
- * 		       <note>
- * 			         <p>Agent updates with the <code>UpdateContainerAgent</code> API operation do not
+ *          </note>
+ *          <note>
+ *             <p>Agent updates with the <code>UpdateContainerAgent</code> API operation do not
  * 				apply to Windows container instances. We recommend that you launch new container
  * 				instances to update the agent version in your Windows clusters.</p>
- * 		       </note>
- * 		       <p>The <code>UpdateContainerAgent</code> API requires an Amazon ECS-optimized AMI or Amazon
+ *          </note>
+ *          <p>The <code>UpdateContainerAgent</code> API requires an Amazon ECS-optimized AMI or Amazon
  * 			Linux AMI with the <code>ecs-init</code> service installed and running. For help
  * 			updating the Amazon ECS container agent on other operating systems, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html#manually_update_agent">Manually updating the Amazon ECS container agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * @example

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

@@ -9,27 +9,27 @@ export interface UpdateContainerInstancesStateCommandOutput extends UpdateContai
 }
 /**
  * <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
+ *          <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
+ *          <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>
- * 		       </important>
- * 		       <p>When you set a container instance to <code>DRAINING</code>, Amazon ECS prevents new tasks
+ *          </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
+ *          <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>UpdateService</a>.</p>
- * 		       <ul>
+ *          <ul>
  *             <li>
- * 				           <p>If <code>minimumHealthyPercent</code> is below 100%, the scheduler can ignore
+ *                <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
@@ -39,22 +39,22 @@ export interface UpdateContainerInstancesStateCommandOutput extends UpdateContai
  * 					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>
  *             <li>
- * 				           <p>The <code>maximumPercent</code> parameter represents an upper limit on the
+ *                <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>
+ *             </li>
  *          </ul>
- * 		       <p>Any <code>PENDING</code> or <code>RUNNING</code> tasks that do not belong to a service
+ *          <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>
+ *          <p>A container instance has completed draining when it has no more <code>RUNNING</code>
  * 			tasks. You can verify this using <a>ListTasks</a>.</p>
- * 		       <p>When a container instance has been drained, you can set a container instance to
+ *          <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