@aws-sdk/client-ecs 3.1044.0 → 3.1046.0

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { CreateExpressGatewayServiceRequest, CreateExpressGatewayServiceResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface CreateExpressGatewayServiceCommandInput extends CreateExpressGa
 export interface CreateExpressGatewayServiceCommandOutput extends CreateExpressGatewayServiceResponse, __MetadataBearer {
 }
 declare const CreateExpressGatewayServiceCommand_base: {
-    new (input: CreateExpressGatewayServiceCommandInput): import("@smithy/smithy-client").CommandImpl<CreateExpressGatewayServiceCommandInput, CreateExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: CreateExpressGatewayServiceCommandInput): import("@smithy/smithy-client").CommandImpl<CreateExpressGatewayServiceCommandInput, CreateExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: CreateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<CreateExpressGatewayServiceCommandInput, CreateExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: CreateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<CreateExpressGatewayServiceCommandInput, CreateExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <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>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { CreateServiceRequest, CreateServiceResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface CreateServiceCommandInput extends CreateServiceRequest {
 export interface CreateServiceCommandOutput extends CreateServiceResponse, __MetadataBearer {
 }
 declare const CreateServiceCommand_base: {
-    new (input: CreateServiceCommandInput): import("@smithy/smithy-client").CommandImpl<CreateServiceCommandInput, CreateServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: CreateServiceCommandInput): import("@smithy/smithy-client").CommandImpl<CreateServiceCommandInput, CreateServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: CreateServiceCommandInput): import("@smithy/core/client").CommandImpl<CreateServiceCommandInput, CreateServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: CreateServiceCommandInput): import("@smithy/core/client").CommandImpl<CreateServiceCommandInput, CreateServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <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>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { CreateTaskSetRequest, CreateTaskSetResponse } from "../models/models_1";
@@ -22,9 +22,11 @@ export interface CreateTaskSetCommandInput extends CreateTaskSetRequest {
 export interface CreateTaskSetCommandOutput extends CreateTaskSetResponse, __MetadataBearer {
 }
 declare const CreateTaskSetCommand_base: {
-    new (input: CreateTaskSetCommandInput): import("@smithy/smithy-client").CommandImpl<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: CreateTaskSetCommandInput): import("@smithy/smithy-client").CommandImpl<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: CreateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: CreateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Create a task set in the specified cluster and 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> <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 information about the maximum number of task sets and other quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteAccountSettingRequest, DeleteAccountSettingResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteAccountSettingCommandInput extends DeleteAccountSettingRe
 export interface DeleteAccountSettingCommandOutput extends DeleteAccountSettingResponse, __MetadataBearer {
 }
 declare const DeleteAccountSettingCommand_base: {
-    new (input: DeleteAccountSettingCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteAccountSettingCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteAccountSettingCommandInput): import("@smithy/core/client").CommandImpl<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteAccountSettingCommandInput): import("@smithy/core/client").CommandImpl<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Disables an account setting for a specified user, role, or the root user for an account.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteAttributesRequest, DeleteAttributesResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteAttributesCommandInput extends DeleteAttributesRequest {
 export interface DeleteAttributesCommandOutput extends DeleteAttributesResponse, __MetadataBearer {
 }
 declare const DeleteAttributesCommand_base: {
-    new (input: DeleteAttributesCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteAttributesCommandInput, DeleteAttributesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteAttributesCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteAttributesCommandInput, DeleteAttributesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteAttributesCommandInput): import("@smithy/core/client").CommandImpl<DeleteAttributesCommandInput, DeleteAttributesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteAttributesCommandInput): import("@smithy/core/client").CommandImpl<DeleteAttributesCommandInput, DeleteAttributesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes one or more custom attributes from an Amazon ECS resource.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteCapacityProviderRequest, DeleteCapacityProviderResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteCapacityProviderCommandInput extends DeleteCapacityProvid
 export interface DeleteCapacityProviderCommandOutput extends DeleteCapacityProviderResponse, __MetadataBearer {
 }
 declare const DeleteCapacityProviderCommand_base: {
-    new (input: DeleteCapacityProviderCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteCapacityProviderCommandInput, DeleteCapacityProviderCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteCapacityProviderCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteCapacityProviderCommandInput, DeleteCapacityProviderCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteCapacityProviderCommandInput): import("@smithy/core/client").CommandImpl<DeleteCapacityProviderCommandInput, DeleteCapacityProviderCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteCapacityProviderCommandInput): import("@smithy/core/client").CommandImpl<DeleteCapacityProviderCommandInput, DeleteCapacityProviderCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes the specified capacity provider.</p> <note> <p>The <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers are reserved and can't be deleted. You can disassociate them from a cluster using either <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html">PutClusterCapacityProviders</a> or by deleting the cluster.</p> </note> <p>Prior to a capacity provider being deleted, the capacity provider must be removed from the capacity provider strategy from all services. The <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a> API can be used to remove a capacity provider from a service's capacity provider strategy. When updating a service, the <code>forceNewDeployment</code> option can be used to ensure that any tasks using the Amazon EC2 instance capacity provided by the capacity provider are transitioned to use the capacity from the remaining capacity providers. Only capacity providers that aren't associated with a cluster can be deleted. To remove a capacity provider from a cluster, you can either use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html">PutClusterCapacityProviders</a> or delete the cluster.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteClusterRequest, DeleteClusterResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteClusterCommandInput extends DeleteClusterRequest {
 export interface DeleteClusterCommandOutput extends DeleteClusterResponse, __MetadataBearer {
 }
 declare const DeleteClusterCommand_base: {
-    new (input: DeleteClusterCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteClusterCommandInput, DeleteClusterCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteClusterCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteClusterCommandInput, DeleteClusterCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteClusterCommandInput): import("@smithy/core/client").CommandImpl<DeleteClusterCommandInput, DeleteClusterCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteClusterCommandInput): import("@smithy/core/client").CommandImpl<DeleteClusterCommandInput, DeleteClusterCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes the specified cluster. The cluster transitions to the <code>INACTIVE</code> state. Clusters with an <code>INACTIVE</code> status might remain discoverable in your account for a period of time. However, this behavior is subject to change in the future. We don't recommend that you rely on <code>INACTIVE</code> clusters persisting.</p> <p>You must deregister all container instances from this cluster before you may delete it. You can list the container instances in a cluster with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html">ListContainerInstances</a> and deregister them with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeregisterContainerInstance.html">DeregisterContainerInstance</a>.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteDaemonRequest, DeleteDaemonResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteDaemonCommandInput extends DeleteDaemonRequest {
 export interface DeleteDaemonCommandOutput extends DeleteDaemonResponse, __MetadataBearer {
 }
 declare const DeleteDaemonCommand_base: {
-    new (input: DeleteDaemonCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteDaemonCommandInput, DeleteDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteDaemonCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteDaemonCommandInput, DeleteDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteDaemonCommandInput): import("@smithy/core/client").CommandImpl<DeleteDaemonCommandInput, DeleteDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteDaemonCommandInput): import("@smithy/core/client").CommandImpl<DeleteDaemonCommandInput, DeleteDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes the specified daemon. The daemon must be in an <code>ACTIVE</code> state to be deleted. Deleting a daemon stops all running daemon tasks on the associated container instances. Amazon ECS drains existing container instances and provisions new instances without the deleted daemon. Amazon ECS automatically launches replacement tasks for your Amazon ECS services.</p> <note> <p>ECS Managed Daemons is only supported for Amazon ECS Managed Instances Capacity Providers.</p> </note>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteDaemonTaskDefinitionRequest, DeleteDaemonTaskDefinitionResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteDaemonTaskDefinitionCommandInput extends DeleteDaemonTask
 export interface DeleteDaemonTaskDefinitionCommandOutput extends DeleteDaemonTaskDefinitionResponse, __MetadataBearer {
 }
 declare const DeleteDaemonTaskDefinitionCommand_base: {
-    new (input: DeleteDaemonTaskDefinitionCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteDaemonTaskDefinitionCommandInput, DeleteDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteDaemonTaskDefinitionCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteDaemonTaskDefinitionCommandInput, DeleteDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteDaemonTaskDefinitionCommandInput): import("@smithy/core/client").CommandImpl<DeleteDaemonTaskDefinitionCommandInput, DeleteDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteDaemonTaskDefinitionCommandInput): import("@smithy/core/client").CommandImpl<DeleteDaemonTaskDefinitionCommandInput, DeleteDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes the specified daemon task definition. After a daemon task definition is deleted, no new daemons can be created using this definition. Existing daemons that reference the deleted daemon task definition continue to run.</p> <p>A daemon task definition must be in an <code>ACTIVE</code> state to be deleted.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteExpressGatewayServiceRequest, DeleteExpressGatewayServiceResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteExpressGatewayServiceCommandInput extends DeleteExpressGa
 export interface DeleteExpressGatewayServiceCommandOutput extends DeleteExpressGatewayServiceResponse, __MetadataBearer {
 }
 declare const DeleteExpressGatewayServiceCommand_base: {
-    new (input: DeleteExpressGatewayServiceCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteExpressGatewayServiceCommandInput, DeleteExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteExpressGatewayServiceCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteExpressGatewayServiceCommandInput, DeleteExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<DeleteExpressGatewayServiceCommandInput, DeleteExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<DeleteExpressGatewayServiceCommandInput, DeleteExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes an Express service and removes all associated Amazon Web Services resources. This operation stops service tasks, removes the Application Load Balancer, target groups, security groups, auto-scaling policies, and other managed infrastructure components.</p> <p>The service enters a <code>DRAINING</code> state where existing tasks complete current requests without starting new tasks. After all tasks stop, the service and infrastructure are permanently removed.</p> <p>This operation cannot be reversed. Back up important data and verify the service is no longer needed before deletion.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteServiceRequest, DeleteServiceResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeleteServiceCommandInput extends DeleteServiceRequest {
 export interface DeleteServiceCommandOutput extends DeleteServiceResponse, __MetadataBearer {
 }
 declare const DeleteServiceCommand_base: {
-    new (input: DeleteServiceCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteServiceCommandInput, DeleteServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteServiceCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteServiceCommandInput, DeleteServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteServiceCommandInput): import("@smithy/core/client").CommandImpl<DeleteServiceCommandInput, DeleteServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteServiceCommandInput): import("@smithy/core/client").CommandImpl<DeleteServiceCommandInput, DeleteServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes a specified service within a cluster. You can delete a service if you have no running tasks in it and the desired task count is zero. If the service is actively maintaining tasks, you can't delete it, and you must update the service to a desired task count of zero. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p> <note> <p>When you delete a service, if there are still running tasks that require cleanup, the service status moves from <code>ACTIVE</code> to <code>DRAINING</code>, and the service is no longer visible in the console or in the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a> API operation. After all tasks have transitioned to either <code>STOPPING</code> or <code>STOPPED</code> status, the service status moves from <code>DRAINING</code> to <code>INACTIVE</code>. Services in the <code>DRAINING</code> or <code>INACTIVE</code> status can still be viewed with the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServices.html">DescribeServices</a> API operation. However, in the future, <code>INACTIVE</code> services may be cleaned up and purged from Amazon ECS record keeping, and <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServices.html">DescribeServices</a> calls on those services return a <code>ServiceNotFoundException</code> error.</p> </note> <important> <p>If you attempt to create a new service with the same name as an existing service in either <code>ACTIVE</code> or <code>DRAINING</code> status, you receive an error.</p> </important>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteTaskDefinitionsRequest } from "../models/models_0";
@@ -23,9 +23,11 @@ export interface DeleteTaskDefinitionsCommandInput extends DeleteTaskDefinitions
 export interface DeleteTaskDefinitionsCommandOutput extends DeleteTaskDefinitionsResponse, __MetadataBearer {
 }
 declare const DeleteTaskDefinitionsCommand_base: {
-    new (input: DeleteTaskDefinitionsCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteTaskDefinitionsCommandInput, DeleteTaskDefinitionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteTaskDefinitionsCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteTaskDefinitionsCommandInput, DeleteTaskDefinitionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteTaskDefinitionsCommandInput): import("@smithy/core/client").CommandImpl<DeleteTaskDefinitionsCommandInput, DeleteTaskDefinitionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteTaskDefinitionsCommandInput): import("@smithy/core/client").CommandImpl<DeleteTaskDefinitionsCommandInput, DeleteTaskDefinitionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes one or more task definitions.</p> <p>You must deregister a task definition revision before you delete it. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeregisterTaskDefinition.html">DeregisterTaskDefinition</a>.</p> <p>When you delete a task definition revision, it is immediately transitions from the <code>INACTIVE</code> to <code>DELETE_IN_PROGRESS</code>. Existing tasks and services that reference a <code>DELETE_IN_PROGRESS</code> task definition revision continue to run without disruption. Existing services that reference a <code>DELETE_IN_PROGRESS</code> task definition revision can still scale up or down by modifying the service's desired count.</p> <p>You can't use a <code>DELETE_IN_PROGRESS</code> task definition revision to run new tasks or create new services. You also can't update an existing service to reference a <code>DELETE_IN_PROGRESS</code> task definition revision.</p> <p> A task definition revision will stay in <code>DELETE_IN_PROGRESS</code> status until all the associated tasks and services have been terminated.</p> <p>When you delete all <code>INACTIVE</code> task definition revisions, the task definition name is not displayed in the console and not returned in the API. If a task definition revisions are in the <code>DELETE_IN_PROGRESS</code> state, the task definition name is displayed in the console and returned in the API. The task definition name is retained by Amazon ECS and the revision is incremented the next time you create a task definition with that name.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeleteTaskSetRequest, DeleteTaskSetResponse } from "../models/models_1";
@@ -22,9 +22,11 @@ export interface DeleteTaskSetCommandInput extends DeleteTaskSetRequest {
 export interface DeleteTaskSetCommandOutput extends DeleteTaskSetResponse, __MetadataBearer {
 }
 declare const DeleteTaskSetCommand_base: {
-    new (input: DeleteTaskSetCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteTaskSetCommandInput, DeleteTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeleteTaskSetCommandInput): import("@smithy/smithy-client").CommandImpl<DeleteTaskSetCommandInput, DeleteTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeleteTaskSetCommandInput): import("@smithy/core/client").CommandImpl<DeleteTaskSetCommandInput, DeleteTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeleteTaskSetCommandInput): import("@smithy/core/client").CommandImpl<DeleteTaskSetCommandInput, DeleteTaskSetCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deletes a specified task set within a 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/DeregisterContainerInstanceCommand.d.ts

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeregisterContainerInstanceRequest, DeregisterContainerInstanceResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeregisterContainerInstanceCommandInput extends DeregisterConta
 export interface DeregisterContainerInstanceCommandOutput extends DeregisterContainerInstanceResponse, __MetadataBearer {
 }
 declare const DeregisterContainerInstanceCommand_base: {
-    new (input: DeregisterContainerInstanceCommandInput): import("@smithy/smithy-client").CommandImpl<DeregisterContainerInstanceCommandInput, DeregisterContainerInstanceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeregisterContainerInstanceCommandInput): import("@smithy/smithy-client").CommandImpl<DeregisterContainerInstanceCommandInput, DeregisterContainerInstanceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeregisterContainerInstanceCommandInput): import("@smithy/core/client").CommandImpl<DeregisterContainerInstanceCommandInput, DeregisterContainerInstanceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeregisterContainerInstanceCommandInput): import("@smithy/core/client").CommandImpl<DeregisterContainerInstanceCommandInput, DeregisterContainerInstanceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deregisters an Amazon ECS container instance from the specified cluster. This instance is no longer available to run tasks.</p> <p>If you intend to use the container instance for some other purpose after deregistration, we recommend that you stop all of the tasks running on the container instance before deregistration. That prevents any orphaned tasks from consuming resources.</p> <p>Deregistering a container instance removes the instance from a cluster, but it doesn't terminate the EC2 instance. If you are finished using the instance, be sure to terminate it in the Amazon EC2 console to stop billing.</p> <note> <p>If you terminate a running container instance, Amazon ECS automatically deregisters the instance from your cluster (stopped container instances or instances with disconnected agents aren't automatically deregistered when terminated).</p> </note>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DeregisterTaskDefinitionRequest, DeregisterTaskDefinitionResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DeregisterTaskDefinitionCommandInput extends DeregisterTaskDefi
 export interface DeregisterTaskDefinitionCommandOutput extends DeregisterTaskDefinitionResponse, __MetadataBearer {
 }
 declare const DeregisterTaskDefinitionCommand_base: {
-    new (input: DeregisterTaskDefinitionCommandInput): import("@smithy/smithy-client").CommandImpl<DeregisterTaskDefinitionCommandInput, DeregisterTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DeregisterTaskDefinitionCommandInput): import("@smithy/smithy-client").CommandImpl<DeregisterTaskDefinitionCommandInput, DeregisterTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DeregisterTaskDefinitionCommandInput): import("@smithy/core/client").CommandImpl<DeregisterTaskDefinitionCommandInput, DeregisterTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DeregisterTaskDefinitionCommandInput): import("@smithy/core/client").CommandImpl<DeregisterTaskDefinitionCommandInput, DeregisterTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Deregisters the specified task definition by family and revision. Upon deregistration, the task definition is marked as <code>INACTIVE</code>. Existing tasks and services that reference an <code>INACTIVE</code> task definition continue to run without disruption. Existing services that reference an <code>INACTIVE</code> task definition can still scale up or down by modifying the service's desired count. If you want to delete a task definition revision, you must first deregister the task definition revision.</p> <p>You can't use an <code>INACTIVE</code> task definition to run new tasks or create new services, and you can't update an existing service to reference an <code>INACTIVE</code> task definition. However, there may be up to a 10-minute window following deregistration where these restrictions have not yet taken effect.</p> <note> <p>At this time, <code>INACTIVE</code> task definitions remain discoverable in your account indefinitely. However, this behavior is subject to change in the future. We don't recommend that you rely on <code>INACTIVE</code> task definitions persisting beyond the lifecycle of any associated tasks and services.</p> </note> <p>You must deregister a task definition revision before you delete it. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteTaskDefinitions.html">DeleteTaskDefinitions</a>.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeCapacityProvidersRequest, DescribeCapacityProvidersResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeCapacityProvidersCommandInput extends DescribeCapacityP
 export interface DescribeCapacityProvidersCommandOutput extends DescribeCapacityProvidersResponse, __MetadataBearer {
 }
 declare const DescribeCapacityProvidersCommand_base: {
-    new (input: DescribeCapacityProvidersCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeCapacityProvidersCommandInput, DescribeCapacityProvidersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (...[input]: [] | [DescribeCapacityProvidersCommandInput]): import("@smithy/smithy-client").CommandImpl<DescribeCapacityProvidersCommandInput, DescribeCapacityProvidersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeCapacityProvidersCommandInput): import("@smithy/core/client").CommandImpl<DescribeCapacityProvidersCommandInput, DescribeCapacityProvidersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (...[input]: [] | [DescribeCapacityProvidersCommandInput]): import("@smithy/core/client").CommandImpl<DescribeCapacityProvidersCommandInput, DescribeCapacityProvidersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes one or more of your capacity providers.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeClustersRequest, DescribeClustersResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeClustersCommandInput extends DescribeClustersRequest {
 export interface DescribeClustersCommandOutput extends DescribeClustersResponse, __MetadataBearer {
 }
 declare const DescribeClustersCommand_base: {
-    new (input: DescribeClustersCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeClustersCommandInput, DescribeClustersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (...[input]: [] | [DescribeClustersCommandInput]): import("@smithy/smithy-client").CommandImpl<DescribeClustersCommandInput, DescribeClustersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeClustersCommandInput): import("@smithy/core/client").CommandImpl<DescribeClustersCommandInput, DescribeClustersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (...[input]: [] | [DescribeClustersCommandInput]): import("@smithy/core/client").CommandImpl<DescribeClustersCommandInput, DescribeClustersCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes one or more of your clusters.</p> <p> For CLI examples, see <a href="https://github.com/aws/aws-cli/blob/develop/awscli/examples/ecs/describe-clusters.rst">describe-clusters.rst</a> on GitHub.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeContainerInstancesRequest, DescribeContainerInstancesResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeContainerInstancesCommandInput extends DescribeContaine
 export interface DescribeContainerInstancesCommandOutput extends DescribeContainerInstancesResponse, __MetadataBearer {
 }
 declare const DescribeContainerInstancesCommand_base: {
-    new (input: DescribeContainerInstancesCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeContainerInstancesCommandInput, DescribeContainerInstancesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DescribeContainerInstancesCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeContainerInstancesCommandInput, DescribeContainerInstancesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeContainerInstancesCommandInput): import("@smithy/core/client").CommandImpl<DescribeContainerInstancesCommandInput, DescribeContainerInstancesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DescribeContainerInstancesCommandInput): import("@smithy/core/client").CommandImpl<DescribeContainerInstancesCommandInput, DescribeContainerInstancesCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes one or more container instances. Returns metadata about each container instance requested.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeDaemonRequest, DescribeDaemonResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeDaemonCommandInput extends DescribeDaemonRequest {
 export interface DescribeDaemonCommandOutput extends DescribeDaemonResponse, __MetadataBearer {
 }
 declare const DescribeDaemonCommand_base: {
-    new (input: DescribeDaemonCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonCommandInput, DescribeDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DescribeDaemonCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonCommandInput, DescribeDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeDaemonCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonCommandInput, DescribeDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DescribeDaemonCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonCommandInput, DescribeDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes the specified daemon.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeDaemonDeploymentsRequest, DescribeDaemonDeploymentsResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeDaemonDeploymentsCommandInput extends DescribeDaemonDep
 export interface DescribeDaemonDeploymentsCommandOutput extends DescribeDaemonDeploymentsResponse, __MetadataBearer {
 }
 declare const DescribeDaemonDeploymentsCommand_base: {
-    new (input: DescribeDaemonDeploymentsCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonDeploymentsCommandInput, DescribeDaemonDeploymentsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DescribeDaemonDeploymentsCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonDeploymentsCommandInput, DescribeDaemonDeploymentsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeDaemonDeploymentsCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonDeploymentsCommandInput, DescribeDaemonDeploymentsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DescribeDaemonDeploymentsCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonDeploymentsCommandInput, DescribeDaemonDeploymentsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes one or more of your daemon deployments.</p> <p>A daemon deployment orchestrates the progressive rollout of daemon task updates across container instances managed by the daemon's capacity providers. Each deployment includes circuit breaker and alarm-based rollback capabilities.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeDaemonRevisionsRequest, DescribeDaemonRevisionsResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeDaemonRevisionsCommandInput extends DescribeDaemonRevis
 export interface DescribeDaemonRevisionsCommandOutput extends DescribeDaemonRevisionsResponse, __MetadataBearer {
 }
 declare const DescribeDaemonRevisionsCommand_base: {
-    new (input: DescribeDaemonRevisionsCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonRevisionsCommandInput, DescribeDaemonRevisionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DescribeDaemonRevisionsCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonRevisionsCommandInput, DescribeDaemonRevisionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeDaemonRevisionsCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonRevisionsCommandInput, DescribeDaemonRevisionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DescribeDaemonRevisionsCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonRevisionsCommandInput, DescribeDaemonRevisionsCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes one or more of your daemon revisions.</p> <p>A daemon revision is a snapshot of a daemon's configuration at the time a deployment was initiated. It captures the daemon task definition, container images, tag propagation, and execute command settings. Daemon revisions are immutable.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeDaemonTaskDefinitionRequest, DescribeDaemonTaskDefinitionResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeDaemonTaskDefinitionCommandInput extends DescribeDaemon
 export interface DescribeDaemonTaskDefinitionCommandOutput extends DescribeDaemonTaskDefinitionResponse, __MetadataBearer {
 }
 declare const DescribeDaemonTaskDefinitionCommand_base: {
-    new (input: DescribeDaemonTaskDefinitionCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonTaskDefinitionCommandInput, DescribeDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DescribeDaemonTaskDefinitionCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeDaemonTaskDefinitionCommandInput, DescribeDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeDaemonTaskDefinitionCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonTaskDefinitionCommandInput, DescribeDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DescribeDaemonTaskDefinitionCommandInput): import("@smithy/core/client").CommandImpl<DescribeDaemonTaskDefinitionCommandInput, DescribeDaemonTaskDefinitionCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Describes a daemon task definition. You can specify a <code>family</code> and <code>revision</code> to find information about a specific daemon task definition, or you can simply specify the family to find the latest <code>ACTIVE</code> revision in that family.</p>

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

@@ -1,4 +1,4 @@
-import { Command as $Command } from "@smithy/smithy-client";
+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 { DescribeExpressGatewayServiceRequest, DescribeExpressGatewayServiceResponse } from "../models/models_0";
@@ -22,9 +22,11 @@ export interface DescribeExpressGatewayServiceCommandInput extends DescribeExpre
 export interface DescribeExpressGatewayServiceCommandOutput extends DescribeExpressGatewayServiceResponse, __MetadataBearer {
 }
 declare const DescribeExpressGatewayServiceCommand_base: {
-    new (input: DescribeExpressGatewayServiceCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeExpressGatewayServiceCommandInput, DescribeExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: DescribeExpressGatewayServiceCommandInput): import("@smithy/smithy-client").CommandImpl<DescribeExpressGatewayServiceCommandInput, DescribeExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    new (input: DescribeExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<DescribeExpressGatewayServiceCommandInput, DescribeExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: DescribeExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<DescribeExpressGatewayServiceCommandInput, DescribeExpressGatewayServiceCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): {
+        [x: string]: unknown;
+    };
 };
 /**
  * <p>Retrieves detailed information about an Express service, including current status, configuration, managed infrastructure, and service revisions.</p> <p>Returns comprehensive service details, active service revisions, ingress paths with endpoints, and managed Amazon Web Services resource status including load balancers and auto-scaling policies.</p> <p>Use the <code>include</code> parameter to retrieve additional information such as resource tags.</p>