@aws-sdk/client-ecs 3.1069.0 → 3.1071.0

package/dist-cjs/schemas/schemas_0.js

@@ -1057,8 +1057,8 @@ const _tC = "timeoutConfiguration";
 const _tCa = "targetCapacity";
 const _tCar = "targetConfiguration";
 const _tD = "taskDefinition";
-const _tDA = "taskDefinitionArns";
-const _tDAa = "taskDefinitionArn";
+const _tDA = "taskDefinitionArn";
+const _tDAa = "taskDefinitionArns";
 const _tDIC = "totalDrainingInstanceCount";
 const _tDR = "targetDaemonRevision";
 const _tDRA = "targetDaemonRevisionArn";
@@ -1572,8 +1572,8 @@ const CreatedAt$ = [3, n0, _CA,
 exports.CreatedAt$ = CreatedAt$;
 const CreateExpressGatewayServiceRequest$ = [3, n0, _CEGSR,
     0,
-    [_eRA, _iRA, _pC, _sN, _cl, _hCP, _tRA, _nC, _cp, _me, _sTc, _ta],
-    [0, 0, [() => ExpressGatewayContainer$, 0], 0, 0, 0, 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$, () => Tags], 3
+    [_iRA, _eRA, _sN, _cl, _hCP, _pC, _tRA, _nC, _cp, _me, _sTc, _ta, _tDA],
+    [0, 0, 0, 0, 0, [() => ExpressGatewayContainer$, 0], 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$, () => Tags, 0], 1
 ];
 exports.CreateExpressGatewayServiceRequest$ = CreateExpressGatewayServiceRequest$;
 const CreateExpressGatewayServiceResponse$ = [3, n0, _CEGSRr,
@@ -2214,8 +2214,8 @@ const ExpressGatewayServiceAwsLogsConfiguration$ = [3, n0, _EGSALC,
 exports.ExpressGatewayServiceAwsLogsConfiguration$ = ExpressGatewayServiceAwsLogsConfiguration$;
 const ExpressGatewayServiceConfiguration$ = [3, n0, _EGSC,
     0,
-    [_sRAe, _eRA, _tRA, _cp, _me, _nC, _hCP, _pC, _sTc, _iP, _cAr],
-    [0, 0, 0, 0, 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, [() => ExpressGatewayContainer$, 0], () => ExpressGatewayScalingTarget$, () => IngressPathSummaries, 4]
+    [_sRAe, _eRA, _tRA, _tDA, _cp, _me, _nC, _hCP, _pC, _sTc, _iP, _cAr],
+    [0, 0, 0, 0, 0, 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, [() => ExpressGatewayContainer$, 0], () => ExpressGatewayScalingTarget$, () => IngressPathSummaries, 4]
 ];
 exports.ExpressGatewayServiceConfiguration$ = ExpressGatewayServiceConfiguration$;
 const ExpressGatewayServiceNetworkConfiguration$ = [3, n0, _EGSNC,
@@ -2508,7 +2508,7 @@ const ListTaskDefinitionsRequest$ = [3, n0, _LTDR,
 exports.ListTaskDefinitionsRequest$ = ListTaskDefinitionsRequest$;
 const ListTaskDefinitionsResponse$ = [3, n0, _LTDRi,
     0,
-    [_tDA, _nT],
+    [_tDAa, _nT],
     [64 | 0, 0]
 ];
 exports.ListTaskDefinitionsResponse$ = ListTaskDefinitionsResponse$;
@@ -3138,13 +3138,13 @@ const TagResourceResponse$ = [3, n0, _TRRa,
 exports.TagResourceResponse$ = TagResourceResponse$;
 const Task$ = [3, n0, _Ta,
     0,
-    [_a, _at, _aZ, _cPN, _cA, _conn, _cAon, _cIA, _conta, _cp, _cAr, _dSe, _eEC, _eSA, _g, _hS, _iAn, _lS, _lT, _me, _ov, _pV, _pF, _pSA, _pSAu, _sA, _sB, _sCtop, _sAt, _sRt, _sAto, _ta, _tA, _tDAa, _ve, _eSp, _fES],
+    [_a, _at, _aZ, _cPN, _cA, _conn, _cAon, _cIA, _conta, _cp, _cAr, _dSe, _eEC, _eSA, _g, _hS, _iAn, _lS, _lT, _me, _ov, _pV, _pF, _pSA, _pSAu, _sA, _sB, _sCtop, _sAt, _sRt, _sAto, _ta, _tA, _tDA, _ve, _eSp, _fES],
     [() => Attachments, () => Attributes, 0, 0, 0, 0, 4, 0, () => Containers, 0, 4, 0, 2, 4, 0, 0, () => InferenceAccelerators, 0, 0, 0, [() => TaskOverride$, 0], 0, 0, 4, 4, 4, 0, 0, 4, 0, 4, () => Tags, 0, 0, 1, () => EphemeralStorage$, () => TaskEphemeralStorage$]
 ];
 exports.Task$ = Task$;
 const TaskDefinition$ = [3, n0, _TD,
     0,
-    [_tDAa, _cD, _f, _tRA, _eRA, _nM, _re, _vo, _st, _rAeq, _pCl, _comp, _rPu, _rCe, _cp, _me, _iAn, _pMi, _iM, _pCr, _rAe, _dAer, _dRAe, _rB, _eSp, _eFI],
+    [_tDA, _cD, _f, _tRA, _eRA, _nM, _re, _vo, _st, _rAeq, _pCl, _comp, _rPu, _rCe, _cp, _me, _iAn, _pMi, _iM, _pCr, _rAe, _dAer, _dRAe, _rB, _eSp, _eFI],
     [0, [() => ContainerDefinitions, 0], 0, 0, 0, 0, 1, () => VolumeList, 0, () => RequiresAttributes, () => TaskDefinitionPlacementConstraints, 64 | 0, () => RuntimePlatform$, 64 | 0, 0, 0, () => InferenceAccelerators, 0, 0, () => ProxyConfiguration$, 4, 4, 4, 0, () => EphemeralStorage$, 2]
 ];
 exports.TaskDefinition$ = TaskDefinition$;
@@ -3306,8 +3306,8 @@ const UpdatedExpressGatewayService$ = [3, n0, _UEGS,
 exports.UpdatedExpressGatewayService$ = UpdatedExpressGatewayService$;
 const UpdateExpressGatewayServiceRequest$ = [3, n0, _UEGSR,
     0,
-    [_sAe, _eRA, _hCP, _pC, _tRA, _nC, _cp, _me, _sTc],
-    [0, 0, 0, [() => ExpressGatewayContainer$, 0], 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$], 1
+    [_sAe, _eRA, _hCP, _pC, _tRA, _nC, _cp, _me, _sTc, _tDA],
+    [0, 0, 0, [() => ExpressGatewayContainer$, 0], 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$, 0], 1
 ];
 exports.UpdateExpressGatewayServiceRequest$ = UpdateExpressGatewayServiceRequest$;
 const UpdateExpressGatewayServiceResponse$ = [3, n0, _UEGSRp,

package/dist-es/schemas/schemas_0.js

@@ -1057,8 +1057,8 @@ const _tC = "timeoutConfiguration";
 const _tCa = "targetCapacity";
 const _tCar = "targetConfiguration";
 const _tD = "taskDefinition";
-const _tDA = "taskDefinitionArns";
-const _tDAa = "taskDefinitionArn";
+const _tDA = "taskDefinitionArn";
+const _tDAa = "taskDefinitionArns";
 const _tDIC = "totalDrainingInstanceCount";
 const _tDR = "targetDaemonRevision";
 const _tDRA = "targetDaemonRevisionArn";
@@ -1503,8 +1503,8 @@ export var CreatedAt$ = [3, n0, _CA,
 ];
 export var CreateExpressGatewayServiceRequest$ = [3, n0, _CEGSR,
     0,
-    [_eRA, _iRA, _pC, _sN, _cl, _hCP, _tRA, _nC, _cp, _me, _sTc, _ta],
-    [0, 0, [() => ExpressGatewayContainer$, 0], 0, 0, 0, 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$, () => Tags], 3
+    [_iRA, _eRA, _sN, _cl, _hCP, _pC, _tRA, _nC, _cp, _me, _sTc, _ta, _tDA],
+    [0, 0, 0, 0, 0, [() => ExpressGatewayContainer$, 0], 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$, () => Tags, 0], 1
 ];
 export var CreateExpressGatewayServiceResponse$ = [3, n0, _CEGSRr,
     0,
@@ -2038,8 +2038,8 @@ export var ExpressGatewayServiceAwsLogsConfiguration$ = [3, n0, _EGSALC,
 ];
 export var ExpressGatewayServiceConfiguration$ = [3, n0, _EGSC,
     0,
-    [_sRAe, _eRA, _tRA, _cp, _me, _nC, _hCP, _pC, _sTc, _iP, _cAr],
-    [0, 0, 0, 0, 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, [() => ExpressGatewayContainer$, 0], () => ExpressGatewayScalingTarget$, () => IngressPathSummaries, 4]
+    [_sRAe, _eRA, _tRA, _tDA, _cp, _me, _nC, _hCP, _pC, _sTc, _iP, _cAr],
+    [0, 0, 0, 0, 0, 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, [() => ExpressGatewayContainer$, 0], () => ExpressGatewayScalingTarget$, () => IngressPathSummaries, 4]
 ];
 export var ExpressGatewayServiceNetworkConfiguration$ = [3, n0, _EGSNC,
     0,
@@ -2283,7 +2283,7 @@ export var ListTaskDefinitionsRequest$ = [3, n0, _LTDR,
 ];
 export var ListTaskDefinitionsResponse$ = [3, n0, _LTDRi,
     0,
-    [_tDA, _nT],
+    [_tDAa, _nT],
     [64 | 0, 0]
 ];
 export var ListTasksRequest$ = [3, n0, _LTR,
@@ -2808,12 +2808,12 @@ export var TagResourceResponse$ = [3, n0, _TRRa,
 ];
 export var Task$ = [3, n0, _Ta,
     0,
-    [_a, _at, _aZ, _cPN, _cA, _conn, _cAon, _cIA, _conta, _cp, _cAr, _dSe, _eEC, _eSA, _g, _hS, _iAn, _lS, _lT, _me, _ov, _pV, _pF, _pSA, _pSAu, _sA, _sB, _sCtop, _sAt, _sRt, _sAto, _ta, _tA, _tDAa, _ve, _eSp, _fES],
+    [_a, _at, _aZ, _cPN, _cA, _conn, _cAon, _cIA, _conta, _cp, _cAr, _dSe, _eEC, _eSA, _g, _hS, _iAn, _lS, _lT, _me, _ov, _pV, _pF, _pSA, _pSAu, _sA, _sB, _sCtop, _sAt, _sRt, _sAto, _ta, _tA, _tDA, _ve, _eSp, _fES],
     [() => Attachments, () => Attributes, 0, 0, 0, 0, 4, 0, () => Containers, 0, 4, 0, 2, 4, 0, 0, () => InferenceAccelerators, 0, 0, 0, [() => TaskOverride$, 0], 0, 0, 4, 4, 4, 0, 0, 4, 0, 4, () => Tags, 0, 0, 1, () => EphemeralStorage$, () => TaskEphemeralStorage$]
 ];
 export var TaskDefinition$ = [3, n0, _TD,
     0,
-    [_tDAa, _cD, _f, _tRA, _eRA, _nM, _re, _vo, _st, _rAeq, _pCl, _comp, _rPu, _rCe, _cp, _me, _iAn, _pMi, _iM, _pCr, _rAe, _dAer, _dRAe, _rB, _eSp, _eFI],
+    [_tDA, _cD, _f, _tRA, _eRA, _nM, _re, _vo, _st, _rAeq, _pCl, _comp, _rPu, _rCe, _cp, _me, _iAn, _pMi, _iM, _pCr, _rAe, _dAer, _dRAe, _rB, _eSp, _eFI],
     [0, [() => ContainerDefinitions, 0], 0, 0, 0, 0, 1, () => VolumeList, 0, () => RequiresAttributes, () => TaskDefinitionPlacementConstraints, 64 | 0, () => RuntimePlatform$, 64 | 0, 0, 0, () => InferenceAccelerators, 0, 0, () => ProxyConfiguration$, 4, 4, 4, 0, () => EphemeralStorage$, 2]
 ];
 export var TaskDefinitionPlacementConstraint$ = [3, n0, _TDPC,
@@ -2948,8 +2948,8 @@ export var UpdatedExpressGatewayService$ = [3, n0, _UEGS,
 ];
 export var UpdateExpressGatewayServiceRequest$ = [3, n0, _UEGSR,
     0,
-    [_sAe, _eRA, _hCP, _pC, _tRA, _nC, _cp, _me, _sTc],
-    [0, 0, 0, [() => ExpressGatewayContainer$, 0], 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$], 1
+    [_sAe, _eRA, _hCP, _pC, _tRA, _nC, _cp, _me, _sTc, _tDA],
+    [0, 0, 0, [() => ExpressGatewayContainer$, 0], 0, () => ExpressGatewayServiceNetworkConfiguration$, 0, 0, () => ExpressGatewayScalingTarget$, 0], 1
 ];
 export var UpdateExpressGatewayServiceResponse$ = [3, n0, _UEGSRp,
     0,

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

@@ -29,7 +29,7 @@ declare const ContinueServiceDeploymentCommand_base: {
     };
 };
 /**
- * <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>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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -70,7 +70,7 @@ declare const ContinueServiceDeploymentCommand_base: {
  *  <p>These errors are usually caused by a server issue.</p>
  *
  * @throws {@link ServiceDeploymentNotFoundException} (client fault)
- *  <p>The service deploy ARN that you specified in the <code>StopServiceDeployment</code> doesn't exist. You can use <code>ListServiceDeployments</code> to retrieve the service deployment ARNs.</p>
+ *  <p>The service deploy ARN that you specified in the <code>ContinueServiceDeployment</code> doesn't exist. You can use <code>ListServiceDeployments</code> to retrieve the service deployment ARNs.</p>
  *
  * @throws {@link UnsupportedFeatureException} (client fault)
  *  <p>The specified task isn't supported in this Region.</p>
@@ -84,7 +84,7 @@ declare const ContinueServiceDeploymentCommand_base: {
  * // This example continues a service deployment that is paused at a lifecycle hook, using the CONTINUE action to proceed to the next deployment stage.
  * const input = {
  *   action: "CONTINUE",
- *   hookId: "ABCDEFGHIJKLMNOPQRSTUVWXYZ234567",
+ *   hookId: "ecs-pause-Xk7rT2mP9sLwQn4vB8fYd3hJ6gA1cE5iO0uR_ZpWq",
  *   serviceDeploymentArn: "arn:aws:ecs:us-east-1:123456789012:service-deployment/MyCluster/MyService/r9i43YFjvgF_xlg7m2eJ1r"
  * };
  * const command = new ContinueServiceDeploymentCommand(input);
@@ -101,7 +101,7 @@ declare const ContinueServiceDeploymentCommand_base: {
  * // This example rolls back a service deployment that is paused at a lifecycle hook, using the ROLLBACK action to revert to the previous service revision.
  * const input = {
  *   action: "ROLLBACK",
- *   hookId: "ABCDEFGHIJKLMNOPQRSTUVWXYZ234567",
+ *   hookId: "ecs-pause-Xk7rT2mP9sLwQn4vB8fYd3hJ6gA1cE5iO0uR_ZpWq",
  *   serviceDeploymentArn: "arn:aws:ecs:us-east-1:123456789012:service-deployment/MyCluster/MyService/r9i43YFjvgF_xlg7m2eJ1r"
  * };
  * const command = new ContinueServiceDeploymentCommand(input);

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

@@ -39,7 +39,7 @@ declare const CreateExpressGatewayServiceCommand_base: {
  * const config = {}; // type is ECSClientConfig
  * const client = new ECSClient(config);
  * const input = { // CreateExpressGatewayServiceRequest
- *   executionRoleArn: "STRING_VALUE", // required
+ *   executionRoleArn: "STRING_VALUE",
  *   infrastructureRoleArn: "STRING_VALUE", // required
  *   serviceName: "STRING_VALUE",
  *   cluster: "STRING_VALUE",
@@ -93,6 +93,7 @@ declare const CreateExpressGatewayServiceCommand_base: {
  *       value: "STRING_VALUE",
  *     },
  *   ],
+ *   taskDefinitionArn: "STRING_VALUE",
  * };
  * const command = new CreateExpressGatewayServiceCommand(input);
  * const response = await client.send(command);
@@ -112,6 +113,7 @@ declare const CreateExpressGatewayServiceCommand_base: {
  * //         serviceRevisionArn: "STRING_VALUE",
  * //         executionRoleArn: "STRING_VALUE",
  * //         taskRoleArn: "STRING_VALUE",
+ * //         taskDefinitionArn: "STRING_VALUE",
  * //         cpu: "STRING_VALUE",
  * //         memory: "STRING_VALUE",
  * //         networkConfiguration: { // ExpressGatewayServiceNetworkConfiguration

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

@@ -59,6 +59,7 @@ declare const DeleteExpressGatewayServiceCommand_base: {
  * //         serviceRevisionArn: "STRING_VALUE",
  * //         executionRoleArn: "STRING_VALUE",
  * //         taskRoleArn: "STRING_VALUE",
+ * //         taskDefinitionArn: "STRING_VALUE",
  * //         cpu: "STRING_VALUE",
  * //         memory: "STRING_VALUE",
  * //         networkConfiguration: { // ExpressGatewayServiceNetworkConfiguration

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

@@ -62,6 +62,7 @@ declare const DescribeExpressGatewayServiceCommand_base: {
  * //         serviceRevisionArn: "STRING_VALUE",
  * //         executionRoleArn: "STRING_VALUE",
  * //         taskRoleArn: "STRING_VALUE",
+ * //         taskDefinitionArn: "STRING_VALUE",
  * //         cpu: "STRING_VALUE",
  * //         memory: "STRING_VALUE",
  * //         networkConfiguration: { // ExpressGatewayServiceNetworkConfiguration

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

@@ -270,7 +270,7 @@ declare const DescribeServiceDeploymentsCommand_base: {
  *       lifecycleHookDetails: [
  *         {
  *           expiresAt: "2026-05-06T17:00:00.000Z",
- *           hookId: "ABCDEFGHIJKLMNOPQRSTUVWXYZ234567",
+ *           hookId: "ecs-pause-Xk7rT2mP9sLwQn4vB8fYd3hJ6gA1cE5iO0uR_ZpWq",
  *           status: "AWAITING_ACTION",
  *           targetType: "PAUSE",
  *           timeoutAction: "ROLLBACK"

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

@@ -72,7 +72,7 @@ declare const StopServiceDeploymentCommand_base: {
  *  <p>These errors are usually caused by a server issue.</p>
  *
  * @throws {@link ServiceDeploymentNotFoundException} (client fault)
- *  <p>The service deploy ARN that you specified in the <code>StopServiceDeployment</code> doesn't exist. You can use <code>ListServiceDeployments</code> to retrieve the service deployment ARNs.</p>
+ *  <p>The service deploy ARN that you specified in the <code>ContinueServiceDeployment</code> doesn't exist. You can use <code>ListServiceDeployments</code> to retrieve the service deployment ARNs.</p>
  *
  * @throws {@link UnsupportedFeatureException} (client fault)
  *  <p>The specified task isn't supported in this Region.</p>

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

@@ -85,6 +85,7 @@ declare const UpdateExpressGatewayServiceCommand_base: {
  *     autoScalingMetric: "AVERAGE_CPU" || "AVERAGE_MEMORY" || "REQUEST_COUNT_PER_TARGET",
  *     autoScalingTargetValue: Number("int"),
  *   },
+ *   taskDefinitionArn: "STRING_VALUE",
  * };
  * const command = new UpdateExpressGatewayServiceCommand(input);
  * const response = await client.send(command);
@@ -101,6 +102,7 @@ declare const UpdateExpressGatewayServiceCommand_base: {
  * //       serviceRevisionArn: "STRING_VALUE",
  * //       executionRoleArn: "STRING_VALUE",
  * //       taskRoleArn: "STRING_VALUE",
+ * //       taskDefinitionArn: "STRING_VALUE",
  * //       cpu: "STRING_VALUE",
  * //       memory: "STRING_VALUE",
  * //       networkConfiguration: { // ExpressGatewayServiceNetworkConfiguration

package/dist-types/models/errors.d.ts

@@ -241,7 +241,7 @@ export declare class NoUpdateAvailableException extends __BaseException {
     constructor(opts: __ExceptionOptionType<NoUpdateAvailableException, __BaseException>);
 }
 /**
- * <p>The service deploy ARN that you specified in the <code>StopServiceDeployment</code> doesn't exist. You can use <code>ListServiceDeployments</code> to retrieve the service deployment ARNs.</p>
+ * <p>The service deploy ARN that you specified in the <code>ContinueServiceDeployment</code> doesn't exist. You can use <code>ListServiceDeployments</code> to retrieve the service deployment ARNs.</p>
  * @public
  */
 export declare class ServiceDeploymentNotFoundException extends __BaseException {

package/dist-types/models/models_0.d.ts

@@ -3025,7 +3025,7 @@ export interface ListDaemonDeploymentsResponse {
  */
 export interface ListDaemonsRequest {
     /**
-     * <p>The Amazon Resource Name (ARN) of the cluster to filter daemons by. If not specified, daemons from all clusters are returned.</p>
+     * <p>The Amazon Resource Name (ARN) of the cluster to filter daemons by. If you do not specify a cluster, the default cluster is assumed.</p>
      * @public
      */
     clusterArn?: string | undefined;
@@ -3822,12 +3822,12 @@ export interface DaemonTaskDefinition {
      */
     registeredBy?: string | undefined;
     /**
-     * <p>The process namespace mode for the daemon. A value of <code>shared</code> means the daemon shares the PID namespace with co-located tasks, giving it visibility into application processes. A value of <code>none</code> means the daemon has its own isolated PID namespace.</p>
+     * <p>The PID namespace mode for the daemon. The valid values are <code>none</code> and <code>shared</code>. The default is <code>none</code>.</p> <p>If <code>none</code> is specified or no value is provided, the daemon runs with its own PID namespace, isolated from other tasks. If <code>shared</code> is specified, the daemon joins the host PID namespace, making it accessible to non-daemon tasks that use <code>pidMode: "host"</code> or other daemons that use <code>pidMode: "shared"</code>.</p>
      * @public
      */
     pidMode?: DaemonPidMode | undefined;
     /**
-     * <p>The IPC namespace mode for the daemon. A value of <code>shared</code> means the daemon shares the IPC namespace with co-located tasks, allowing communication through POSIX shared memory, semaphores, and message queues. A value of <code>none</code> means the daemon has its own isolated IPC namespace.</p>
+     * <p>The IPC namespace mode for the daemon. The valid values are <code>none</code> and <code>shared</code>. The default is <code>none</code>.</p> <p>If <code>none</code> is specified or no value is provided, the daemon runs with its own IPC namespace, isolated from other tasks. If <code>shared</code> is specified, the daemon joins the host IPC namespace, making it accessible to non-daemon tasks that use <code>ipcMode: "host"</code> or other daemons that use <code>ipcMode: "shared"</code>.</p>
      * @public
      */
     ipcMode?: DaemonIpcMode | undefined;
@@ -3973,12 +3973,12 @@ export interface RegisterDaemonTaskDefinitionRequest {
      */
     tags?: Tag[] | undefined;
     /**
-     * <p>The process namespace mode for the daemon. When set to <code>shared</code>, the daemon shares the PID namespace with co-located tasks on the same container instance, giving the daemon visibility into application processes. When set to <code>none</code>, the daemon gets its own isolated PID namespace. The default is <code>none</code>.</p>
+     * <p>The PID namespace mode for the daemon. The valid values are <code>none</code> and <code>shared</code>. The default is <code>none</code>.</p> <p>If <code>none</code> is specified or no value is provided, the daemon runs with its own PID namespace, isolated from other tasks. If <code>shared</code> is specified, the daemon joins the host PID namespace, making it accessible to non-daemon tasks that use <code>pidMode: "host"</code> or other daemons that use <code>pidMode: "shared"</code>.</p>
      * @public
      */
     pidMode?: DaemonPidMode | undefined;
     /**
-     * <p>The IPC namespace mode for the daemon. When set to <code>shared</code>, the daemon shares the IPC namespace with co-located tasks on the same container instance, allowing communication through POSIX shared memory, semaphores, and message queues. When set to <code>none</code>, the daemon gets its own isolated IPC namespace. The default is <code>none</code>.</p>
+     * <p>The IPC namespace mode for the daemon. The valid values are <code>none</code> and <code>shared</code>. The default is <code>none</code>.</p> <p>If <code>none</code> is specified or no value is provided, the daemon runs with its own IPC namespace, isolated from other tasks. If <code>shared</code> is specified, the daemon joins the host IPC namespace, making it accessible to non-daemon tasks that use <code>ipcMode: "host"</code> or other daemons that use <code>ipcMode: "shared"</code>.</p>
      * @public
      */
     ipcMode?: DaemonIpcMode | undefined;
@@ -5191,18 +5191,18 @@ export interface DeploymentCircuitBreaker {
  */
 export interface DeploymentLifecycleHookTimeoutConfiguration {
     /**
-     * <p>The number of minutes Amazon ECS waits for the lifecycle hook to complete before taking the timeout action.</p>
+     * <p>The number of minutes Amazon ECS waits for the lifecycle hook to complete before taking the timeout action.</p> <p>Default: 1440 (24 hours)</p>
      * @public
      */
     timeoutInMinutes?: number | undefined;
     /**
-     * <p>The action Amazon ECS takes when the lifecycle hook times out. Valid values are:</p> <ul> <li> <p> <code>CONTINUE</code> - Proceeds the deployment to the next lifecycle stage.</p> </li> <li> <p> <code>ROLLBACK</code> - Rolls back the deployment to the previous service revision.</p> </li> </ul>
+     * <p>The action Amazon ECS takes when the lifecycle hook times out. Valid values are:</p> <ul> <li> <p> <code>CONTINUE</code> - Proceeds the deployment to the next lifecycle stage.</p> </li> <li> <p> <code>ROLLBACK</code> - Rolls back the deployment to the previous service revision.</p> </li> </ul> <p>Default: <code>ROLLBACK</code> </p>
      * @public
      */
     action?: DeploymentLifecycleHookAction | undefined;
 }
 /**
- * <p>A deployment lifecycle hook runs custom logic at specific stages of the deployment process. Currently, you can use Lambda functions as hook targets.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html">Lifecycle hooks for Amazon ECS service deployments</a> in the <i> Amazon Elastic Container Service Developer Guide</i>.</p>
+ * <p>A deployment lifecycle hook runs custom logic or pauses the deployment at specific stages of the deployment process. You can use Lambda functions or pause hooks as hook targets.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html">Lifecycle hooks for Amazon ECS service deployments</a> in the <i> Amazon Elastic Container Service Developer Guide</i>.</p>
  * @public
  */
 export interface DeploymentLifecycleHook {
@@ -5212,7 +5212,7 @@ export interface DeploymentLifecycleHook {
      */
     targetType?: DeploymentLifecycleHookTargetType | undefined;
     /**
-     * <p>The Amazon Resource Name (ARN) of the hook target. Currently, only Lambda function ARNs are supported.</p> <p>You must provide this parameter when configuring a deployment lifecycle hook.</p>
+     * <p>The Amazon Resource Name (ARN) of the hook target. For <code>AWS_LAMBDA</code> hooks, this is the Lambda function ARN. This field is not applicable for <code>PAUSE</code> hooks.</p> <p>You must provide this parameter when configuring an <code>AWS_LAMBDA</code> lifecycle hook.</p>
      * @public
      */
     hookTargetArn?: string | undefined;
@@ -5222,12 +5222,12 @@ export interface DeploymentLifecycleHook {
      */
     roleArn?: string | undefined;
     /**
-     * <p>The lifecycle stages at which to run the hook. Choose from these valid values:</p> <ul> <li> <p>RECONCILE_SERVICE</p> <p>The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>PRE_SCALE_UP</p> <p>The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>POST_SCALE_UP</p> <p>The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>POST_TEST_TRAFFIC_SHIFT</p> <p>The test traffic shift is complete. The green service revision handles 100% of the test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>PRODUCTION_TRAFFIC_SHIFT</p> <p>Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>POST_PRODUCTION_TRAFFIC_SHIFT</p> <p>The production traffic shift is complete.</p> <p>You can use a lifecycle hook for this stage.</p> </li> </ul> <p>You must provide this parameter when configuring a deployment lifecycle hook.</p>
+     * <p>The lifecycle stages at which to run the hook. Choose from these valid values:</p> <ul> <li> <p>RECONCILE_SERVICE</p> <p>The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>PRE_SCALE_UP</p> <p>The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>POST_SCALE_UP</p> <p>The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>POST_TEST_TRAFFIC_SHIFT</p> <p>The test traffic shift is complete. The green service revision handles 100% of the test traffic.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>PRE_PRODUCTION_TRAFFIC_SHIFT</p> <p>Occurs before production traffic shift. For linear and canary deployments, this stage is invoked before every traffic shift step.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>PRODUCTION_TRAFFIC_SHIFT</p> <p>Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic. For linear and canary deployments, this stage is invoked at every traffic shift step.</p> <p>You can use a lifecycle hook for this stage.</p> </li> <li> <p>POST_PRODUCTION_TRAFFIC_SHIFT</p> <p>The production traffic shift is complete.</p> <p>You can use a lifecycle hook for this stage.</p> </li> </ul> <note> <p> <code>PAUSE</code> hooks cannot be configured at <code>TEST_TRAFFIC_SHIFT</code> or <code>PRODUCTION_TRAFFIC_SHIFT</code> stages. These stages are only valid for <code>AWS_LAMBDA</code> hooks.</p> </note> <p>You must provide this parameter when configuring a deployment lifecycle hook.</p>
      * @public
      */
     lifecycleStages?: DeploymentLifecycleHookStage[] | undefined;
     /**
-     * <p>Use this field to specify custom parameters that Amazon ECS will pass to your hook target invocations (such as a Lambda function).</p>
+     * <p>Use this field to specify custom parameters that Amazon ECS passes to your Lambda function on each invocation. This field is not used for <code>PAUSE</code> hooks.</p>
      * @public
      */
     hookDetails?: __DocumentType | undefined;
@@ -5289,7 +5289,7 @@ export interface DeploymentConfiguration {
      */
     bakeTimeInMinutes?: number | undefined;
     /**
-     * <p>An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle.</p>
+     * <p>An array of deployment lifecycle hook objects to run custom logic or pause the deployment at specific stages of the deployment lifecycle.</p>
      * @public
      */
     lifecycleHooks?: DeploymentLifecycleHook[] | undefined;
@@ -5325,7 +5325,7 @@ export interface DeploymentLifecycleHookDetail {
      */
     targetArn?: string | undefined;
     /**
-     * <p>The status of the lifecycle hook. Valid values depend on the hook type:</p> <ul> <li> <p>For <code>AWS_LAMBDA</code> hooks: <code>IN_PROGRESS</code>, <code>SUCCEEDED</code>, <code>FAILED</code>, and <code>TIMED_OUT</code>.</p> </li> <li> <p>For <code>PAUSE</code> hooks: <code>AWAITING_ACTION</code>, <code>SUCCEEDED</code>, <code>FAILED</code>, and <code>TIMED_OUT</code>.</p> </li> </ul>
+     * <p>The status of the lifecycle hook. Valid values include <code>AWAITING_ACTION</code>, <code>IN_PROGRESS</code>, <code>SUCCEEDED</code>, <code>FAILED</code>, and <code>TIMED_OUT</code>.</p>
      * @public
      */
     status?: DeploymentLifecycleHookStatus | undefined;
@@ -5463,7 +5463,7 @@ export interface ServiceDeployment {
      */
     statusReason?: string | undefined;
     /**
-     * <p>The current lifecycle stage of the deployment. Possible values include:</p> <ul> <li> <p>RECONCILE_SERVICE</p> <p>The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state.</p> </li> <li> <p>PRE_SCALE_UP</p> <p>The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> </li> <li> <p>SCALE_UP</p> <p>The stage when the green service revision scales up to 100% and launches new tasks. The green service revision is not serving any traffic at this point.</p> </li> <li> <p>POST_SCALE_UP</p> <p>The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> </li> <li> <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic.</p> </li> <li> <p>POST_TEST_TRAFFIC_SHIFT</p> <p>The test traffic shift is complete. The green service revision handles 100% of the test traffic.</p> </li> <li> <p>PRODUCTION_TRAFFIC_SHIFT</p> <p>Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic.</p> </li> <li> <p>POST_PRODUCTION_TRAFFIC_SHIFT</p> <p>The production traffic shift is complete.</p> </li> <li> <p>BAKE_TIME</p> <p>The stage when both blue and green service revisions are running simultaneously after the production traffic has shifted.</p> </li> <li> <p>CLEAN_UP</p> <p>The stage when the blue service revision has completely scaled down to 0 running tasks. The green service revision is now the production service revision after this stage.</p> </li> </ul>
+     * <p>The current lifecycle stage of the deployment. Possible values include:</p> <ul> <li> <p>RECONCILE_SERVICE</p> <p>The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state.</p> </li> <li> <p>PRE_SCALE_UP</p> <p>The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> </li> <li> <p>SCALE_UP</p> <p>The stage when the green service revision scales up to 100% and launches new tasks. The green service revision is not serving any traffic at this point.</p> </li> <li> <p>POST_SCALE_UP</p> <p>The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.</p> </li> <li> <p>TEST_TRAFFIC_SHIFT</p> <p>The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic.</p> </li> <li> <p>POST_TEST_TRAFFIC_SHIFT</p> <p>The test traffic shift is complete. The green service revision handles 100% of the test traffic.</p> </li> <li> <p>PRE_PRODUCTION_TRAFFIC_SHIFT</p> <p>Occurs before production traffic shift. For linear and canary deployments, this stage is invoked before every traffic shift step.</p> </li> <li> <p>PRODUCTION_TRAFFIC_SHIFT</p> <p>Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic. For linear and canary deployments, this stage is invoked at every traffic shift step.</p> </li> <li> <p>POST_PRODUCTION_TRAFFIC_SHIFT</p> <p>The production traffic shift is complete.</p> </li> <li> <p>BAKE_TIME</p> <p>The stage when both blue and green service revisions are running simultaneously after the production traffic has shifted.</p> </li> <li> <p>CLEAN_UP</p> <p>The stage when the blue service revision has completely scaled down to 0 running tasks. The green service revision is now the production service revision after this stage.</p> </li> </ul>
      * @public
      */
     lifecycleStage?: ServiceDeploymentLifecycleStage | undefined;
@@ -5626,7 +5626,7 @@ export interface CreateExpressGatewayServiceRequest {
      * <p>The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. This role is required for Amazon ECS to pull container images from Amazon ECR, send container logs to Amazon CloudWatch Logs, and retrieve sensitive data from Amazon Web Services Systems Manager Parameter Store or Amazon Web Services Secrets Manager.</p> <p>The execution role must include the <code>AmazonECSTaskExecutionRolePolicy</code> managed policy or equivalent permissions. For Express services, this role is used during task startup and runtime for container management operations.</p>
      * @public
      */
-    executionRoleArn: string | undefined;
+    executionRoleArn?: string | undefined;
     /**
      * <p>The Amazon Resource Name (ARN) of the infrastructure role that grants Amazon ECS permission to create and manage Amazon Web Services resources on your behalf for the Express service. This role is used to provision and manage Application Load Balancers, target groups, security groups, auto-scaling policies, and other Amazon Web Services infrastructure components.</p> <p>The infrastructure role must include permissions for Elastic Load Balancing, Application Auto Scaling, Amazon EC2 (for security groups), and other services required for managed infrastructure. This role is only used during Express service creation, updates, and deletion operations.</p>
      * @public
@@ -5651,7 +5651,7 @@ export interface CreateExpressGatewayServiceRequest {
      * <p>The primary container configuration for the Express service. This defines the main application container that will receive traffic from the Application Load Balancer.</p> <p>The primary container must specify at minimum a container image. You can also configure the container port (defaults to 80), logging configuration, environment variables, secrets, and startup commands. The container image can be from Amazon ECR, Docker Hub, or any other container registry accessible to your execution role.</p>
      * @public
      */
-    primaryContainer: ExpressGatewayContainer | undefined;
+    primaryContainer?: ExpressGatewayContainer | undefined;
     /**
      * <p>The Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. This role allows your application code to access other Amazon Web Services services securely.</p> <p>The task role is different from the execution role. While the execution role is used by the Amazon ECS agent to set up the task, the task role is used by your application code running inside the container to make Amazon Web Services API calls. If your application doesn't need to access Amazon Web Services services, you can omit this parameter.</p>
      * @public
@@ -5682,6 +5682,11 @@ export interface CreateExpressGatewayServiceRequest {
      * @public
      */
     tags?: Tag[] | undefined;
+    /**
+     * <p>The Amazon Resource Name (ARN) of a task definition to use to create the Express Gateway service. This allows you to manage your own task definition, giving you more control over the service configuration such as adding sidecar containers.</p> <p>The task definition must have a container named <code>Main</code> with a single TCP port mapping that includes a container port and port name. The task definition must also have <code>FARGATE</code> compatibility.</p> <p>If you provide a task definition ARN, you cannot also specify <code>primaryContainer</code>, <code>executionRoleArn</code>, <code>taskRoleArn</code>, <code>cpu</code>, or <code>memory</code>.</p>
+     * @public
+     */
+    taskDefinitionArn?: string | undefined;
 }
 /**
  * <p>The entry point into an Express service.</p>
@@ -5719,6 +5724,11 @@ export interface ExpressGatewayServiceConfiguration {
      * @public
      */
     taskRoleArn?: string | undefined;
+    /**
+     * <p>The ARN of the task definition used by this service revision. This is present for all Express services and reflects the task definition in use, whether managed by Amazon ECS or provided by the customer.</p>
+     * @public
+     */
+    taskDefinitionArn?: string | undefined;
     /**
      * <p>The CPU allocation for tasks in this service revision.</p>
      * @public
@@ -7284,6 +7294,11 @@ export interface UpdateExpressGatewayServiceRequest {
      * @public
      */
     scalingTarget?: ExpressGatewayScalingTarget | undefined;
+    /**
+     * <p>The Amazon Resource Name (ARN) of a task definition to use to update the Express Gateway service. This allows you to manage your own task definition, giving you more control over the service configuration such as adding sidecar containers.</p> <p>The task definition must have a container named <code>Main</code> with a single TCP port mapping that includes a container port and port name. The task definition must also have <code>FARGATE</code> compatibility.</p> <p>If you provide a task definition ARN, you cannot also specify <code>primaryContainer</code>, <code>taskRoleArn</code>, <code>cpu</code>, or <code>memory</code>.</p>
+     * @public
+     */
+    taskDefinitionArn?: string | undefined;
 }
 /**
  * <p>An object that describes an Express service to be updated.</p>

package/dist-types/ts3.4/models/models_0.d.ts

@@ -1427,18 +1427,19 @@ export interface ExpressGatewayScalingTarget {
   autoScalingTargetValue?: number | undefined;
 }
 export interface CreateExpressGatewayServiceRequest {
-  executionRoleArn: string | undefined;
+  executionRoleArn?: string | undefined;
   infrastructureRoleArn: string | undefined;
   serviceName?: string | undefined;
   cluster?: string | undefined;
   healthCheckPath?: string | undefined;
-  primaryContainer: ExpressGatewayContainer | undefined;
+  primaryContainer?: ExpressGatewayContainer | undefined;
   taskRoleArn?: string | undefined;
   networkConfiguration?: ExpressGatewayServiceNetworkConfiguration | undefined;
   cpu?: string | undefined;
   memory?: string | undefined;
   scalingTarget?: ExpressGatewayScalingTarget | undefined;
   tags?: Tag[] | undefined;
+  taskDefinitionArn?: string | undefined;
 }
 export interface IngressPathSummary {
   accessType: AccessType | undefined;
@@ -1448,6 +1449,7 @@ export interface ExpressGatewayServiceConfiguration {
   serviceRevisionArn?: string | undefined;
   executionRoleArn?: string | undefined;
   taskRoleArn?: string | undefined;
+  taskDefinitionArn?: string | undefined;
   cpu?: string | undefined;
   memory?: string | undefined;
   networkConfiguration?: ExpressGatewayServiceNetworkConfiguration | undefined;
@@ -1803,6 +1805,7 @@ export interface UpdateExpressGatewayServiceRequest {
   cpu?: string | undefined;
   memory?: string | undefined;
   scalingTarget?: ExpressGatewayScalingTarget | undefined;
+  taskDefinitionArn?: string | undefined;
 }
 export interface UpdatedExpressGatewayService {
   serviceArn?: string | undefined;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-ecs",
   "description": "AWS SDK for JavaScript Ecs Client for Node.js, Browser and React Native",
-  "version": "3.1069.0",
+  "version": "3.1071.0",
   "scripts": {
     "build": "concurrently 'yarn:build:types' 'yarn:build:es' && yarn build:cjs",
     "build:cjs": "node ../../scripts/compilation/inline",
@@ -23,8 +23,8 @@
   "dependencies": {
     "@aws-crypto/sha256-browser": "5.2.0",
     "@aws-crypto/sha256-js": "5.2.0",
-    "@aws-sdk/core": "^3.974.21",
-    "@aws-sdk/credential-provider-node": "^3.972.56",
+    "@aws-sdk/core": "^3.974.22",
+    "@aws-sdk/credential-provider-node": "^3.972.57",
     "@aws-sdk/types": "^3.973.13",
     "@smithy/core": "^3.24.6",
     "@smithy/fetch-http-handler": "^5.4.6",