@aws-sdk/client-ecs 3.1161.0 → 3.1162.0

package/dist-cjs/index.js

@@ -1,4 +1,4 @@
-const { awsEndpointFunctions, emitWarningIfUnsupportedVersion: emitWarningIfUnsupportedVersion$1, createDefaultUserAgentProvider, NODE_APP_ID_CONFIG_OPTIONS, getAwsRegionExtensionConfiguration, resolveAwsRegionExtensionConfiguration, resolveUserAgentConfig, resolveHostHeaderConfig, getUserAgentPlugin, getHostHeaderPlugin, getLoggerPlugin, getRecursionDetectionPlugin } = require("@aws-sdk/core/client");
+const { awsEndpointFunctions, emitWarningIfUnsupportedVersion: emitWarningIfUnsupportedVersion$1, createDefaultUserAgentProvider, getDefaultSocketTimeout, NODE_APP_ID_CONFIG_OPTIONS, getAwsRegionExtensionConfiguration, resolveAwsRegionExtensionConfiguration, resolveUserAgentConfig, resolveHostHeaderConfig, getUserAgentPlugin, getHostHeaderPlugin, getLoggerPlugin, getRecursionDetectionPlugin } = require("@aws-sdk/core/client");
 const { getHttpAuthSchemeEndpointRuleSetPlugin, DefaultIdentityProviderConfig, getHttpSigningPlugin, createPaginator } = require("@smithy/core");
 const { normalizeProvider, getSmithyContext, ServiceException, NoOpLogger, emitWarningIfUnsupportedVersion, loadConfigsForDefaultMode, getDefaultExtensionConfiguration, resolveDefaultRuntimeConfig, Client, makeBuilder, createWaiter, checkExceptions, WaiterState, createAggregatedClient } = require("@smithy/core/client");
 const { Command: $Command } = require("@smithy/core/client");
@@ -69,7 +69,7 @@ const commonParams = {
     UseDualStack: { type: "builtInParams", name: "useDualstackEndpoint" },
 };
 
-var version = "3.1160.0";
+var version = "3.1161.0";
 var packageInfo = {
 	version: version};
 
@@ -907,6 +907,7 @@ const _LDRi = "ListDaemonsResponse";
 const _LDTD = "ListDaemonTaskDefinitions";
 const _LDTDR = "ListDaemonTaskDefinitionsRequest";
 const _LDTDRi = "ListDaemonTaskDefinitionsResponse";
+const _LDVC = "LogDriverVolumeConfiguration";
 const _LEE = "LimitExceededException";
 const _LG = "ListGateways";
 const _LGCA = "ListGatewayClusterAssociations";
@@ -1512,6 +1513,7 @@ const _lBo = "loadBalancer";
 const _lC = "logConfiguration";
 const _lCi = "linearConfiguration";
 const _lD = "logDriver";
+const _lDVC = "logDriverVolumeConfiguration";
 const _lG = "logGroups";
 const _lGN = "logGroupName";
 const _lGo = "logGroup";
