@aws-sdk/client-ecs 3.699.0 → 3.708.0

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

@@ -53,16 +53,17 @@ declare const UntagResourceCommand_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>
  *
@@ -70,7 +71,8 @@ declare const UntagResourceCommand_base: {
  *  <p>The specified cluster wasn't found. You can view your available clusters with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html">ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API
+ * 			request.</p>
  *
  * @throws {@link ResourceNotFoundException} (client fault)
  *  <p>The specified resource wasn't found.</p>

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

@@ -87,21 +87,23 @@ declare const UpdateCapacityProviderCommand_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/UpdateClusterCommand.d.ts

@@ -148,16 +148,17 @@ declare const UpdateClusterCommand_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>
  *
@@ -165,7 +166,8 @@ declare const UpdateClusterCommand_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/UpdateClusterSettingsCommand.d.ts

@@ -128,16 +128,17 @@ declare const UpdateClusterSettingsCommand_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>
  *
@@ -145,7 +146,8 @@ declare const UpdateClusterSettingsCommand_base: {
  *  <p>The specified cluster wasn't found. You can view your available clusters with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html">ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API
+ * 			request.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

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

@@ -27,25 +27,25 @@ declare const UpdateContainerAgentCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Updates the Amazon ECS container agent on a specified container instance. Updating the 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>
+ * <p>Updates the Amazon ECS container agent on a specified container instance. Updating the
+ * 			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 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>
+ *             <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 apply to Windows
- * 				container instances. We recommend that you launch new container instances to update the agent
- * 				version in your Windows clusters.</p>
+ *             <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 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>
+ *          <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
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -150,16 +150,17 @@ declare const UpdateContainerAgentCommand_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>
  *
@@ -167,26 +168,29 @@ declare const UpdateContainerAgentCommand_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 MissingVersionException} (client fault)
- *  <p>Amazon ECS can't determine the current version of the Amazon ECS container agent on the container instance and
- * 			doesn't have enough information to proceed with an update. This could be because the agent running on
- * 			the container instance is a previous or custom version that doesn't use our version information.</p>
+ *  <p>Amazon ECS can't determine the current version of the Amazon ECS container agent on the
+ * 			container instance and doesn't have enough information to proceed with an update. This
+ * 			could be because the agent running on the container instance is a previous or custom
+ * 			version that doesn't use our version information.</p>
  *
  * @throws {@link NoUpdateAvailableException} (client fault)
- *  <p>There's no update available for this Amazon ECS container agent. This might be because the agent is
- * 			already running the latest version or because it's so old that there's no update path to the current
- * 			version.</p>
+ *  <p>There's no update available for this Amazon ECS container agent. This might be because the
+ * 			agent is already running the latest version or because it's so old that there's no
+ * 			update path to the current version.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <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/UpdateContainerInstancesStateCommand.d.ts

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