@aws-sdk/client-ecs 3.1077.0 → 3.1079.0

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateClusterSettingsRequest, UpdateClusterSettingsResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateClusterSettingsCommandInput extends UpdateClusterSettings
 export interface UpdateClusterSettingsCommandOutput extends UpdateClusterSettingsResponse, __MetadataBearer {
 }
 declare const UpdateClusterSettingsCommand_base: {
-    new (input: UpdateClusterSettingsCommandInput): import("@smithy/core/client").CommandImpl<UpdateClusterSettingsCommandInput, UpdateClusterSettingsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateClusterSettingsCommandInput): import("@smithy/core/client").CommandImpl<UpdateClusterSettingsCommandInput, UpdateClusterSettingsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateClusterSettingsCommandInput): import("@smithy/core/client").CommandImpl<UpdateClusterSettingsCommandInput, UpdateClusterSettingsCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateClusterSettingsCommandInput): import("@smithy/core/client").CommandImpl<UpdateClusterSettingsCommandInput, UpdateClusterSettingsCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Modifies the settings to use for a cluster.</p>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateContainerAgentRequest, UpdateContainerAgentResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateContainerAgentCommandInput extends UpdateContainerAgentRe
 export interface UpdateContainerAgentCommandOutput extends UpdateContainerAgentResponse, __MetadataBearer {
 }
 declare const UpdateContainerAgentCommand_base: {
-    new (input: UpdateContainerAgentCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerAgentCommandInput, UpdateContainerAgentCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateContainerAgentCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerAgentCommandInput, UpdateContainerAgentCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateContainerAgentCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerAgentCommandInput, UpdateContainerAgentCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateContainerAgentCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerAgentCommandInput, UpdateContainerAgentCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").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> <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 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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateContainerInstancesStateRequest, UpdateContainerInstancesStateResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateContainerInstancesStateCommandInput extends UpdateContain
 export interface UpdateContainerInstancesStateCommandOutput extends UpdateContainerInstancesStateResponse, __MetadataBearer {
 }
 declare const UpdateContainerInstancesStateCommand_base: {
-    new (input: UpdateContainerInstancesStateCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerInstancesStateCommandInput, UpdateContainerInstancesStateCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateContainerInstancesStateCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerInstancesStateCommandInput, UpdateContainerInstancesStateCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateContainerInstancesStateCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerInstancesStateCommandInput, UpdateContainerInstancesStateCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateContainerInstancesStateCommandInput): import("@smithy/core/client").CommandImpl<UpdateContainerInstancesStateCommandInput, UpdateContainerInstancesStateCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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> <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 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> </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> </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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateDaemonRequest, UpdateDaemonResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateDaemonCommandInput extends UpdateDaemonRequest {
 export interface UpdateDaemonCommandOutput extends UpdateDaemonResponse, __MetadataBearer {
 }
 declare const UpdateDaemonCommand_base: {
-    new (input: UpdateDaemonCommandInput): import("@smithy/core/client").CommandImpl<UpdateDaemonCommandInput, UpdateDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateDaemonCommandInput): import("@smithy/core/client").CommandImpl<UpdateDaemonCommandInput, UpdateDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateDaemonCommandInput): import("@smithy/core/client").CommandImpl<UpdateDaemonCommandInput, UpdateDaemonCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateDaemonCommandInput): import("@smithy/core/client").CommandImpl<UpdateDaemonCommandInput, UpdateDaemonCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Updates the specified daemon. When you update a daemon, a new deployment is triggered that progressively rolls out the changes to the container instances associated with the daemon's capacity providers. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/daemon-deployments.html">Daemon deployments</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>Amazon ECS drains existing container instances and provisions new instances with the updated daemon. Amazon ECS automatically launches replacement tasks for your services.</p> <important> <p>Updating a daemon triggers a rolling deployment that drains and replaces container instances. Plan updates during maintenance windows to minimize impact on running services.</p> </important> <note> <p>ECS Managed Daemons is only supported for Amazon ECS Managed Instances Capacity Providers.</p> </note>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateExpressGatewayServiceRequest, UpdateExpressGatewayServiceResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateExpressGatewayServiceCommandInput extends UpdateExpressGa
 export interface UpdateExpressGatewayServiceCommandOutput extends UpdateExpressGatewayServiceResponse, __MetadataBearer {
 }
 declare const UpdateExpressGatewayServiceCommand_base: {
-    new (input: UpdateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateExpressGatewayServiceCommandInput, UpdateExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateExpressGatewayServiceCommandInput, UpdateExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateExpressGatewayServiceCommandInput, UpdateExpressGatewayServiceCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateExpressGatewayServiceCommandInput, UpdateExpressGatewayServiceCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Updates an existing Express service configuration. Modifies container settings, resource allocation, auto-scaling configuration, and other service parameters without recreating the service.</p> <p>Amazon ECS creates a new service revision with updated configuration and performs a rolling deployment to replace existing tasks. The service remains available during updates, ensuring zero-downtime deployments.</p> <p>Some parameters like the infrastructure role cannot be modified after service creation and require creating a new service.</p>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateServiceRequest, UpdateServiceResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateServiceCommandInput extends UpdateServiceRequest {
 export interface UpdateServiceCommandOutput extends UpdateServiceResponse, __MetadataBearer {
 }
 declare const UpdateServiceCommand_base: {
-    new (input: UpdateServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateServiceCommandInput, UpdateServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateServiceCommandInput, UpdateServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateServiceCommandInput, UpdateServiceCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateServiceCommandInput): import("@smithy/core/client").CommandImpl<UpdateServiceCommandInput, UpdateServiceCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Modifies the parameters of a service.</p> <note> <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p> </note> <p>For services using the rolling update (<code>ECS</code>) you can update the desired count, deployment configuration, network configuration, load balancers, service registries, enable ECS managed tags option, propagate tags option, task placement constraints and strategies, and task definition. When you update any of these parameters, Amazon ECS starts new tasks with the new configuration. </p> <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or running a task, or when creating or updating a 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>. You can update your volume configurations and trigger a new deployment. <code>volumeConfigurations</code> is only supported for REPLICA service and not DAEMON service. If you leave <code>volumeConfigurations</code> <code>null</code>, it doesn't trigger a new deployment. For more information on volumes, 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>For services using the blue/green (<code>CODE_DEPLOY</code>) deployment controller, only the desired count, deployment configuration, health check grace period, task placement constraints and strategies, enable ECS managed tags option, and propagate tags can be updated using this API. If the network configuration, platform version, task definition, or load balancer need to be updated, create a new CodeDeploy deployment. For more information, see <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html">CreateDeployment</a> in the <i>CodeDeploy API Reference</i>.</p> <p>For services using an external deployment controller, you can update only the desired count, task placement constraints and strategies, health check grace period, enable ECS managed tags option, and propagate tags option, using this API. If the launch type, load balancer, network configuration, platform version, or task definition need to be updated, create a new task set For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>.</p> <p>You can add to or subtract from the number of instantiations of a task definition in a service by specifying the cluster that the service is running in and a new <code>desiredCount</code> parameter.</p> <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or running a task, or when creating or updating a 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>If you have updated the container image of your application, you can create a new task definition with that image and deploy it to your service. The service scheduler uses the minimum healthy percent and maximum percent parameters (in the service's deployment configuration) to determine the deployment strategy.</p> <note> <p>If your updated Docker image uses the same tag as what is in the existing task definition for your service (for example, <code>my_image:latest</code>), you don't need to create a new revision of your task definition. You can update the service using the <code>forceNewDeployment</code> option. The new tasks launched by the deployment pull the current image/tag combination from your repository when they start.</p> </note> <p>You can also update the deployment configuration of a service. When a deployment is triggered by updating the task definition of a service, the service scheduler uses the deployment configuration parameters, <code>minimumHealthyPercent</code> and <code>maximumPercent</code>, to determine the deployment strategy.</p> <ul> <li> <p>If <code>minimumHealthyPercent</code> is below 100%, the scheduler can ignore <code>desiredCount</code> temporarily during a deployment. For example, if <code>desiredCount</code> is four tasks, a minimum of 50% allows the scheduler to stop two existing tasks before starting two new tasks. 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> </li> <li> <p>The <code>maximumPercent</code> parameter represents an upper limit on the number of running tasks during a deployment. You can use it to define the deployment batch size. For example, if <code>desiredCount</code> is four tasks, a maximum of 200% starts four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available).</p> </li> </ul> <p>When <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a> stops a task during a deployment, the equivalent of <code>docker stop</code> is issued to the containers running in the task. This results in a <code>SIGTERM</code> and a 30-second timeout. After this, <code>SIGKILL</code> is sent and the containers are forcibly stopped. If the container handles the <code>SIGTERM</code> gracefully and exits within 30 seconds from receiving it, no <code>SIGKILL</code> is sent.</p> <p>When the service scheduler launches new tasks, it determines task placement in your cluster with the following logic.</p> <ul> <li> <p>Determine which of the container instances in your cluster can support your service's task definition. For example, they have the required CPU, memory, ports, and container instance attributes.</p> </li> <li> <p>By default, the service scheduler attempts to balance tasks across Availability Zones in this manner even though you can choose a different placement strategy.</p> <ul> <li> <p>Sort the valid container instances by the fewest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have zero, valid container instances in either zone B or C are considered optimal for placement.</p> </li> <li> <p>Place the new service task on a valid container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the fewest number of running tasks for this service.</p> </li> </ul> </li> </ul> <p>When the service scheduler stops running tasks, it attempts to maintain balance across the Availability Zones in your cluster using the following logic: </p> <ul> <li> <p>Sort the container instances by the largest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have two, container instances in either zone B or C are considered optimal for termination.</p> </li> <li> <p>Stop the task on a container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the largest number of running tasks for this service.</p> </li> </ul>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateServicePrimaryTaskSetRequest, UpdateServicePrimaryTaskSetResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateServicePrimaryTaskSetCommandInput extends UpdateServicePr
 export interface UpdateServicePrimaryTaskSetCommandOutput extends UpdateServicePrimaryTaskSetResponse, __MetadataBearer {
 }
 declare const UpdateServicePrimaryTaskSetCommand_base: {
-    new (input: UpdateServicePrimaryTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateServicePrimaryTaskSetCommandInput, UpdateServicePrimaryTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateServicePrimaryTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateServicePrimaryTaskSetCommandInput, UpdateServicePrimaryTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateServicePrimaryTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateServicePrimaryTaskSetCommandInput, UpdateServicePrimaryTaskSetCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateServicePrimaryTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateServicePrimaryTaskSetCommandInput, UpdateServicePrimaryTaskSetCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Modifies which task set in a service is the primary task set. Any parameters that are updated on the primary task set in a service will transition to the service. This is used when a service uses the <code>EXTERNAL</code> deployment controller type. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS Deployment Types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateTaskProtectionRequest, UpdateTaskProtectionResponse } from "../models/models_1";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateTaskProtectionCommandInput extends UpdateTaskProtectionRe
 export interface UpdateTaskProtectionCommandOutput extends UpdateTaskProtectionResponse, __MetadataBearer {
 }
 declare const UpdateTaskProtectionCommand_base: {
-    new (input: UpdateTaskProtectionCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskProtectionCommandInput, UpdateTaskProtectionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateTaskProtectionCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskProtectionCommandInput, UpdateTaskProtectionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateTaskProtectionCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskProtectionCommandInput, UpdateTaskProtectionCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateTaskProtectionCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskProtectionCommandInput, UpdateTaskProtectionCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Updates the protection status of a task. You can set <code>protectionEnabled</code> to <code>true</code> to protect your task from termination during scale-in events from <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html">Service Autoscaling</a> or <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">deployments</a>.</p> <p>Task-protection, by default, expires after 2 hours at which point Amazon ECS clears the <code>protectionEnabled</code> property making the task eligible for termination by a subsequent scale-in event.</p> <p>You can specify a custom expiration period for task protection from 1 minute to up to 2,880 minutes (48 hours). To specify the custom expiration period, set the <code>expiresInMinutes</code> property. The <code>expiresInMinutes</code> property is always reset when you invoke this operation for a task that already has <code>protectionEnabled</code> set to <code>true</code>. You can keep extending the protection expiration period of a task by invoking this operation repeatedly.</p> <p>To learn more about Amazon ECS task protection, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection.html">Task scale-in protection</a> in the <i> <i>Amazon Elastic Container Service Developer Guide</i> </i>.</p> <note> <p>This operation is only supported for tasks belonging to an Amazon ECS service. Invoking this operation for a standalone task will result in an <code>TASK_NOT_VALID</code> failure. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/api_failures_messages.html">API failure reasons</a>.</p> </note> <important> <p>If you prefer to set task protection from within the container, we recommend using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection-endpoint.html">Task scale-in protection endpoint</a>.</p> </important>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ECSClient";
 import type { UpdateTaskSetRequest, UpdateTaskSetResponse } from "../models/models_1";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface UpdateTaskSetCommandInput extends UpdateTaskSetRequest {
 export interface UpdateTaskSetCommandOutput extends UpdateTaskSetResponse, __MetadataBearer {
 }
 declare const UpdateTaskSetCommand_base: {
-    new (input: UpdateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskSetCommandInput, UpdateTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: UpdateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskSetCommandInput, UpdateTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: UpdateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskSetCommandInput, UpdateTaskSetCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: UpdateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<UpdateTaskSetCommandInput, UpdateTaskSetCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Modifies a task set. This is used when a service uses the <code>EXTERNAL</code> deployment controller type. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS Deployment Types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>

package/dist-types/index.d.ts

@@ -9,6 +9,7 @@ export type { ClientInputEndpointParameters } from "./endpoint/EndpointParameter
 export type { RuntimeExtension } from "./runtimeExtensions";
 export type { ECSExtensionConfiguration } from "./extensionConfiguration";
 export * from "./commands";
+export { Command as $Command } from "@smithy/core/client";
 export * from "./schemas/schemas_0";
 export * from "./pagination";
 export * from "./waiters";

package/dist-types/ts3.4/commandBuilder.d.ts

@@ -0,0 +1,46 @@
+import { EndpointParameterInstructions } from "@smithy/types";
+import {
+  ECSClientResolvedConfig,
+  ServiceInputTypes,
+  ServiceOutputTypes,
+} from "./ECSClient";
+export declare const command: <
+  I extends ServiceInputTypes,
+  O extends ServiceOutputTypes
+>(
+  added: EndpointParameterInstructions,
+  plugins: (
+    CommandCtor: any,
+    clientStack: any,
+    config: any,
+    options: any
+  ) => import("@smithy/types").Pluggable<any, any>[],
+  op: string,
+  $: import("@smithy/types").StaticOperationSchema,
+  smithyContext?: Record<string, unknown>
+) => {
+  new (input: I): import("@smithy/core/client").CommandImpl<
+    I,
+    O,
+    ECSClientResolvedConfig,
+    ServiceInputTypes,
+    ServiceOutputTypes
+  >;
+  new (
+    ...[input]: import("@smithy/types").OptionalParameter<I>
+  ): import("@smithy/core/client").CommandImpl<
+    I,
+    O,
+    ECSClientResolvedConfig,
+    ServiceInputTypes,
+    ServiceOutputTypes
+  >;
+  getEndpointParameterInstructions(): EndpointParameterInstructions;
+};
+export declare const _ep0: EndpointParameterInstructions;
+export declare const _mw0: (
+  Command: any,
+  cs: any,
+  config: any,
+  o: any
+) => never[];

package/dist-types/ts3.4/commands/ContinueServiceDeploymentCommand.d.ts

@@ -1,16 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import {
-  ECSClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../ECSClient";
 import {
   ContinueServiceDeploymentRequest,
   ContinueServiceDeploymentResponse,
 } from "../models/models_0";
 export { __MetadataBearer };
-export { $Command };
 export interface ContinueServiceDeploymentCommandInput
   extends ContinueServiceDeploymentRequest {}
 export interface ContinueServiceDeploymentCommandOutput
@@ -22,22 +15,20 @@ declare const ContinueServiceDeploymentCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     ContinueServiceDeploymentCommandInput,
     ContinueServiceDeploymentCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: ContinueServiceDeploymentCommandInput
   ): import("@smithy/core/client").CommandImpl<
     ContinueServiceDeploymentCommandInput,
     ContinueServiceDeploymentCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class ContinueServiceDeploymentCommand extends ContinueServiceDeploymentCommand_base {
   protected static __types: {

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

@@ -1,16 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import {
-  ECSClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../ECSClient";
 import {
   CreateCapacityProviderRequest,
   CreateCapacityProviderResponse,
 } from "../models/models_0";
 export { __MetadataBearer };
-export { $Command };
 export interface CreateCapacityProviderCommandInput
   extends CreateCapacityProviderRequest {}
 export interface CreateCapacityProviderCommandOutput
@@ -22,22 +15,20 @@ declare const CreateCapacityProviderCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     CreateCapacityProviderCommandInput,
     CreateCapacityProviderCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: CreateCapacityProviderCommandInput
   ): import("@smithy/core/client").CommandImpl<
     CreateCapacityProviderCommandInput,
     CreateCapacityProviderCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class CreateCapacityProviderCommand extends CreateCapacityProviderCommand_base {
   protected static __types: {

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

@@ -1,16 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import {
-  ECSClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../ECSClient";
 import {
   CreateClusterRequest,
   CreateClusterResponse,
 } from "../models/models_0";
 export { __MetadataBearer };
-export { $Command };
 export interface CreateClusterCommandInput extends CreateClusterRequest {}
 export interface CreateClusterCommandOutput
   extends CreateClusterResponse,
@@ -21,22 +14,20 @@ declare const CreateClusterCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     CreateClusterCommandInput,
     CreateClusterCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     ...[input]: [] | [CreateClusterCommandInput]
   ): import("@smithy/core/client").CommandImpl<
     CreateClusterCommandInput,
     CreateClusterCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class CreateClusterCommand extends CreateClusterCommand_base {
   protected static __types: {

package/dist-types/ts3.4/commands/CreateDaemonCommand.d.ts

@@ -1,13 +1,6 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import {
-  ECSClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../ECSClient";
 import { CreateDaemonRequest, CreateDaemonResponse } from "../models/models_0";
 export { __MetadataBearer };
-export { $Command };
 export interface CreateDaemonCommandInput extends CreateDaemonRequest {}
 export interface CreateDaemonCommandOutput
   extends CreateDaemonResponse,
@@ -18,22 +11,20 @@ declare const CreateDaemonCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     CreateDaemonCommandInput,
     CreateDaemonCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: CreateDaemonCommandInput
   ): import("@smithy/core/client").CommandImpl<
     CreateDaemonCommandInput,
     CreateDaemonCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class CreateDaemonCommand extends CreateDaemonCommand_base {
   protected static __types: {

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

@@ -1,16 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import {
-  ECSClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../ECSClient";
 import {
   CreateExpressGatewayServiceRequest,
   CreateExpressGatewayServiceResponse,
 } from "../models/models_0";
 export { __MetadataBearer };
-export { $Command };
 export interface CreateExpressGatewayServiceCommandInput
   extends CreateExpressGatewayServiceRequest {}
 export interface CreateExpressGatewayServiceCommandOutput
@@ -22,22 +15,20 @@ declare const CreateExpressGatewayServiceCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     CreateExpressGatewayServiceCommandInput,
     CreateExpressGatewayServiceCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: CreateExpressGatewayServiceCommandInput
   ): import("@smithy/core/client").CommandImpl<
     CreateExpressGatewayServiceCommandInput,
     CreateExpressGatewayServiceCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class CreateExpressGatewayServiceCommand extends CreateExpressGatewayServiceCommand_base {
   protected static __types: {

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

@@ -1,16 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import {
-  ECSClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../ECSClient";
 import {
   CreateServiceRequest,
   CreateServiceResponse,
 } from "../models/models_0";
 export { __MetadataBearer };
-export { $Command };
 export interface CreateServiceCommandInput extends CreateServiceRequest {}
 export interface CreateServiceCommandOutput
   extends CreateServiceResponse,
@@ -21,22 +14,20 @@ declare const CreateServiceCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     CreateServiceCommandInput,
     CreateServiceCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: CreateServiceCommandInput
   ): import("@smithy/core/client").CommandImpl<
     CreateServiceCommandInput,
     CreateServiceCommandOutput,
-    ECSClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").ECSClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class CreateServiceCommand extends CreateServiceCommand_base {
   protected static __types: {