@aws-sdk/client-ecs 3.1077.0 → 3.1078.0

package/dist-es/commands/SubmitContainerStateChangeCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { SubmitContainerStateChange$ } from "../schemas/schemas_0";
-export { $Command };
-export class SubmitContainerStateChangeCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "SubmitContainerStateChange", {})
-    .n("ECSClient", "SubmitContainerStateChangeCommand")
-    .sc(SubmitContainerStateChange$)
-    .build() {
+export class SubmitContainerStateChangeCommand extends command(_ep0, _mw0, "SubmitContainerStateChange", SubmitContainerStateChange$) {
 }

package/dist-es/commands/SubmitTaskStateChangeCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { SubmitTaskStateChange$ } from "../schemas/schemas_0";
-export { $Command };
-export class SubmitTaskStateChangeCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "SubmitTaskStateChange", {})
-    .n("ECSClient", "SubmitTaskStateChangeCommand")
-    .sc(SubmitTaskStateChange$)
-    .build() {
+export class SubmitTaskStateChangeCommand extends command(_ep0, _mw0, "SubmitTaskStateChange", SubmitTaskStateChange$) {
 }

package/dist-es/commands/TagResourceCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { TagResource$ } from "../schemas/schemas_0";
-export { $Command };
-export class TagResourceCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "TagResource", {})
-    .n("ECSClient", "TagResourceCommand")
-    .sc(TagResource$)
-    .build() {
+export class TagResourceCommand extends command(_ep0, _mw0, "TagResource", TagResource$) {
 }

package/dist-es/commands/UntagResourceCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UntagResource$ } from "../schemas/schemas_0";
-export { $Command };
-export class UntagResourceCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UntagResource", {})
-    .n("ECSClient", "UntagResourceCommand")
-    .sc(UntagResource$)
-    .build() {
+export class UntagResourceCommand extends command(_ep0, _mw0, "UntagResource", UntagResource$) {
 }

package/dist-es/commands/UpdateCapacityProviderCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateCapacityProvider$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateCapacityProviderCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateCapacityProvider", {})
-    .n("ECSClient", "UpdateCapacityProviderCommand")
-    .sc(UpdateCapacityProvider$)
-    .build() {
+export class UpdateCapacityProviderCommand extends command(_ep0, _mw0, "UpdateCapacityProvider", UpdateCapacityProvider$) {
 }

package/dist-es/commands/UpdateClusterCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateCluster$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateClusterCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateCluster", {})
-    .n("ECSClient", "UpdateClusterCommand")
-    .sc(UpdateCluster$)
-    .build() {
+export class UpdateClusterCommand extends command(_ep0, _mw0, "UpdateCluster", UpdateCluster$) {
 }

package/dist-es/commands/UpdateClusterSettingsCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateClusterSettings$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateClusterSettingsCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateClusterSettings", {})
-    .n("ECSClient", "UpdateClusterSettingsCommand")
-    .sc(UpdateClusterSettings$)
-    .build() {
+export class UpdateClusterSettingsCommand extends command(_ep0, _mw0, "UpdateClusterSettings", UpdateClusterSettings$) {
 }

package/dist-es/commands/UpdateContainerAgentCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateContainerAgent$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateContainerAgentCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateContainerAgent", {})
-    .n("ECSClient", "UpdateContainerAgentCommand")
-    .sc(UpdateContainerAgent$)
-    .build() {
+export class UpdateContainerAgentCommand extends command(_ep0, _mw0, "UpdateContainerAgent", UpdateContainerAgent$) {
 }

package/dist-es/commands/UpdateContainerInstancesStateCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateContainerInstancesState$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateContainerInstancesStateCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateContainerInstancesState", {})
-    .n("ECSClient", "UpdateContainerInstancesStateCommand")
-    .sc(UpdateContainerInstancesState$)
-    .build() {
+export class UpdateContainerInstancesStateCommand extends command(_ep0, _mw0, "UpdateContainerInstancesState", UpdateContainerInstancesState$) {
 }

package/dist-es/commands/UpdateDaemonCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateDaemon$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateDaemonCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateDaemon", {})
-    .n("ECSClient", "UpdateDaemonCommand")
-    .sc(UpdateDaemon$)
-    .build() {
+export class UpdateDaemonCommand extends command(_ep0, _mw0, "UpdateDaemon", UpdateDaemon$) {
 }

package/dist-es/commands/UpdateExpressGatewayServiceCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateExpressGatewayService$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateExpressGatewayServiceCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateExpressGatewayService", {})
-    .n("ECSClient", "UpdateExpressGatewayServiceCommand")
-    .sc(UpdateExpressGatewayService$)
-    .build() {
+export class UpdateExpressGatewayServiceCommand extends command(_ep0, _mw0, "UpdateExpressGatewayService", UpdateExpressGatewayService$) {
 }

package/dist-es/commands/UpdateServiceCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateService$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateServiceCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateService", {})
-    .n("ECSClient", "UpdateServiceCommand")
-    .sc(UpdateService$)
-    .build() {
+export class UpdateServiceCommand extends command(_ep0, _mw0, "UpdateService", UpdateService$) {
 }

package/dist-es/commands/UpdateServicePrimaryTaskSetCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateServicePrimaryTaskSet$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateServicePrimaryTaskSetCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateServicePrimaryTaskSet", {})
-    .n("ECSClient", "UpdateServicePrimaryTaskSetCommand")
-    .sc(UpdateServicePrimaryTaskSet$)
-    .build() {
+export class UpdateServicePrimaryTaskSetCommand extends command(_ep0, _mw0, "UpdateServicePrimaryTaskSet", UpdateServicePrimaryTaskSet$) {
 }

package/dist-es/commands/UpdateTaskProtectionCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateTaskProtection$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateTaskProtectionCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateTaskProtection", {})
-    .n("ECSClient", "UpdateTaskProtectionCommand")
-    .sc(UpdateTaskProtection$)
-    .build() {
+export class UpdateTaskProtectionCommand extends command(_ep0, _mw0, "UpdateTaskProtection", UpdateTaskProtection$) {
 }

package/dist-es/commands/UpdateTaskSetCommand.js

@@ -1,16 +1,4 @@
-import { Command as $Command } from "@smithy/core/client";
-import { getEndpointPlugin } from "@smithy/core/endpoints";
-import { commonParams } from "../endpoint/EndpointParameters";
+import { _ep0, _mw0, command } from "../commandBuilder";
 import { UpdateTaskSet$ } from "../schemas/schemas_0";
-export { $Command };
-export class UpdateTaskSetCommand extends $Command
-    .classBuilder()
-    .ep(commonParams)
-    .m(function (Command, cs, config, o) {
-    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
-})
-    .s("AmazonEC2ContainerServiceV20141113", "UpdateTaskSet", {})
-    .n("ECSClient", "UpdateTaskSetCommand")
-    .sc(UpdateTaskSet$)
-    .build() {
+export class UpdateTaskSetCommand extends command(_ep0, _mw0, "UpdateTaskSet", UpdateTaskSet$) {
 }

package/dist-es/index.js

@@ -1,6 +1,7 @@
 export * from "./ECSClient";
 export * from "./ECS";
 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/commandBuilder.d.ts

@@ -0,0 +1,18 @@
+import type { EndpointParameterInstructions } from "@smithy/types";
+import type { ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "./ECSClient";
+/**
+ * @internal
+ */
+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;
+};
+/**
+ * @internal
+ */
+export declare const _ep0: EndpointParameterInstructions;
+/**
+ * @internal
+ */
+export declare const _mw0: (Command: any, cs: any, config: any, o: any) => never[];

package/dist-types/commands/ContinueServiceDeploymentCommand.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 { ContinueServiceDeploymentRequest, ContinueServiceDeploymentResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface ContinueServiceDeploymentCommandInput extends ContinueServiceDe
 export interface ContinueServiceDeploymentCommandOutput extends ContinueServiceDeploymentResponse, __MetadataBearer {
 }
 declare const ContinueServiceDeploymentCommand_base: {
-    new (input: ContinueServiceDeploymentCommandInput): import("@smithy/core/client").CommandImpl<ContinueServiceDeploymentCommandInput, ContinueServiceDeploymentCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: ContinueServiceDeploymentCommandInput): import("@smithy/core/client").CommandImpl<ContinueServiceDeploymentCommandInput, ContinueServiceDeploymentCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: ContinueServiceDeploymentCommandInput): import("@smithy/core/client").CommandImpl<ContinueServiceDeploymentCommandInput, ContinueServiceDeploymentCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: ContinueServiceDeploymentCommandInput): import("@smithy/core/client").CommandImpl<ContinueServiceDeploymentCommandInput, ContinueServiceDeploymentCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Continues or rolls back an Amazon ECS service deployment that is paused at a lifecycle hook.</p> <p>When a service deployment reaches a lifecycle stage that has a <code>PAUSE</code> hook configured, the deployment pauses and waits for an explicit action. Use this API to either continue the deployment to the next stage or roll back to the previous service revision.</p> <p>To find the <code>hookId</code> of the paused hook, call <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServiceDeployments.html">DescribeServiceDeployments</a> and inspect the <code>lifecycleHookDetails</code> field.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/continue-service-deployment.html">Continuing Amazon ECS service deployments</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>

package/dist-types/commands/CreateCapacityProviderCommand.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 { CreateCapacityProviderRequest, CreateCapacityProviderResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface CreateCapacityProviderCommandInput extends CreateCapacityProvid
 export interface CreateCapacityProviderCommandOutput extends CreateCapacityProviderResponse, __MetadataBearer {
 }
 declare const CreateCapacityProviderCommand_base: {
-    new (input: CreateCapacityProviderCommandInput): import("@smithy/core/client").CommandImpl<CreateCapacityProviderCommandInput, CreateCapacityProviderCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: CreateCapacityProviderCommandInput): import("@smithy/core/client").CommandImpl<CreateCapacityProviderCommandInput, CreateCapacityProviderCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: CreateCapacityProviderCommandInput): import("@smithy/core/client").CommandImpl<CreateCapacityProviderCommandInput, CreateCapacityProviderCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: CreateCapacityProviderCommandInput): import("@smithy/core/client").CommandImpl<CreateCapacityProviderCommandInput, CreateCapacityProviderCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Creates a capacity provider. Capacity providers are associated with a cluster and are used in capacity provider strategies to facilitate cluster auto scaling. You can create capacity providers for Amazon ECS Managed Instances and EC2 instances. Fargate has the predefined <code>FARGATE</code> and <code>FARGATE_SPOT</code> capacity providers.</p>

package/dist-types/commands/CreateClusterCommand.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 { CreateClusterRequest, CreateClusterResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface CreateClusterCommandInput extends CreateClusterRequest {
 export interface CreateClusterCommandOutput extends CreateClusterResponse, __MetadataBearer {
 }
 declare const CreateClusterCommand_base: {
-    new (input: CreateClusterCommandInput): import("@smithy/core/client").CommandImpl<CreateClusterCommandInput, CreateClusterCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (...[input]: [] | [CreateClusterCommandInput]): import("@smithy/core/client").CommandImpl<CreateClusterCommandInput, CreateClusterCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: CreateClusterCommandInput): import("@smithy/core/client").CommandImpl<CreateClusterCommandInput, CreateClusterCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (...[input]: [] | [CreateClusterCommandInput]): import("@smithy/core/client").CommandImpl<CreateClusterCommandInput, CreateClusterCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Creates a new Amazon ECS cluster. By default, your account receives a <code>default</code> cluster when you launch your first container instance. However, you can create your own cluster with a unique name.</p> <note> <p>When you call the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html">CreateCluster</a> API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account. This is so that it can manage required resources in other Amazon Web Services services on your behalf. However, if the user that makes the call doesn't have permissions to create the service-linked role, it isn't created. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using service-linked roles for Amazon ECS</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </note>

package/dist-types/commands/CreateDaemonCommand.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 { CreateDaemonRequest, CreateDaemonResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface CreateDaemonCommandInput extends CreateDaemonRequest {
 export interface CreateDaemonCommandOutput extends CreateDaemonResponse, __MetadataBearer {
 }
 declare const CreateDaemonCommand_base: {
-    new (input: CreateDaemonCommandInput): import("@smithy/core/client").CommandImpl<CreateDaemonCommandInput, CreateDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: CreateDaemonCommandInput): import("@smithy/core/client").CommandImpl<CreateDaemonCommandInput, CreateDaemonCommandOutput, ECSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: CreateDaemonCommandInput): import("@smithy/core/client").CommandImpl<CreateDaemonCommandInput, CreateDaemonCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: CreateDaemonCommandInput): import("@smithy/core/client").CommandImpl<CreateDaemonCommandInput, CreateDaemonCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Creates a new daemon in the specified cluster and capacity providers. A daemon deploys cross-cutting software agents such as security monitoring, telemetry, and logging independently across your Amazon ECS infrastructure.</p> <p>Amazon ECS deploys exactly one daemon task on each container instance of the specified capacity providers. When a container instance registers with the cluster, Amazon ECS automatically starts daemon tasks. Amazon ECS starts a daemon task before scheduling other tasks.</p> <p>Daemons are essential for instance health - if a daemon task stops, Amazon ECS automatically drains and replaces that container instance.</p> <note> <p>ECS Managed Daemons is only supported for Amazon ECS Managed Instances Capacity Providers.</p> </note>

package/dist-types/commands/CreateExpressGatewayServiceCommand.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 { CreateExpressGatewayServiceRequest, CreateExpressGatewayServiceResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface CreateExpressGatewayServiceCommandInput extends CreateExpressGa
 export interface CreateExpressGatewayServiceCommandOutput extends CreateExpressGatewayServiceResponse, __MetadataBearer {
 }
 declare const CreateExpressGatewayServiceCommand_base: {
-    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;
-    };
+    new (input: CreateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<CreateExpressGatewayServiceCommandInput, CreateExpressGatewayServiceCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: CreateExpressGatewayServiceCommandInput): import("@smithy/core/client").CommandImpl<CreateExpressGatewayServiceCommandInput, CreateExpressGatewayServiceCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Creates an Express service that simplifies deploying containerized web applications on Amazon ECS with managed Amazon Web Services infrastructure. This operation provisions and configures Application Load Balancers, target groups, security groups, and auto-scaling policies automatically.</p> <p>Specify a primary container configuration with your application image and basic settings. Amazon ECS creates the necessary Amazon Web Services resources for traffic distribution, health monitoring, network access control, and capacity management.</p> <p>Provide an execution role for task operations and an infrastructure role for managing Amazon Web Services resources on your behalf.</p>

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

package/dist-types/commands/CreateTaskSetCommand.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 { CreateTaskSetRequest, CreateTaskSetResponse } from "../models/models_1";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface CreateTaskSetCommandInput extends CreateTaskSetRequest {
 export interface CreateTaskSetCommandOutput extends CreateTaskSetResponse, __MetadataBearer {
 }
 declare const CreateTaskSetCommand_base: {
-    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;
-    };
+    new (input: CreateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: CreateTaskSetCommandInput): import("@smithy/core/client").CommandImpl<CreateTaskSetCommandInput, CreateTaskSetCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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,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 { DeleteAccountSettingRequest, DeleteAccountSettingResponse } from "../models/models_0";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface DeleteAccountSettingCommandInput extends DeleteAccountSettingRe
 export interface DeleteAccountSettingCommandOutput extends DeleteAccountSettingResponse, __MetadataBearer {
 }
 declare const DeleteAccountSettingCommand_base: {
-    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;
-    };
+    new (input: DeleteAccountSettingCommandInput): import("@smithy/core/client").CommandImpl<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: DeleteAccountSettingCommandInput): import("@smithy/core/client").CommandImpl<DeleteAccountSettingCommandInput, DeleteAccountSettingCommandOutput, import("..").ECSClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Disables an account setting for a specified user, role, or the root user for an account.</p>