@@ -2374,8 +2376,8 @@ var DaemonTaskDefinitionSummary$ = [3, n0, _DTDS,
 ];
 var DaemonVolume$ = [3, n0, _DV,
     0,
-    [_n, _ho],
-    [0, () => HostVolumeProperties$]
+    [_n, _ho, _lDVC],
+    [0, () => HostVolumeProperties$, () => LogDriverVolumeConfiguration$]
 ];
 var DeleteAccountSettingRequest$ = [3, n0, _DASR,
     0,
@@ -3257,6 +3259,11 @@ var LogConfiguration$ = [3, n0, _LCo,
     [_lD, _o, _sO],
     [0, 128 | 0, () => SecretList], 1
 ];
+var LogDriverVolumeConfiguration$ = [3, n0, _LDVC,
+    0,
+    [_dr],
+    [0], 1
+];
 var ManagedAgent$ = [3, n0, _MA,
     0,
     [_lSA, _n, _r, _lS],
@@ -4752,6 +4759,7 @@ const getRuntimeConfig = (config) => {
         authSchemePreference: config?.authSchemePreference ?? loadConfig(NODE_AUTH_SCHEME_PREFERENCE_OPTIONS, loaderConfig),
         bodyLengthChecker: config?.bodyLengthChecker ?? calculateBodyLength,
         credentialDefaultProvider: config?.credentialDefaultProvider ?? defaultProvider,
+        defaultSocketTimeout: getDefaultSocketTimeout(config?.requestHandler, 900_000),
         defaultUserAgentProvider: config?.defaultUserAgentProvider ?? createDefaultUserAgentProvider({ serviceId: clientSharedValues.serviceId, clientVersion: packageInfo.version }),
         maxAttempts: config?.maxAttempts ?? loadConfig(NODE_MAX_ATTEMPT_CONFIG_OPTIONS, config),
         region: config?.region ?? loadConfig(NODE_REGION_CONFIG_OPTIONS, { ...NODE_REGION_CONFIG_FILE_OPTIONS, ...loaderConfig }),
@@ -6866,6 +6874,7 @@ exports.LocalStorage = LocalStorage;
 exports.LocalStorageType = LocalStorageType;
 exports.LogConfiguration$ = LogConfiguration$;
 exports.LogDriver = LogDriver;
+exports.LogDriverVolumeConfiguration$ = LogDriverVolumeConfiguration$;
 exports.ManagedAgent$ = ManagedAgent$;
 exports.ManagedAgentName = ManagedAgentName;
 exports.ManagedAgentStateChange$ = ManagedAgentStateChange$;

package/dist-es/runtimeConfig.js

@@ -1,5 +1,5 @@
 import packageInfo from "../package.json";
-import { createDefaultUserAgentProvider, emitWarningIfUnsupportedVersion as awsCheckVersion, NODE_APP_ID_CONFIG_OPTIONS, } from "@aws-sdk/core/client";
+import { createDefaultUserAgentProvider, emitWarningIfUnsupportedVersion as awsCheckVersion, getDefaultSocketTimeout, NODE_APP_ID_CONFIG_OPTIONS, } from "@aws-sdk/core/client";
 import { NODE_AUTH_SCHEME_PREFERENCE_OPTIONS } from "@aws-sdk/core/httpAuthSchemes";
 import { defaultProvider as credentialDefaultProvider } from "@aws-sdk/credential-provider-node";
 import { emitWarningIfUnsupportedVersion, loadConfigsForDefaultMode } from "@smithy/core/client";
@@ -26,6 +26,7 @@ export const getRuntimeConfig = (config) => {
         authSchemePreference: config?.authSchemePreference ?? loadNodeConfig(NODE_AUTH_SCHEME_PREFERENCE_OPTIONS, loaderConfig),
         bodyLengthChecker: config?.bodyLengthChecker ?? calculateBodyLength,
         credentialDefaultProvider: config?.credentialDefaultProvider ?? credentialDefaultProvider,
+        defaultSocketTimeout: getDefaultSocketTimeout(config?.requestHandler, 900_000),
         defaultUserAgentProvider: config?.defaultUserAgentProvider ?? createDefaultUserAgentProvider({ serviceId: clientSharedValues.serviceId, clientVersion: packageInfo.version }),
         maxAttempts: config?.maxAttempts ?? loadNodeConfig(NODE_MAX_ATTEMPT_CONFIG_OPTIONS, config),
         region: config?.region ?? loadNodeConfig(NODE_REGION_CONFIG_OPTIONS, { ...NODE_REGION_CONFIG_FILE_OPTIONS, ...loaderConfig }),

package/dist-es/schemas/schemas_0.js

@@ -360,6 +360,7 @@ const _LDRi = "ListDaemonsResponse";
 const _LDTD = "ListDaemonTaskDefinitions";
 const _LDTDR = "ListDaemonTaskDefinitionsRequest";
 const _LDTDRi = "ListDaemonTaskDefinitionsResponse";
+const _LDVC = "LogDriverVolumeConfiguration";
 const _LEE = "LimitExceededException";
 const _LG = "ListGateways";
 const _LGCA = "ListGatewayClusterAssociations";
@@ -965,6 +966,7 @@ const _lBo = "loadBalancer";
 const _lC = "logConfiguration";
 const _lCi = "linearConfiguration";
 const _lD = "logDriver";
+const _lDVC = "logDriverVolumeConfiguration";
 const _lG = "logGroups";
 const _lGN = "logGroupName";
 const _lGo = "logGroup";
@@ -1830,8 +1832,8 @@ export var DaemonTaskDefinitionSummary$ = [3, n0, _DTDS,
 ];
 export var DaemonVolume$ = [3, n0, _DV,
     0,
-    [_n, _ho],
-    [0, () => HostVolumeProperties$]
+    [_n, _ho, _lDVC],
+    [0, () => HostVolumeProperties$, () => LogDriverVolumeConfiguration$]
 ];
 export var DeleteAccountSettingRequest$ = [3, n0, _DASR,
     0,
@@ -2713,6 +2715,11 @@ export var LogConfiguration$ = [3, n0, _LCo,
     [_lD, _o, _sO],
     [0, 128 | 0, () => SecretList], 1
 ];
+export var LogDriverVolumeConfiguration$ = [3, n0, _LDVC,
+    0,
+    [_dr],
+    [0], 1
+];
 export var ManagedAgent$ = [3, n0, _MA,
     0,
     [_lSA, _n, _r, _lS],

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

@@ -179,6 +179,9 @@ declare const DescribeDaemonTaskDefinitionCommand_base: {
  * //         host: { // HostVolumeProperties
  * //           sourcePath: "STRING_VALUE",
  * //         },
+ * //         logDriverVolumeConfiguration: { // LogDriverVolumeConfiguration
+ * //           driver: "json-file" || "syslog" || "journald" || "gelf" || "fluentd" || "awslogs" || "splunk" || "awsfirelens", // required
+ * //         },
  * //       },
  * //     ],
  * //     cpu: "STRING_VALUE",

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

@@ -173,6 +173,9 @@ declare const RegisterDaemonTaskDefinitionCommand_base: {
  *       host: { // HostVolumeProperties
  *         sourcePath: "STRING_VALUE",
  *       },
+ *       logDriverVolumeConfiguration: { // LogDriverVolumeConfiguration
+ *         driver: "json-file" || "syslog" || "journald" || "gelf" || "fluentd" || "awslogs" || "splunk" || "awsfirelens", // required
+ *       },
  *     },
  *   ],
  *   tags: [ // Tags

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

@@ -3534,12 +3534,12 @@ export interface Secret {
     valueFrom: string | undefined;
 }
 /**
- * <p>The log configuration for the container. This parameter maps to <code>LogConfig</code> in the docker container create command and the <code>--log-driver</code> option to docker run.</p> <p>By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition.</p> <p>Understand the following when specifying a log configuration for your containers.</p> <ul> <li> <p>Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent.</p> <p>For tasks on Fargate, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks hosted on Amazon EC2 instances, the supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>, <code>json-file</code>, <code>journald</code>,<code>syslog</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> </li> <li> <p>This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.</p> </li> <li> <p>For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the <code>ECS_AVAILABLE_LOGGING_DRIVERS</code> environment variable before containers placed on that instance can use these log configuration options. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html">Amazon ECS container agent configuration</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </li> <li> <p>For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.</p> </li> </ul>
+ * <p>The log configuration for the container. This parameter maps to <code>LogConfig</code> in the docker container create command and the <code>--log-driver</code> option to docker run.</p> <p>By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition.</p> <p>Understand the following when specifying a log configuration for your containers.</p> <ul> <li> <p>Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent.</p> <p>For tasks on Fargate, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks hosted on Amazon EC2 instances, the supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>, <code>json-file</code>, <code>journald</code>,<code>syslog</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks on Amazon ECS Managed Instances, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, <code>awsfirelens</code>, and <code>json-file</code>.</p> </li> <li> <p>This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.</p> </li> <li> <p>For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the <code>ECS_AVAILABLE_LOGGING_DRIVERS</code> environment variable before containers placed on that instance can use these log configuration options. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html">Amazon ECS container agent configuration</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </li> <li> <p>For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.</p> </li> </ul>
  * @public
  */
 export interface LogConfiguration {
     /**
-     * <p>The log driver to use for the container.</p> <p>For tasks on Fargate, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks hosted on Amazon EC2 instances, the supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>, <code>json-file</code>, <code>journald</code>, <code>syslog</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For more information about using the <code>awslogs</code> log driver, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html">Send Amazon ECS logs to CloudWatch</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>For more information about using the <code>awsfirelens</code> log driver, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html">Send Amazon ECS logs to an Amazon Web Services service or Amazon Web Services Partner</a>.</p> <note> <p>If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's <a href="https://github.com/aws/amazon-ecs-agent">available on GitHub</a> and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.</p> </note>
+     * <p>The log driver to use for the container.</p> <p>For tasks on Fargate, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks hosted on Amazon EC2 instances, the supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>, <code>json-file</code>, <code>journald</code>, <code>syslog</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks on Amazon ECS Managed Instances, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, <code>awsfirelens</code>, and <code>json-file</code>.</p> <p>For more information about using the <code>awslogs</code> log driver, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html">Send Amazon ECS logs to CloudWatch</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>For more information about using the <code>awsfirelens</code> log driver, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html">Send Amazon ECS logs to an Amazon Web Services service or Amazon Web Services Partner</a>.</p> <note> <p>If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's <a href="https://github.com/aws/amazon-ecs-agent">available on GitHub</a> and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.</p> </note>
      * @public
      */
     logDriver: LogDriver | undefined;
@@ -3806,6 +3806,17 @@ export interface HostVolumeProperties {
      */
     sourcePath?: string | undefined;
 }
+/**
+ * <p>The configuration for a log driver volume in a daemon task definition. The volume contains the log files for each container on the container instance that uses the specified log driver in its <code>logConfiguration</code>. Containers that use a different log driver don't write log files to the volume.</p> <p>For the <code>json-file</code> log driver, the volume has one directory for each container, named with the container ID. Each directory contains the container's log file, <code>&lt;container-id&gt;-json.log</code>, and any rotated log files. After a container stops and Amazon ECS removes it, Amazon ECS deletes the container's directory. Read the log files before the container is removed.</p>
+ * @public
+ */
+export interface LogDriverVolumeConfiguration {
+    /**
+     * <p>The log driver whose log files the volume contains. The only supported value is <code>json-file</code>.</p>
+     * @public
+     */
+    driver: LogDriver | undefined;
+}
 /**
  * <p>A data volume definition for a daemon task.</p>
  * @public
@@ -3821,6 +3832,11 @@ export interface DaemonVolume {
      * @public
      */
     host?: HostVolumeProperties | undefined;
+    /**
+     * <p>The log driver volume configuration. With a log driver volume, the containers in a daemon task can read the log files that a log driver writes for the other tasks on the container instance. To read the log files, mount the volume into a container in the daemon task with <code>mountPoints</code>.</p> <p>Use <code>host</code> to bind mount a path on the container instance. Use <code>logDriverVolumeConfiguration</code> to read the log output of other tasks. You can't specify both for the same volume.</p>
+     * @public
+     */
+    logDriverVolumeConfiguration?: LogDriverVolumeConfiguration | undefined;
 }
 /**
  * <p>The details of a daemon task definition. A daemon task definition is a template that describes the containers that form a daemon. Daemons deploy cross-cutting software agents independently across your Amazon ECS infrastructure.</p>
@@ -7531,24 +7547,3 @@ export interface ServiceConnectTestTrafficRules {
      */
     header: ServiceConnectTestTrafficHeaderRules | undefined;
 }
-/**
- * <p>Each alias ("endpoint") is a fully-qualified name and port number that other tasks ("clients") can use to connect to this service.</p> <p>Each name and port mapping must be unique within the namespace.</p> <p>Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * @public
- */
-export interface ServiceConnectClientAlias {
-    /**
-     * <p>The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace.</p> <p>To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
-     * @public
-     */
-    port: number | undefined;
-    /**
-     * <p>The <code>dnsName</code> is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen.</p> <p>If this parameter isn't specified, the default value of <code>discoveryName.namespace</code> is used. If the <code>discoveryName</code> isn't specified, the port mapping name from the task definition is used in <code>portName.namespace</code>.</p> <p>To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are <code>database</code>, <code>db</code>, or the lowercase name of a database, such as <code>mysql</code> or <code>redis</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
-     * @public
-     */
-    dnsName?: string | undefined;
-    /**
-     * <p>The configuration for test traffic routing rules used during blue/green deployments with Amazon ECS Service Connect. This allows you to route a portion of traffic to the new service revision of your service for testing before shifting all production traffic.</p>
-     * @public
-     */
-    testTrafficRules?: ServiceConnectTestTrafficRules | undefined;
-}

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

@@ -1,5 +1,26 @@
 import type { AccessType, AvailabilityZoneRebalancing, Compatibility, Connectivity, DeploymentRolloutState, EBSResourceType, ExpressCpuArchitecture, ExpressGatewayServiceInclude, GatewayRouteStatus, HealthStatus, IpcMode, LaunchType, ManagedAgentName, ManagedResourceStatus, NetworkMode, PidMode, PropagateTags, ResourceManagementType, ScaleUnit, SchedulingStrategy, ServiceDeploymentStatus, ServiceField, SortOrder, StabilityStatus, StopServiceDeploymentStopType, TaskDefinitionStatus, TaskField, TaskFilesystemType, TaskSetField, TaskStopCode } from "./enums";
-import type { Attachment, Attribute, CapacityProviderStrategyItem, ContainerDefinition, CreatedAt, DeploymentConfiguration, DeploymentController, ECSExpressGatewayService, EnvironmentFile, EphemeralStorage, ExpressGatewayContainer, ExpressGatewayScalingTarget, ExpressGatewayServiceConfiguration, ExpressGatewayServiceNetworkConfiguration, ExpressGatewayServiceStatus, Failure, GatewayConnector, InferenceAccelerator, KeyValuePair, LoadBalancer, LogConfiguration, MonitoringConfiguration, NetworkBinding, NetworkConfiguration, PlacementConstraint, PlacementStrategy, ProxyConfiguration, ResourceRequirement, RuntimePlatform, ServiceConnectAccessLogConfiguration, ServiceConnectClientAlias, ServiceConnectContainerConfiguration, SharingStrategy, Tag, TaskDefinition, TaskDefinitionPlacementConstraint, Volume } from "./models_0";
+import type { Attachment, Attribute, CapacityProviderStrategyItem, ContainerDefinition, CreatedAt, DeploymentConfiguration, DeploymentController, ECSExpressGatewayService, EnvironmentFile, EphemeralStorage, ExpressGatewayContainer, ExpressGatewayScalingTarget, ExpressGatewayServiceConfiguration, ExpressGatewayServiceNetworkConfiguration, ExpressGatewayServiceStatus, Failure, GatewayConnector, InferenceAccelerator, KeyValuePair, LoadBalancer, LogConfiguration, MonitoringConfiguration, NetworkBinding, NetworkConfiguration, PlacementConstraint, PlacementStrategy, ProxyConfiguration, ResourceRequirement, RuntimePlatform, ServiceConnectAccessLogConfiguration, ServiceConnectContainerConfiguration, ServiceConnectTestTrafficRules, SharingStrategy, Tag, TaskDefinition, TaskDefinitionPlacementConstraint, Volume } from "./models_0";
+/**
+ * <p>Each alias ("endpoint") is a fully-qualified name and port number that other tasks ("clients") can use to connect to this service.</p> <p>Each name and port mapping must be unique within the namespace.</p> <p>Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * @public
+ */
+export interface ServiceConnectClientAlias {
+    /**
+     * <p>The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace.</p> <p>To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * @public
+     */
+    port: number | undefined;
+    /**
+     * <p>The <code>dnsName</code> is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen.</p> <p>If this parameter isn't specified, the default value of <code>discoveryName.namespace</code> is used. If the <code>discoveryName</code> isn't specified, the port mapping name from the task definition is used in <code>portName.namespace</code>.</p> <p>To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are <code>database</code>, <code>db</code>, or the lowercase name of a database, such as <code>mysql</code> or <code>redis</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * @public
+     */
+    dnsName?: string | undefined;
+    /**
+     * <p>The configuration for test traffic routing rules used during blue/green deployments with Amazon ECS Service Connect. This allows you to route a portion of traffic to the new service revision of your service for testing before shifting all production traffic.</p>
+     * @public
+     */
+    testTrafficRules?: ServiceConnectTestTrafficRules | undefined;
+}
 /**
  * <p>An object that represents the timeout configurations for Service Connect.</p> <note> <p>If <code>idleTimeout</code> is set to a time that is less than <code>perRequestTimeout</code>, the connection will close when the <code>idleTimeout</code> is reached and not the <code>perRequestTimeout</code>.</p> </note>
  * @public
@@ -105,7 +126,7 @@ export interface ServiceConnectConfiguration {
      */
     services?: ServiceConnectService[] | undefined;
     /**
-     * <p>The log configuration for the container. This parameter maps to <code>LogConfig</code> in the docker container create command and the <code>--log-driver</code> option to docker run.</p> <p>By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition.</p> <p>Understand the following when specifying a log configuration for your containers.</p> <ul> <li> <p>Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent.</p> <p>For tasks on Fargate, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks hosted on Amazon EC2 instances, the supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>, <code>json-file</code>, <code>journald</code>,<code>syslog</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> </li> <li> <p>This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.</p> </li> <li> <p>For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the <code>ECS_AVAILABLE_LOGGING_DRIVERS</code> environment variable before containers placed on that instance can use these log configuration options. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html">Amazon ECS container agent configuration</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </li> <li> <p>For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.</p> </li> </ul>
+     * <p>The log configuration for the container. This parameter maps to <code>LogConfig</code> in the docker container create command and the <code>--log-driver</code> option to docker run.</p> <p>By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition.</p> <p>Understand the following when specifying a log configuration for your containers.</p> <ul> <li> <p>Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent.</p> <p>For tasks on Fargate, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks hosted on Amazon EC2 instances, the supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>, <code>json-file</code>, <code>journald</code>,<code>syslog</code>, <code>splunk</code>, and <code>awsfirelens</code>.</p> <p>For tasks on Amazon ECS Managed Instances, the supported log drivers are <code>awslogs</code>, <code>splunk</code>, <code>awsfirelens</code>, and <code>json-file</code>.</p> </li> <li> <p>This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.</p> </li> <li> <p>For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the <code>ECS_AVAILABLE_LOGGING_DRIVERS</code> environment variable before containers placed on that instance can use these log configuration options. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html">Amazon ECS container agent configuration</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> </li> <li> <p>For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.</p> </li> </ul>
      * @public
      */
     logConfiguration?: LogConfiguration | undefined;

package/dist-types/runtimeConfig.d.ts

@@ -44,6 +44,7 @@ export declare const getRuntimeConfig: (config: ECSClientConfig) => {
     authSchemePreference: string[] | import("@smithy/types").Provider<string[]>;
     bodyLengthChecker: import("@smithy/types").BodyLengthCalculator;
     credentialDefaultProvider: ((init?: import("@aws-sdk/credential-provider-node").DefaultProviderInit) => import("@aws-sdk/credential-provider-node").MemoizedRuntimeConfigAwsCredentialIdentityProvider) | ((input: any) => import("@smithy/types").AwsCredentialIdentityProvider);
+    defaultSocketTimeout: number | undefined;
     defaultUserAgentProvider: (config?: import("@aws-sdk/core/client").PreviouslyResolved) => Promise<import("@smithy/types").UserAgent>;
     maxAttempts: number | import("@smithy/types").Provider<number>;
     region: string | import("@smithy/types").Provider<string>;

package/dist-types/schemas/schemas_0.d.ts

@@ -283,6 +283,7 @@ export declare var ListTasksRequest$: StaticStructureSchema;
 export declare var ListTasksResponse$: StaticStructureSchema;
 export declare var LoadBalancer$: StaticStructureSchema;
 export declare var LogConfiguration$: StaticStructureSchema;
+export declare var LogDriverVolumeConfiguration$: StaticStructureSchema;
 export declare var ManagedAgent$: StaticStructureSchema;
 export declare var ManagedAgentStateChange$: StaticStructureSchema;
 export declare var ManagedApplicationAutoScalingPolicy$: StaticStructureSchema;

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

@@ -996,9 +996,13 @@ export interface DaemonContainerDefinition {
 export interface HostVolumeProperties {
   sourcePath?: string | undefined;
 }
+export interface LogDriverVolumeConfiguration {
+  driver: LogDriver | undefined;
+}
 export interface DaemonVolume {
   name?: string | undefined;
   host?: HostVolumeProperties | undefined;
+  logDriverVolumeConfiguration?: LogDriverVolumeConfiguration | undefined;
 }
 export interface DaemonTaskDefinition {
   daemonTaskDefinitionArn?: string | undefined;
@@ -1938,8 +1942,3 @@ export interface ServiceConnectTestTrafficHeaderRules {
 export interface ServiceConnectTestTrafficRules {
   header: ServiceConnectTestTrafficHeaderRules | undefined;
 }
-export interface ServiceConnectClientAlias {
-  port: number | undefined;
-  dnsName?: string | undefined;
-  testTrafficRules?: ServiceConnectTestTrafficRules | undefined;
-}

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

@@ -61,14 +61,19 @@ import {
   ResourceRequirement,
   RuntimePlatform,
   ServiceConnectAccessLogConfiguration,
-  ServiceConnectClientAlias,
   ServiceConnectContainerConfiguration,
+  ServiceConnectTestTrafficRules,
   SharingStrategy,
   Tag,
   TaskDefinition,
   TaskDefinitionPlacementConstraint,
   Volume,
 } from "./models_0";
+export interface ServiceConnectClientAlias {
+  port: number | undefined;
+  dnsName?: string | undefined;
+  testTrafficRules?: ServiceConnectTestTrafficRules | undefined;
+}
 export interface TimeoutConfiguration {
   idleTimeoutSeconds?: number | undefined;
   perRequestTimeoutSeconds?: number | undefined;

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

@@ -78,6 +78,7 @@ export declare const getRuntimeConfig: (config: ECSClientConfig) => {
         init?: import("@aws-sdk/credential-provider-node").DefaultProviderInit,
       ) => import("@aws-sdk/credential-provider-node").MemoizedRuntimeConfigAwsCredentialIdentityProvider)
     | ((input: any) => import("@smithy/types").AwsCredentialIdentityProvider);
+  defaultSocketTimeout: number | undefined;
   defaultUserAgentProvider: (
     config?: import("@aws-sdk/core/client").PreviouslyResolved,
   ) => Promise<import("@smithy/types").UserAgent>;

package/dist-types/ts3.4/schemas/schemas_0.d.ts

@@ -283,6 +283,7 @@ export declare var ListTasksRequest$: StaticStructureSchema;
 export declare var ListTasksResponse$: StaticStructureSchema;
 export declare var LoadBalancer$: StaticStructureSchema;
 export declare var LogConfiguration$: StaticStructureSchema;
+export declare var LogDriverVolumeConfiguration$: StaticStructureSchema;
 export declare var ManagedAgent$: StaticStructureSchema;
 export declare var ManagedAgentStateChange$: StaticStructureSchema;
 export declare var ManagedApplicationAutoScalingPolicy$: StaticStructureSchema;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aws-sdk/client-ecs",
-  "version": "3.1161.0",
+  "version": "3.1162.0",
   "description": "AWS SDK for JavaScript Ecs Client for Node.js, Browser and React Native",
   "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-ecs",
   "license": "Apache-2.0",
@@ -48,8 +48,8 @@
     "test:index": "tsc -p tsconfig.test.json && node ./test/index-objects.spec.mjs"
   },
   "dependencies": {
-    "@aws-sdk/core": "^3.979.1",
-    "@aws-sdk/credential-provider-node": "^3.972.92",
+    "@aws-sdk/core": "^3.980.0",
+    "@aws-sdk/credential-provider-node": "^3.972.93",
     "@aws-sdk/types": "^3.975.0",
     "@smithy/core": "^3.38.0",
     "@smithy/fetch-http-handler": "^5.8.0",