@aws-sdk/client-ecs 3.994.0 → 3.995.0

package/dist-es/schemas/schemas_0.js

@@ -2910,7 +2910,7 @@ var FirelensConfigurationOptionsMap = 128 | 0;
 var LogConfigurationOptionsMap = 128 | 0;
 var StringMap = 128 | 0;
 export var CreateCapacityProvider$ = [9, n0, _CCP,
-    0, () => CreateCapacityProviderRequest$, () => CreateCapacityProviderResponse$
+    2, () => CreateCapacityProviderRequest$, () => CreateCapacityProviderResponse$
 ];
 export var CreateCluster$ = [9, n0, _CCr,
     0, () => CreateClusterRequest$, () => CreateClusterResponse$
@@ -2931,22 +2931,22 @@ export var DeleteAttributes$ = [9, n0, _DAe,
     0, () => DeleteAttributesRequest$, () => DeleteAttributesResponse$
 ];
 export var DeleteCapacityProvider$ = [9, n0, _DCP,
-    0, () => DeleteCapacityProviderRequest$, () => DeleteCapacityProviderResponse$
+    2, () => DeleteCapacityProviderRequest$, () => DeleteCapacityProviderResponse$
 ];
 export var DeleteCluster$ = [9, n0, _DCel,
-    0, () => DeleteClusterRequest$, () => DeleteClusterResponse$
+    2, () => DeleteClusterRequest$, () => DeleteClusterResponse$
 ];
 export var DeleteExpressGatewayService$ = [9, n0, _DEGS,
     0, () => DeleteExpressGatewayServiceRequest$, () => DeleteExpressGatewayServiceResponse$
 ];
 export var DeleteService$ = [9, n0, _DS,
-    0, () => DeleteServiceRequest$, () => DeleteServiceResponse$
+    2, () => DeleteServiceRequest$, () => DeleteServiceResponse$
 ];
 export var DeleteTaskDefinitions$ = [9, n0, _DTD,
     0, () => DeleteTaskDefinitionsRequest$, () => DeleteTaskDefinitionsResponse$
 ];
 export var DeleteTaskSet$ = [9, n0, _DTS,
-    0, () => DeleteTaskSetRequest$, () => DeleteTaskSetResponse$
+    2, () => DeleteTaskSetRequest$, () => DeleteTaskSetResponse$
 ];
 export var DeregisterContainerInstance$ = [9, n0, _DCI,
     0, () => DeregisterContainerInstanceRequest$, () => DeregisterContainerInstanceResponse$

package/dist-es/waiters/waitForServicesInactive.js

@@ -42,11 +42,11 @@ const checkState = async (client, input) => {
     return { state: WaiterState.RETRY, reason };
 };
 export const waitForServicesInactive = async (params, input) => {
-    const serviceDefaults = { minDelay: 15, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 15, maxDelay: 600 };
     return createWaiter({ ...serviceDefaults, ...params }, input, checkState);
 };
 export const waitUntilServicesInactive = async (params, input) => {
-    const serviceDefaults = { minDelay: 15, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 15, maxDelay: 600 };
     const result = await createWaiter({ ...serviceDefaults, ...params }, input, checkState);
     return checkExceptions(result);
 };

package/dist-es/waiters/waitForServicesStable.js

@@ -69,11 +69,11 @@ const checkState = async (client, input) => {
     return { state: WaiterState.RETRY, reason };
 };
 export const waitForServicesStable = async (params, input) => {
-    const serviceDefaults = { minDelay: 15, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 15, maxDelay: 600 };
     return createWaiter({ ...serviceDefaults, ...params }, input, checkState);
 };
 export const waitUntilServicesStable = async (params, input) => {
-    const serviceDefaults = { minDelay: 15, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 15, maxDelay: 600 };
     const result = await createWaiter({ ...serviceDefaults, ...params }, input, checkState);
     return checkExceptions(result);
 };

package/dist-es/waiters/waitForTasksRunning.js

@@ -59,11 +59,11 @@ const checkState = async (client, input) => {
     return { state: WaiterState.RETRY, reason };
 };
 export const waitForTasksRunning = async (params, input) => {
-    const serviceDefaults = { minDelay: 6, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 6, maxDelay: 600 };
     return createWaiter({ ...serviceDefaults, ...params }, input, checkState);
 };
 export const waitUntilTasksRunning = async (params, input) => {
-    const serviceDefaults = { minDelay: 6, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 6, maxDelay: 600 };
     const result = await createWaiter({ ...serviceDefaults, ...params }, input, checkState);
     return checkExceptions(result);
 };

package/dist-es/waiters/waitForTasksStopped.js

@@ -29,11 +29,11 @@ const checkState = async (client, input) => {
     return { state: WaiterState.RETRY, reason };
 };
 export const waitForTasksStopped = async (params, input) => {
-    const serviceDefaults = { minDelay: 6, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 6, maxDelay: 600 };
     return createWaiter({ ...serviceDefaults, ...params }, input, checkState);
 };
 export const waitUntilTasksStopped = async (params, input) => {
-    const serviceDefaults = { minDelay: 6, maxDelay: 120 };
+    const serviceDefaults = { minDelay: 6, maxDelay: 600 };
     const result = await createWaiter({ ...serviceDefaults, ...params }, input, checkState);
     return checkExceptions(result);
 };

package/dist-types/ECS.d.ts

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

package/dist-types/ECSClient.d.ts

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

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

@@ -27,10 +27,7 @@ declare const CreateCapacityProviderCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a capacity provider. Capacity providers are associated with a cluster and are
- * 			used in capacity provider strategies to facilitate cluster auto scaling. You can create
- * 			capacity providers for Amazon ECS Managed Instances and EC2 instances. Fargate has the
- * 			predefined <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers.</p>
+ * <p>Creates a capacity provider. Capacity providers are associated with a cluster and are used in capacity provider strategies to facilitate cluster auto scaling. You can create capacity providers for Amazon ECS Managed Instances and EC2 instances. Fargate has the predefined <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -288,18 +285,13 @@ declare const CreateCapacityProviderCommand_base: {
  * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.</p>
  *
  * @throws {@link ClusterNotFoundException} (client fault)
  *  <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>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
- * 				service event messages</a>. </p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p> <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service event messages</a>. </p>
  *
  * @throws {@link LimitExceededException} (client fault)
  *  <p>The limit for the resource was exceeded.</p>
@@ -311,11 +303,7 @@ declare const CreateCapacityProviderCommand_base: {
  *  <p>The specified task isn't supported in this Region.</p>
  *
  * @throws {@link UpdateInProgressException} (client fault)
- *  <p>There's already a current Amazon ECS container agent update in progress on the
- * 			container instance that's specified. If the container agent becomes disconnected while
- * 			it's in a transitional stage, such as <code>PENDING</code> or <code>STAGING</code>, the
- * 			update process can get stuck in that state. However, when the agent reconnects, it
- * 			resumes where it stopped previously.</p>
+ *  <p>There's already a current Amazon ECS container agent update in progress on the container instance that's specified. If the container agent becomes disconnected while it's in a transitional stage, such as <code>PENDING</code> or <code>STAGING</code>, the update process can get stuck in that state. However, when the agent reconnects, it resumes where it stopped previously.</p>
  *
  * @throws {@link ECSServiceException}
  * <p>Base exception class for all service exceptions from ECS service.</p>

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

@@ -27,19 +27,7 @@ declare const CreateClusterCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a new Amazon ECS cluster. By default, your account receives a
- * 				<code>default</code> cluster when you launch your first container instance. However,
- * 			you can create your own cluster with a unique name.</p>
- *          <note>
- *             <p>When you call the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html">CreateCluster</a>
- * 				API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for
- * 				your account. This is so that it can manage required resources in other Amazon Web
- * 					Services services on your behalf. However, if the user that makes the
- * 				call doesn't have permissions to create the service-linked role, it isn't created.
- * 				For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
- * 					service-linked roles for Amazon ECS</a> in the <i>Amazon Elastic
- * 					Container Service Developer Guide</i>.</p>
- *          </note>
+ * <p>Creates a new Amazon ECS cluster. By default, your account receives a <code>default</code> cluster when you launch your first container instance. However, you can create your own cluster with a unique name.</p> <note> <p>When you call the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html">CreateCluster</a> API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account. This is so that it can manage required resources in other Amazon Web Services services on your behalf. However, if the user that makes the call doesn't have permissions to create the service-linked role, it isn't created. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using service-linked roles for Amazon ECS</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -178,15 +166,10 @@ declare const CreateClusterCommand_base: {
  * @see {@link ECSClientResolvedConfig | config} for ECSClient's `config` shape.
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.</p>
  *
  * @throws {@link InvalidParameterException} (client fault)
- *  <p>The specified parameter isn't valid. Review the available parameters for the API
- * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
- * 				service event messages</a>. </p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p> <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service event messages</a>. </p>
  *
  * @throws {@link NamespaceNotFoundException} (client fault)
  *  <p>The specified namespace wasn't found.</p>

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

@@ -27,15 +27,7 @@ declare const CreateExpressGatewayServiceCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates an Express service that simplifies deploying containerized web applications on
- * 			Amazon ECS with managed Amazon Web Services infrastructure. This operation provisions and configures
- * 			Application Load Balancers, target groups, security groups, and auto-scaling policies
- * 			automatically.</p>
- *          <p>Specify a primary container configuration with your application image and basic
- * 			settings. Amazon ECS creates the necessary Amazon Web Services resources for traffic distribution, health
- * 			monitoring, network access control, and capacity management.</p>
- *          <p>Provide an execution role for task operations and an infrastructure role for managing
- * 			Amazon Web Services resources on your behalf.</p>
+ * <p>Creates an Express service that simplifies deploying containerized web applications on Amazon ECS with managed Amazon Web Services infrastructure. This operation provisions and configures Application Load Balancers, target groups, security groups, and auto-scaling policies automatically.</p> <p>Specify a primary container configuration with your application image and basic settings. Amazon ECS creates the necessary Amazon Web Services resources for traffic distribution, health monitoring, network access control, and capacity management.</p> <p>Provide an execution role for task operations and an infrastructure role for managing Amazon Web Services resources on your behalf.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -193,22 +185,16 @@ declare const CreateExpressGatewayServiceCommand_base: {
  *  <p>You don't have authorization to perform the requested action.</p>
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.</p>
  *
  * @throws {@link ClusterNotFoundException} (client fault)
  *  <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>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
- * 				service event messages</a>. </p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p> <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service event messages</a>. </p>
  *
  * @throws {@link PlatformTaskDefinitionIncompatibilityException} (client fault)
- *  <p>The specified platform version doesn't satisfy the required capabilities of the task
- * 			definition.</p>
+ *  <p>The specified platform version doesn't satisfy the required capabilities of the task definition.</p>
  *
  * @throws {@link PlatformUnknownException} (client fault)
  *  <p>The specified platform version doesn't exist.</p>

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

@@ -27,233 +27,7 @@ declare const CreateServiceCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Runs and maintains your desired number of tasks from a specified task definition. If
- * 			the number of tasks running in a service drops below the <code>desiredCount</code>,
- * 			Amazon ECS runs another copy of the task in the specified cluster. To update an existing
- * 			service, use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p>
- *          <note>
- *             <p>On March 21, 2024, a change was made to resolve the task definition revision
- * 				before authorization. When a task definition revision is not specified,
- * 				authorization will occur using the latest revision of a task definition.</p>
- *          </note>
- *          <note>
- *             <p>Amazon Elastic Inference (EI) is no longer available to customers.</p>
- *          </note>
- *          <p>In addition to maintaining the desired count of tasks in your service, you can
- * 			optionally run your service behind one or more load balancers. The load balancers
- * 			distribute traffic across the tasks that are associated with the service. For more
- * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic
- * 				Container Service Developer Guide</i>.</p>
- *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when
- * 			creating or updating a service. <code>volumeConfigurations</code> is only supported for
- * 			REPLICA service and not DAEMON service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic
- * 				Container Service Developer Guide</i>.</p>
- *          <p>Tasks for services that don't use a load balancer are considered healthy if they're in
- * 			the <code>RUNNING</code> state. Tasks for services that use a load balancer are
- * 			considered healthy if they're in the <code>RUNNING</code> state and are reported as
- * 			healthy by the load balancer.</p>
- *          <p>There are two service scheduler strategies available:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <code>REPLICA</code> - The replica scheduling strategy places and maintains
- * 					your desired number of tasks across your cluster. By default, the service
- * 					scheduler spreads tasks across Availability Zones. You can use task placement
- * 					strategies and constraints to customize task placement decisions. For more
- * 					information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the
- * 						<i>Amazon Elastic Container Service Developer
- * 					Guide</i>.</p>
- *             </li>
- *             <li>
- *                <p>
- *                   <code>DAEMON</code> - The daemon scheduling strategy deploys exactly one task
- * 					on each active container instance that meets all of the task placement
- * 					constraints that you specify in your cluster. The service scheduler also
- * 					evaluates the task placement constraints for running tasks. It also stops tasks
- * 					that don't meet the placement constraints. When using this strategy, you don't
- * 					need to specify a desired number of tasks, a task placement strategy, or use
- * 					Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Amazon ECS services</a> in the <i>Amazon Elastic Container
- * 						Service Developer Guide</i>.</p>
- *             </li>
- *          </ul>
- *          <p>The deployment controller is the mechanism that determines how tasks are deployed for
- * 			your service. The valid options are:</p>
- *          <ul>
- *             <li>
- *                <p>ECS</p>
- *                <p> When you create a service which uses the <code>ECS</code> deployment
- * 					controller, you can choose between the following deployment strategies (which
- * 					you can set in the “<code>strategy</code>” field in
- * 						“<code>deploymentConfiguration</code>”): :</p>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <code>ROLLING</code>: When you create a service which uses the
- * 								<i>rolling update</i> (<code>ROLLING</code>)
- * 							deployment strategy, the Amazon ECS service scheduler replaces the
- * 							currently running tasks with new tasks. The number of tasks that Amazon
- * 							ECS adds or removes from the service during a rolling update is
- * 							controlled by the service deployment configuration. For more
- * 							information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Deploy Amazon ECS services by replacing
- * 								tasks</a> in the <i>Amazon Elastic Container Service
- * 								Developer Guide</i>.</p>
- *                      <p>Rolling update deployments are best suited for the following
- * 							scenarios:</p>
- *                      <ul>
- *                         <li>
- *                            <p>Gradual service updates: You need to update your service
- * 									incrementally without taking the entire service offline at
- * 									once.</p>
- *                         </li>
- *                         <li>
- *                            <p>Limited resource requirements: You want to avoid the
- * 									additional resource costs of running two complete environments
- * 									simultaneously (as required by blue/green deployments).</p>
- *                         </li>
- *                         <li>
- *                            <p>Acceptable deployment time: Your application can tolerate a
- * 									longer deployment process, as rolling updates replace tasks one
- * 									by one.</p>
- *                         </li>
- *                         <li>
- *                            <p>No need for instant roll back: Your service can tolerate a
- * 									rollback process that takes minutes rather than seconds.</p>
- *                         </li>
- *                         <li>
- *                            <p>Simple deployment process: You prefer a straightforward
- * 									deployment approach without the complexity of managing multiple
- * 									environments, target groups, and listeners.</p>
- *                         </li>
- *                         <li>
- *                            <p>No load balancer requirement: Your service doesn't use or
- * 									require a load balancer, Application Load Balancer, Network Load
- * 									Balancer, or Service Connect (which are required for blue/green
- * 									deployments).</p>
- *                         </li>
- *                         <li>
- *                            <p>Stateful applications: Your application maintains state that
- * 									makes it difficult to run two parallel environments.</p>
- *                         </li>
- *                         <li>
- *                            <p>Cost sensitivity: You want to minimize deployment costs by not
- * 									running duplicate environments during deployment.</p>
- *                         </li>
- *                      </ul>
- *                      <p>Rolling updates are the default deployment strategy for services and
- * 							provide a balance between deployment safety and resource efficiency for
- * 							many common application scenarios.</p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <code>BLUE_GREEN</code>: A <i>blue/green</i> deployment
- * 							strategy (<code>BLUE_GREEN</code>) is a release methodology that reduces
- * 							downtime and risk by running two identical production environments
- * 							called blue and green. With Amazon ECS blue/green deployments, you can
- * 							validate new service revisions before directing production traffic to
- * 							them. This approach provides a safer way to deploy changes with the
- * 							ability to quickly roll back if needed. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-blue-green.html">Amazon ECS blue/green deployments</a> in
- * 							the <i>Amazon Elastic Container Service Developer
- * 								Guide</i>.</p>
- *                      <p>Amazon ECS blue/green deployments are best suited for the following
- * 							scenarios:</p>
- *                      <ul>
- *                         <li>
- *                            <p>Service validation: When you need to validate new service
- * 									revisions before directing production traffic to them</p>
- *                         </li>
- *                         <li>
- *                            <p>Zero downtime: When your service requires zero-downtime
- * 									deployments</p>
- *                         </li>
- *                         <li>
- *                            <p>Instant roll back: When you need the ability to quickly roll
- * 									back if issues are detected</p>
- *                         </li>
- *                         <li>
- *                            <p>Load balancer requirement: When your service uses Application
- * 									Load Balancer, Network Load Balancer, or Service Connect</p>
- *                         </li>
- *                      </ul>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <code>LINEAR</code>: A <i>linear</i> deployment strategy
- * 								(<code>LINEAR</code>) gradually shifts traffic from the current
- * 							production environment to a new environment in equal percentage
- * 							increments. With Amazon ECS linear deployments, you can control the pace
- * 							of traffic shifting and validate new service revisions with increasing
- * 							amounts of production traffic.</p>
- *                      <p>Linear deployments are best suited for the following scenarios:</p>
- *                      <ul>
- *                         <li>
- *                            <p>Gradual validation: When you want to gradually validate your
- * 									new service version with increasing traffic</p>
- *                         </li>
- *                         <li>
- *                            <p>Performance monitoring: When you need time to monitor metrics
- * 									and performance during the deployment</p>
- *                         </li>
- *                         <li>
- *                            <p>Risk minimization: When you want to minimize risk by exposing
- * 									the new version to production traffic incrementally</p>
- *                         </li>
- *                         <li>
- *                            <p>Load balancer requirement: When your service uses Application
- * 									Load Balancer or Service Connect</p>
- *                         </li>
- *                      </ul>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <code>CANARY</code>: A <i>canary</i> deployment strategy
- * 								(<code>CANARY</code>) shifts a small percentage of traffic to the
- * 							new service revision first, then shifts the remaining traffic all at
- * 							once after a specified time period. This allows you to test the new
- * 							version with a subset of users before full deployment.</p>
- *                      <p>Canary deployments are best suited for the following scenarios:</p>
- *                      <ul>
- *                         <li>
- *                            <p>Feature testing: When you want to test new features with a
- * 									small subset of users before full rollout</p>
- *                         </li>
- *                         <li>
- *                            <p>Production validation: When you need to validate performance
- * 									and functionality with real production traffic</p>
- *                         </li>
- *                         <li>
- *                            <p>Blast radius control: When you want to minimize blast radius
- * 									if issues are discovered in the new version</p>
- *                         </li>
- *                         <li>
- *                            <p>Load balancer requirement: When your service uses Application
- * 									Load Balancer or Service Connect</p>
- *                         </li>
- *                      </ul>
- *                   </li>
- *                </ul>
- *             </li>
- *             <li>
- *                <p>External</p>
- *                <p>Use a third-party deployment controller.</p>
- *             </li>
- *             <li>
- *                <p>Blue/green deployment (powered by CodeDeploy)</p>
- *                <p>CodeDeploy installs an updated version of the application as a new
- * 					replacement task set and reroutes production traffic from the original
- * 					application task set to the replacement task set. The original task set is
- * 					terminated after a successful deployment. Use this deployment controller to
- * 					verify a new deployment of a service before sending production traffic to
- * 					it.</p>
- *             </li>
- *          </ul>
- *          <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
- * 			can specify only parameters that aren't controlled at the task set level. The only
- * 			required parameter is the service name. You control your services using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container
- * 				Service Developer Guide</i>.</p>
- *          <p>When the service scheduler launches new tasks, it determines task placement. For
- * 			information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS task placement</a> in the <i>Amazon Elastic Container Service
- * 				Developer Guide</i>
- *          </p>
+ * <p>Runs and maintains your desired number of tasks from a specified task definition. If the number of tasks running in a service drops below the <code>desiredCount</code>, Amazon ECS runs another copy of the task in the specified cluster. To update an existing service, use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p> <note> <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p> </note> <note> <p>Amazon Elastic Inference (EI) is no longer available to customers.</p> </note> <p>In addition to maintaining the desired count of tasks in your service, you can optionally run your service behind one or more load balancers. The load balancers distribute traffic across the tasks that are associated with the service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a service. <code>volumeConfigurations</code> is only supported for REPLICA service and not DAEMON service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>Tasks for services that don't use a load balancer are considered healthy if they're in the <code>RUNNING</code> state. Tasks for services that use a load balancer are considered healthy if they're in the <code>RUNNING</code> state and are reported as healthy by the load balancer.</p> <p>There are two service scheduler strategies available:</p> <ul> <li> <p> <code>REPLICA</code> - The replica scheduling strategy places and maintains your desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </li> <li> <p> <code>DAEMON</code> - The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It also stops tasks that don't meet the placement constraints. When using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Amazon ECS services</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </li> </ul> <p>The deployment controller is the mechanism that determines how tasks are deployed for your service. The valid options are:</p> <ul> <li> <p>ECS</p> <p> When you create a service which uses the <code>ECS</code> deployment controller, you can choose between the following deployment strategies (which you can set in the “<code>strategy</code>” field in “<code>deploymentConfiguration</code>”): :</p> <ul> <li> <p> <code>ROLLING</code>: When you create a service which uses the <i>rolling update</i> (<code>ROLLING</code>) deployment strategy, the Amazon ECS service scheduler replaces the currently running tasks with new tasks. The number of tasks that Amazon ECS adds or removes from the service during a rolling update is controlled by the service deployment configuration. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Deploy Amazon ECS services by replacing tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>Rolling update deployments are best suited for the following scenarios:</p> <ul> <li> <p>Gradual service updates: You need to update your service incrementally without taking the entire service offline at once.</p> </li> <li> <p>Limited resource requirements: You want to avoid the additional resource costs of running two complete environments simultaneously (as required by blue/green deployments).</p> </li> <li> <p>Acceptable deployment time: Your application can tolerate a longer deployment process, as rolling updates replace tasks one by one.</p> </li> <li> <p>No need for instant roll back: Your service can tolerate a rollback process that takes minutes rather than seconds.</p> </li> <li> <p>Simple deployment process: You prefer a straightforward deployment approach without the complexity of managing multiple environments, target groups, and listeners.</p> </li> <li> <p>No load balancer requirement: Your service doesn't use or require a load balancer, Application Load Balancer, Network Load Balancer, or Service Connect (which are required for blue/green deployments).</p> </li> <li> <p>Stateful applications: Your application maintains state that makes it difficult to run two parallel environments.</p> </li> <li> <p>Cost sensitivity: You want to minimize deployment costs by not running duplicate environments during deployment.</p> </li> </ul> <p>Rolling updates are the default deployment strategy for services and provide a balance between deployment safety and resource efficiency for many common application scenarios.</p> </li> <li> <p> <code>BLUE_GREEN</code>: A <i>blue/green</i> deployment strategy (<code>BLUE_GREEN</code>) is a release methodology that reduces downtime and risk by running two identical production environments called blue and green. With Amazon ECS blue/green deployments, you can validate new service revisions before directing production traffic to them. This approach provides a safer way to deploy changes with the ability to quickly roll back if needed. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-blue-green.html">Amazon ECS blue/green deployments</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>Amazon ECS blue/green deployments are best suited for the following scenarios:</p> <ul> <li> <p>Service validation: When you need to validate new service revisions before directing production traffic to them</p> </li> <li> <p>Zero downtime: When your service requires zero-downtime deployments</p> </li> <li> <p>Instant roll back: When you need the ability to quickly roll back if issues are detected</p> </li> <li> <p>Load balancer requirement: When your service uses Application Load Balancer, Network Load Balancer, or Service Connect</p> </li> </ul> </li> <li> <p> <code>LINEAR</code>: A <i>linear</i> deployment strategy (<code>LINEAR</code>) gradually shifts traffic from the current production environment to a new environment in equal percentage increments. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic.</p> <p>Linear deployments are best suited for the following scenarios:</p> <ul> <li> <p>Gradual validation: When you want to gradually validate your new service version with increasing traffic</p> </li> <li> <p>Performance monitoring: When you need time to monitor metrics and performance during the deployment</p> </li> <li> <p>Risk minimization: When you want to minimize risk by exposing the new version to production traffic incrementally</p> </li> <li> <p>Load balancer requirement: When your service uses Application Load Balancer or Service Connect</p> </li> </ul> </li> <li> <p> <code>CANARY</code>: A <i>canary</i> deployment strategy (<code>CANARY</code>) shifts a small percentage of traffic to the new service revision first, then shifts the remaining traffic all at once after a specified time period. This allows you to test the new version with a subset of users before full deployment.</p> <p>Canary deployments are best suited for the following scenarios:</p> <ul> <li> <p>Feature testing: When you want to test new features with a small subset of users before full rollout</p> </li> <li> <p>Production validation: When you need to validate performance and functionality with real production traffic</p> </li> <li> <p>Blast radius control: When you want to minimize blast radius if issues are discovered in the new version</p> </li> <li> <p>Load balancer requirement: When your service uses Application Load Balancer or Service Connect</p> </li> </ul> </li> </ul> </li> <li> <p>External</p> <p>Use a third-party deployment controller.</p> </li> <li> <p>Blue/green deployment (powered by CodeDeploy)</p> <p>CodeDeploy installs an updated version of the application as a new replacement task set and reroutes production traffic from the original application task set to the replacement task set. The original task set is terminated after a successful deployment. Use this deployment controller to verify a new deployment of a service before sending production traffic to it.</p> </li> </ul> <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you can specify only parameters that aren't controlled at the task set level. The only required parameter is the service name. You control your services using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>When the service scheduler launches new tasks, it determines task placement. For information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i> </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -813,25 +587,19 @@ declare const CreateServiceCommand_base: {
  *  <p>You don't have authorization to perform the requested action.</p>
  *
  * @throws {@link ClientException} (client fault)
- *  <p>These errors are usually caused by a client action. This client action might be using
- * 			an action or resource on behalf of a user that doesn't have permissions to use the
- * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
+ *  <p>These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.</p>
  *
  * @throws {@link ClusterNotFoundException} (client fault)
  *  <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>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
- * 				service event messages</a>. </p>
+ *  <p>The specified parameter isn't valid. Review the available parameters for the API request.</p> <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service event messages</a>. </p>
  *
  * @throws {@link NamespaceNotFoundException} (client fault)
  *  <p>The specified namespace wasn't found.</p>
  *
  * @throws {@link PlatformTaskDefinitionIncompatibilityException} (client fault)
- *  <p>The specified platform version doesn't satisfy the required capabilities of the task
- * 			definition.</p>
+ *  <p>The specified platform version doesn't satisfy the required capabilities of the task definition.</p>
  *
  * @throws {@link PlatformUnknownException} (client fault)
  *  <p>The specified platform version doesn't exist.</p>