@pulumi/aws-native 1.28.0-alpha.1745559155 → 1.28.0-alpha.1745848410

package/types/output.d.ts

@@ -2107,6 +2107,10 @@ export declare namespace apigatewayv2 {
          * The endpoint type.
          */
         endpointType?: string;
+        /**
+         * The IP address types that can invoke the domain name. Use `ipv4` to allow only IPv4 addresses to invoke your domain name, or use `dualstack` to allow both IPv4 and IPv6 addresses to invoke your domain name.
+         */
+        ipAddressType?: string;
         /**
          * The Amazon resource name (ARN) for the public certificate issued by ACMlong. This ARN is used to validate custom domain ownership. It's required only if you configure mutual TLS and use either an ACM-imported or a private CA certificate ARN as the regionalCertificateArn.
          */
@@ -5565,6 +5569,24 @@ export declare namespace appsync {
     interface ChannelNamespaceAuthMode {
         authType?: enums.appsync.ChannelNamespaceAuthenticationType;
     }
+    interface ChannelNamespaceHandlerConfig {
+        behavior: enums.appsync.ChannelNamespaceHandlerBehavior;
+        integration: outputs.appsync.ChannelNamespaceIntegration;
+    }
+    interface ChannelNamespaceHandlerConfigs {
+        onPublish?: outputs.appsync.ChannelNamespaceHandlerConfig;
+        onSubscribe?: outputs.appsync.ChannelNamespaceHandlerConfig;
+    }
+    interface ChannelNamespaceIntegration {
+        /**
+         * Data source to invoke for this integration.
+         */
+        dataSourceName: string;
+        lambdaConfig?: outputs.appsync.ChannelNamespaceLambdaConfig;
+    }
+    interface ChannelNamespaceLambdaConfig {
+        invokeType: enums.appsync.ChannelNamespaceInvokeType;
+    }
     interface DataSourceAuthorizationConfig {
         /**
          * The authorization type that the HTTP endpoint requires.
@@ -6022,6 +6044,9 @@ export declare namespace aps {
          * An array of series labels
          */
         labelSet: outputs.aps.WorkspaceLabel[];
+        /**
+         * This structure contains the information about the limits that apply to time series that match this label set.
+         */
         limits: outputs.aps.WorkspaceLimitsPerLabelSetEntry;
     }
     /**
@@ -6453,20 +6478,26 @@ export declare namespace autoscaling {
          */
         min?: number;
     }
+    /**
+     * The baseline performance to consider, using an instance family as a baseline reference. The instance family establishes the lowest acceptable level of performance. Auto Scaling uses this baseline to guide instance type selection, but there is no guarantee that the selected instance types will always exceed the baseline for every application.
+     *  Currently, this parameter only supports CPU performance as a baseline performance factor. For example, specifying ``c6i`` uses the CPU performance of the ``c6i`` family as the baseline reference.
+     */
     interface AutoScalingGroupBaselinePerformanceFactorsRequest {
         /**
          * The CPU performance to consider, using an instance family as the baseline reference.
          */
         cpu?: outputs.autoscaling.AutoScalingGroupCpuPerformanceFactorRequest;
     }
+    /**
+     * Describes the Capacity Reservation preference and targeting options. If you specify ``open`` or ``none`` for ``CapacityReservationPreference``, do not specify a ``CapacityReservationTarget``.
+     */
     interface AutoScalingGroupCapacityReservationSpecification {
         /**
          * The capacity reservation preference. The following options are available:
-         *
-         * - `capacity-reservations-only` - Auto Scaling will only launch instances into a Capacity Reservation or Capacity Reservation resource group. If capacity isn't available, instances will fail to launch.
-         * - `capacity-reservations-first` - Auto Scaling will try to launch instances into a Capacity Reservation or Capacity Reservation resource group first. If capacity isn't available, instances will run in On-Demand capacity.
-         * - `none` - Auto Scaling will not launch instances into a Capacity Reservation. Instances will run in On-Demand capacity.
-         * - `default` - Auto Scaling uses the Capacity Reservation preference from your launch template or an open Capacity Reservation.
+         *   +   ``capacity-reservations-only`` - Auto Scaling will only launch instances into a Capacity Reservation or Capacity Reservation resource group. If capacity isn't available, instances will fail to launch.
+         *   +   ``capacity-reservations-first`` - Auto Scaling will try to launch instances into a Capacity Reservation or Capacity Reservation resource group first. If capacity isn't available, instances will run in On-Demand capacity.
+         *   +   ``none`` - Auto Scaling will not launch instances into a Capacity Reservation. Instances will run in On-Demand capacity.
+         *   +   ``default`` - Auto Scaling uses the Capacity Reservation preference from your launch template or an open Capacity Reservation.
          */
         capacityReservationPreference: string;
         /**
@@ -6474,6 +6505,9 @@ export declare namespace autoscaling {
          */
         capacityReservationTarget?: outputs.autoscaling.AutoScalingGroupCapacityReservationTarget;
     }
+    /**
+     * The target for the Capacity Reservation. Specify Capacity Reservations IDs or Capacity Reservation resource group ARNs.
+     */
     interface AutoScalingGroupCapacityReservationTarget {
         /**
          * The Capacity Reservation IDs to launch instances into.
@@ -6484,11 +6518,13 @@ export declare namespace autoscaling {
          */
         capacityReservationResourceGroupArns?: string[];
     }
+    /**
+     * The CPU performance to consider, using an instance family as the baseline reference.
+     */
     interface AutoScalingGroupCpuPerformanceFactorRequest {
         /**
          * Specify an instance family to use as the baseline reference for CPU performance. All instance types that match your specified attributes will be compared against the CPU performance of the referenced instance family, regardless of CPU manufacturer or architecture differences.
-         *
-         * > Currently only one instance family can be specified in the list.
+         *   Currently only one instance family can be specified in the list.
          */
         references?: outputs.autoscaling.AutoScalingGroupPerformanceFactorReferenceRequest[];
     }
@@ -6973,7 +7009,27 @@ export declare namespace autoscaling {
          */
         topicArn: string[];
     }
+    /**
+     * Specify an instance family to use as the baseline reference for CPU performance. All instance types that All instance types that match your specified attributes will be compared against the CPU performance of the referenced instance family, regardless of CPU manufacturer or architecture differences.
+     *   Currently only one instance family can be specified in the list.
+     */
     interface AutoScalingGroupPerformanceFactorReferenceRequest {
+        /**
+         * The instance family to use as a baseline reference.
+         *   Make sure that you specify the correct value for the instance family. The instance family is everything before the period (.) in the instance type name. For example, in the instance ``c6i.large``, the instance family is ``c6i``, not ``c6``. For more information, see [Amazon EC2 instance type naming conventions](https://docs.aws.amazon.com/ec2/latest/instancetypes/instance-type-names.html) in *Amazon EC2 Instance Types*.
+         *   The following instance types are *not supported* for performance protection.
+         *   +   ``c1``
+         *   +   ``g3| g3s``
+         *   +   ``hpc7g``
+         *   +   ``m1| m2``
+         *   +   ``mac1 | mac2 | mac2-m1ultra | mac2-m2 | mac2-m2pro``
+         *   +   ``p3dn | p4d | p5``
+         *   +   ``t1``
+         *   +   ``u-12tb1 | u-18tb1 | u-24tb1 | u-3tb1 | u-6tb1 | u-9tb1 | u7i-12tb | u7in-16tb | u7in-24tb | u7in-32tb``
+         *
+         *  If you performance protection by specifying a supported instance family, the returned instance types will exclude the preceding unsupported instance families.
+         *  If you specify an unsupported instance family as a value for baseline performance, the API returns an empty response.
+         */
         instanceFamily?: string;
     }
     /**
@@ -8233,7 +8289,7 @@ export declare namespace batch {
          */
         jobExecutionTimeoutMinutes?: number;
         /**
-         * Specifies whether jobs are automatically terminated when the computer environment infrastructure is updated. The default value is `false` .
+         * Specifies whether jobs are automatically terminated when the compute environment infrastructure is updated. The default value is `false` .
          */
         terminateJobsOnUpdate?: boolean;
     }
@@ -9858,6 +9914,9 @@ export declare namespace bedrock {
          */
         types?: enums.bedrock.DataAutomationProjectAudioExtractionCategoryType[];
     }
+    interface DataAutomationProjectAudioOverrideConfiguration {
+        modalityProcessing?: outputs.bedrock.DataAutomationProjectModalityProcessingConfiguration;
+    }
     interface DataAutomationProjectAudioStandardExtraction {
         /**
          * Settings for generating data from audio.
@@ -9942,6 +10001,7 @@ export declare namespace bedrock {
         types?: enums.bedrock.DataAutomationProjectDocumentOutputTextFormatType[];
     }
     interface DataAutomationProjectDocumentOverrideConfiguration {
+        modalityProcessing?: outputs.bedrock.DataAutomationProjectModalityProcessingConfiguration;
         /**
          * Whether document splitter is enabled for a project.
          */
@@ -9993,6 +10053,9 @@ export declare namespace bedrock {
          */
         types?: enums.bedrock.DataAutomationProjectImageExtractionCategoryType[];
     }
+    interface DataAutomationProjectImageOverrideConfiguration {
+        modalityProcessing?: outputs.bedrock.DataAutomationProjectModalityProcessingConfiguration;
+    }
     interface DataAutomationProjectImageStandardExtraction {
         /**
          * Settings for generating bounding boxes.
@@ -10023,14 +10086,30 @@ export declare namespace bedrock {
          */
         generativeField?: outputs.bedrock.DataAutomationProjectImageStandardGenerativeField;
     }
+    interface DataAutomationProjectModalityProcessingConfiguration {
+        state?: enums.bedrock.DataAutomationProjectState;
+    }
+    /**
+     * Modality routing configuration
+     */
+    interface DataAutomationProjectModalityRoutingConfiguration {
+        jpeg?: enums.bedrock.DataAutomationProjectDesiredModality;
+        mov?: enums.bedrock.DataAutomationProjectDesiredModality;
+        mp4?: enums.bedrock.DataAutomationProjectDesiredModality;
+        png?: enums.bedrock.DataAutomationProjectDesiredModality;
+    }
     /**
      * Override configuration
      */
     interface DataAutomationProjectOverrideConfiguration {
+        audio?: outputs.bedrock.DataAutomationProjectAudioOverrideConfiguration;
         /**
          * Additional settings for a project.
          */
         document?: outputs.bedrock.DataAutomationProjectDocumentOverrideConfiguration;
+        image?: outputs.bedrock.DataAutomationProjectImageOverrideConfiguration;
+        modalityRouting?: outputs.bedrock.DataAutomationProjectModalityRoutingConfiguration;
+        video?: outputs.bedrock.DataAutomationProjectVideoOverrideConfiguration;
     }
     interface DataAutomationProjectSplitterConfiguration {
         /**
@@ -10075,6 +10154,9 @@ export declare namespace bedrock {
          */
         types?: enums.bedrock.DataAutomationProjectVideoExtractionCategoryType[];
     }
+    interface DataAutomationProjectVideoOverrideConfiguration {
+        modalityProcessing?: outputs.bedrock.DataAutomationProjectModalityProcessingConfiguration;
+    }
     interface DataAutomationProjectVideoStandardExtraction {
         /**
          * Settings for generating bounding boxes.
@@ -13236,32 +13318,6 @@ export declare namespace cassandra {
     }
 }
 export declare namespace ce {
-    /**
-     * A key-value pair to associate with a resource.
-     */
-    interface AnomalyMonitorResourceTag {
-        /**
-         * The key name for the tag.
-         */
-        key: string;
-        /**
-         * The value for the tag.
-         */
-        value: string;
-    }
-    /**
-     * A key-value pair to associate with a resource.
-     */
-    interface AnomalySubscriptionResourceTag {
-        /**
-         * The key name for the tag.
-         */
-        key: string;
-        /**
-         * The value for the tag.
-         */
-        value: string;
-    }
     interface AnomalySubscriptionSubscriber {
         /**
          * The email address or SNS Topic Amazon Resource Name (ARN), depending on the `Type` .
@@ -14548,6 +14604,7 @@ export declare namespace cloudfront {
          * A comment to describe the distribution. The comment cannot be longer than 128 characters.
          */
         comment?: string;
+        connectionMode?: enums.cloudfront.DistributionConnectionMode;
         /**
          * The identifier of a continuous deployment policy. For more information, see ``CreateContinuousDeploymentPolicy``.
          */
@@ -14633,6 +14690,7 @@ export declare namespace cloudfront {
          * A Boolean that indicates whether this is a staging distribution. When this value is ``true``, this is a staging distribution. When this value is ``false``, this is not a staging distribution.
          */
         staging?: boolean;
+        tenantConfig?: outputs.cloudfront.DistributionConfigTenantConfigProperties;
         /**
          * A complex type that determines the distribution's SSL/TLS configuration for communicating with viewers.
          */
@@ -14643,6 +14701,9 @@ export declare namespace cloudfront {
          */
         webAclId?: string;
     }
+    interface DistributionConfigTenantConfigProperties {
+        parameterDefinitions?: outputs.cloudfront.DistributionParameterDefinition[];
+    }
     /**
      * This field is deprecated. We recommend that you use a cache policy or an origin request policy instead of this field.
      *  If you want to include cookies in the cache key, use a cache policy. For more information, see [Creating cache policies](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/controlling-the-cache-key.html#cache-key-create-cache-policy) in the *Amazon CloudFront Developer Guide*.
@@ -15182,6 +15243,18 @@ export declare namespace cloudfront {
          */
         originShieldRegion?: string;
     }
+    interface DistributionParameterDefinition {
+        definition: outputs.cloudfront.DistributionParameterDefinitionDefinitionProperties;
+        name: string;
+    }
+    interface DistributionParameterDefinitionDefinitionProperties {
+        stringSchema?: outputs.cloudfront.DistributionParameterDefinitionDefinitionPropertiesStringSchemaProperties;
+    }
+    interface DistributionParameterDefinitionDefinitionPropertiesStringSchemaProperties {
+        comment?: string;
+        defaultValue?: string;
+        required: boolean;
+    }
     /**
      * A complex type that identifies ways in which you want to restrict distribution of your content.
      */
@@ -15220,6 +15293,35 @@ export declare namespace cloudfront {
          */
         quantity: number;
     }
+    interface DistributionTenantCertificate {
+        arn?: string;
+    }
+    interface DistributionTenantCustomizations {
+        certificate?: outputs.cloudfront.DistributionTenantCertificate;
+        geoRestrictions?: outputs.cloudfront.DistributionTenantGeoRestrictionCustomization;
+        webAcl?: outputs.cloudfront.DistributionTenantWebAclCustomization;
+    }
+    interface DistributionTenantDomainResult {
+        domain?: string;
+        status?: enums.cloudfront.DistributionTenantDomainResultStatus;
+    }
+    interface DistributionTenantGeoRestrictionCustomization {
+        locations?: string[];
+        restrictionType?: enums.cloudfront.DistributionTenantGeoRestrictionCustomizationRestrictionType;
+    }
+    interface DistributionTenantManagedCertificateRequest {
+        certificateTransparencyLoggingPreference?: enums.cloudfront.DistributionTenantManagedCertificateRequestCertificateTransparencyLoggingPreference;
+        primaryDomainName?: string;
+        validationTokenHost?: enums.cloudfront.DistributionTenantManagedCertificateRequestValidationTokenHost;
+    }
+    interface DistributionTenantParameter {
+        name?: string;
+        value?: string;
+    }
+    interface DistributionTenantWebAclCustomization {
+        action?: enums.cloudfront.DistributionTenantWebAclCustomizationAction;
+        arn?: string;
+    }
     /**
      * A complex type that determines the distribution's SSL/TLS configuration for communicating with viewers.
      *  If the distribution doesn't use ``Aliases`` (also known as alternate domain names or CNAMEs)—that is, if the distribution uses the CloudFront domain name such as ``d111111abcdef8.cloudfront.net``—set ``CloudFrontDefaultCertificate`` to ``true`` and leave all other fields empty.
@@ -16548,6 +16650,10 @@ export declare namespace codepipeline {
          * The action's configuration. These are key-value pairs that specify input values for an action.
          */
         configuration?: any;
+        /**
+         * The list of environment variables that are input to a compute based action.
+         */
+        environmentVariables?: outputs.codepipeline.PipelineEnvironmentVariable[];
         /**
          * The name or ID of the artifact consumed by the action, such as a test or build artifact. While the field is not a required parameter, most actions have an action configuration that requires a specified quantity of input artifacts. To refer to the action configuration specification by action provider, see the [Action structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference.html) in the *AWS CodePipeline User Guide* .
          *
@@ -16688,6 +16794,19 @@ export declare namespace codepipeline {
          */
         type: string;
     }
+    /**
+     * Represents information about the environment variable of an action.
+     */
+    interface PipelineEnvironmentVariable {
+        /**
+         * The name of the environment variable.
+         */
+        name: string;
+        /**
+         * The value of the environment variable.
+         */
+        value: string;
+    }
     /**
      * The configuration that specifies the result, such as rollback, to occur upon stage failure
      */
@@ -23046,9 +23165,9 @@ export declare namespace dynamodb {
         attributeName: string;
         /**
          * The data type for the attribute, where:
-         *   +   ``S`` - the attribute is of type String
-         *   +   ``N`` - the attribute is of type Number
-         *   +   ``B`` - the attribute is of type Binary
+         *   +  ``S`` - the attribute is of type String
+         *   +  ``N`` - the attribute is of type Number
+         *   +  ``B`` - the attribute is of type Binary
          */
         attributeType: string;
     }
@@ -23088,8 +23207,8 @@ export declare namespace dynamodb {
         indexName: string;
         /**
          * The complete key schema for a global secondary index, which consists of one or more pairs of attribute names and key types:
-         *   +   ``HASH`` - partition key
-         *   +   ``RANGE`` - sort key
+         *   +  ``HASH`` - partition key
+         *   +  ``RANGE`` - sort key
          *
          *   The partition key of an item is also known as its *hash attribute*. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values.
          *  The sort key of an item is also known as its *range attribute*. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
@@ -23155,8 +23274,8 @@ export declare namespace dynamodb {
         attributeName: string;
         /**
          * The role that this key attribute will assume:
-         *   +   ``HASH`` - partition key
-         *   +   ``RANGE`` - sort key
+         *   +  ``HASH`` - partition key
+         *   +  ``RANGE`` - sort key
          *
          *   The partition key of an item is also known as its *hash attribute*. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values.
          *  The sort key of an item is also known as its *range attribute*. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
@@ -23187,8 +23306,8 @@ export declare namespace dynamodb {
         indexName: string;
         /**
          * The complete key schema for the local secondary index, consisting of one or more pairs of attribute names and key types:
-         *   +   ``HASH`` - partition key
-         *   +   ``RANGE`` - sort key
+         *   +  ``HASH`` - partition key
+         *   +  ``RANGE`` - sort key
          *
          *   The partition key of an item is also known as its *hash attribute*. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values.
          *  The sort key of an item is also known as its *range attribute*. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
@@ -23238,9 +23357,9 @@ export declare namespace dynamodb {
         nonKeyAttributes?: string[];
         /**
          * The set of attributes that are projected into the index:
-         *   +   ``KEYS_ONLY`` - Only the index and primary keys are projected into the index.
-         *   +   ``INCLUDE`` - In addition to the attributes described in ``KEYS_ONLY``, the secondary index will include other non-key attributes that you specify.
-         *   +   ``ALL`` - All of the table attributes are projected into the index.
+         *   +  ``KEYS_ONLY`` - Only the index and primary keys are projected into the index.
+         *   +  ``INCLUDE`` - In addition to the attributes described in ``KEYS_ONLY``, the secondary index will include other non-key attributes that you specify.
+         *   +  ``ALL`` - All of the table attributes are projected into the index.
          *
          *  When using the DynamoDB console, ``ALL`` is selected by default.
          */
@@ -23310,7 +23429,7 @@ export declare namespace dynamodb {
         sseEnabled: boolean;
         /**
          * Server-side encryption type. The only supported value is:
-         *   +   ``KMS`` - Server-side encryption that uses KMSlong. The key is stored in your account and is managed by KMS (KMS charges apply).
+         *   +  ``KMS`` - Server-side encryption that uses KMSlong. The key is stored in your account and is managed by KMS (KMS charges apply).
          */
         sseType?: string;
     }
@@ -23325,10 +23444,10 @@ export declare namespace dynamodb {
         resourcePolicy?: outputs.dynamodb.TableResourcePolicy;
         /**
          * When an item in the table is modified, ``StreamViewType`` determines what information is written to the stream for this table. Valid values for ``StreamViewType`` are:
-         *   +   ``KEYS_ONLY`` - Only the key attributes of the modified item are written to the stream.
-         *   +   ``NEW_IMAGE`` - The entire item, as it appears after it was modified, is written to the stream.
-         *   +   ``OLD_IMAGE`` - The entire item, as it appeared before it was modified, is written to the stream.
-         *   +   ``NEW_AND_OLD_IMAGES`` - Both the new and the old item images of the item are written to the stream.
+         *   +  ``KEYS_ONLY`` - Only the key attributes of the modified item are written to the stream.
+         *   +  ``NEW_IMAGE`` - The entire item, as it appears after it was modified, is written to the stream.
+         *   +  ``OLD_IMAGE`` - The entire item, as it appeared before it was modified, is written to the stream.
+         *   +  ``NEW_AND_OLD_IMAGES`` - Both the new and the old item images of the item are written to the stream.
          */
         streamViewType: string;
     }
@@ -23712,6 +23831,7 @@ export declare namespace ec2 {
          *
          * - For instance types with FPGA accelerators, specify `fpga` .
          * - For instance types with GPU accelerators, specify `gpu` .
+         * - For instance types with Inference accelerators, specify `inference` .
          *
          * Default: Any accelerator type
          */
@@ -26744,6 +26864,7 @@ export declare namespace ec2 {
          *
          * - For instance types with FPGA accelerators, specify `fpga` .
          * - For instance types with GPU accelerators, specify `gpu` .
+         * - For instance types with Inference accelerators, specify `inference` .
          *
          * Default: Any accelerator type
          */
@@ -27954,6 +28075,23 @@ export declare namespace ec2 {
     }
 }
 export declare namespace ecr {
+    /**
+     * The details of a scanning repository filter.
+     */
+    interface RegistryScanningConfigurationRepositoryFilter {
+        filter: string;
+        filterType: enums.ecr.RegistryScanningConfigurationFilterType;
+    }
+    /**
+     * A rule representing the details of a scanning configuration.
+     */
+    interface RegistryScanningConfigurationScanningRule {
+        /**
+         * The repository filters associated with the scanning configuration for a private registry.
+         */
+        repositoryFilters: outputs.ecr.RegistryScanningConfigurationRepositoryFilter[];
+        scanFrequency: enums.ecr.RegistryScanningConfigurationScanFrequency;
+    }
     /**
      * The replication configuration for a registry.
      */
@@ -28580,7 +28718,9 @@ export declare namespace ecs {
         /**
          * The configuration options to send to the log driver.
          *  The options you can specify depend on the log driver. Some of the options you can specify when you use the ``awslogs`` log driver to route logs to Amazon CloudWatch include the following:
-         *   + awslogs-create-group Required: No Specify whether you want the log group to be created automatically. If this option isn't specified, it defaults to false. Your IAM policy must include the logs:CreateLogGroup permission before you attempt to use awslogs-create-group. + awslogs-region Required: Yes Specify the Region that the awslogs log driver is to send your Docker logs to. You can choose to send all of your logs from clusters in different Regions to a single region in CloudWatch Logs. This is so that they're all visible in one location. Otherwise, you can separate them by Region for more granularity. Make sure that the specified log group exists in the Region that you specify with this option. + awslogs-group Required: Yes Make sure to specify a log group that the awslogs log driver sends its log streams to. + awslogs-stream-prefix Required: Yes, when using the Fargate launch type.Optional for the EC2 launch type, required for the Fargate launch type. Use the awslogs-stream-prefix option to associate a log stream with the specified prefix, the container name, and the ID of the Amazon ECS task that the container belongs to. If you specify a prefix with this option, then the log stream takes the format prefix-name/container-name/ecs-task-id. If you don't specify a prefix with this option, then the log stream is named after the container ID that's assigned by the Docker daemon on the container instance. Because it's difficult to trace logs back to the container that sent them with just the Docker container ID (which is only available on the container instance), we recommend that you specify a prefix with this option. For Amazon ECS services, you can use the service name as the prefix. Doing so, you can trace log streams to the service that the container belongs to, the name of the container that sent them, and the ID of the task that the container belongs to. You must specify a stream-prefix for your logs to have your logs appear in the Log pane when using the Amazon ECS console. + awslogs-datetime-format Required: No This option defines a multiline start pattern in Python strftime format. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. One example of a use case for using this format is for parsing output such as a stack dump, which might otherwise be logged in multiple entries. The correct pattern allows it to be captured in a single entry. For more information, see awslogs-datetime-format. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + awslogs-multiline-pattern Required: No This option defines a multiline start pattern that uses a regular expression. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. For more information, see awslogs-multiline-pattern. This option is ignored if awslogs-datetime-format is also configured. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + mode Required: No Valid values: non-blocking | blocking This option defines the delivery mode of log messages from the container to CloudWatch Logs. The delivery mode you choose affects application availability when the flow of logs from container to CloudWatch is interrupted. If you use the blocking mode and the flow of logs to CloudWatch is interrupted, calls from container code to write to the stdout and stderr streams will block. The logging thread of the application will block as a result. This may cause the application to become unresponsive and lead to container healthcheck failure. If you use the non-blocking mode, the container's logs are instead stored in an in-memory intermediate buffer configured with the max-buffer-size option. This prevents the application from becoming unresponsive when logs cannot be sent to CloudWatch. We recommend using this mode if you want to ensure service availability and are okay with some log loss. For more information, see Preventing log loss with non-blocking mode in the awslogs container log driver. + max-buffer-size Required: No Default value: 1m When non-blocking mode is used, the max-buffer-size log option controls the size of the buffer that's used for intermediate message storage. Make sure to specify an adequate buffer size based on your application. When the buffer fills up, further logs cannot be stored. Logs that cannot be stored are lost.
+         *   + awslogs-create-group Required: No Specify whether you want the log group to be created automatically. If this option isn't specified, it defaults to false. Your IAM policy must include the logs:CreateLogGroup permission before you attempt to use awslogs-create-group. + awslogs-region Required: Yes Specify the Region that the awslogs log driver is to send your Docker logs to. You can choose to send all of your logs from clusters in different Regions to a single region in CloudWatch Logs. This is so that they're all visible in one location. Otherwise, you can separate them by Region for more granularity. Make sure that the specified log group exists in the Region that you specify with this option. + awslogs-group Required: Yes Make sure to specify a log group that the awslogs log driver sends its log streams to. + awslogs-stream-prefix Required: Yes, when using Fargate.Optional when using EC2. Use the awslogs-stream-prefix option to associate a log stream with the specified prefix, the container name, and the ID of the Amazon ECS task that the container belongs to. If you specify a prefix with this option, then the log stream takes the format prefix-name/container-name/ecs-task-id. If you don't specify a prefix with this option, then the log stream is named after the container ID that's assigned by the Docker daemon on the container instance. Because it's difficult to trace logs back to the container that sent them with just the Docker container ID (which is only available on the container instance), we recommend that you specify a prefix with this option. For Amazon ECS services, you can use the service name as the prefix. Doing so, you can trace log streams to the service that the container belongs to, the name of the container that sent them, and the ID of the task that the container belongs to. You must specify a stream-prefix for your logs to have your logs appear in the Log pane when using the Amazon ECS console. + awslogs-datetime-format Required: No This option defines a multiline start pattern in Python strftime format. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. One example of a use case for using this format is for parsing output such as a stack dump, which might otherwise be logged in multiple entries. The correct pattern allows it to be captured in a single entry. For more information, see awslogs-datetime-format. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + awslogs-multiline-pattern Required: No This option defines a multiline start pattern that uses a regular expression. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. For more information, see awslogs-multiline-pattern. This option is ignored if awslogs-datetime-format is also configured. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance.
+         *  The following options apply to all supported log drivers.
+         *   + mode Required: No Valid values: non-blocking | blocking This option defines the delivery mode of log messages from the container to the log driver specified using logDriver. The delivery mode you choose affects application availability when the flow of logs from container is interrupted. If you use the blocking mode and the flow of logs is interrupted, calls from container code to write to the stdout and stderr streams will block. The logging thread of the application will block as a result. This may cause the application to become unresponsive and lead to container healthcheck failure. If you use the non-blocking mode, the container's logs are instead stored in an in-memory intermediate buffer configured with the max-buffer-size option. This prevents the application from becoming unresponsive when logs cannot be sent. We recommend using this mode if you want to ensure service availability and are okay with some log loss. For more information, see Preventing log loss with non-blocking mode in the awslogs container log driver. You can set a default mode for all containers in a specific Region by using the defaultLogDriverMode account setting. If you don't specify the mode option or configure the account setting, Amazon ECS will default to the blocking mode. For more information about the account setting, see Default log driver mode in the Amazon Elastic Container Service Developer Guide. + max-buffer-size Required: No Default value: 1m When non-blocking mode is used, the max-buffer-size log option controls the size of the buffer that's used for intermediate message storage. Make sure to specify an adequate buffer size based on your application. When the buffer fills up, further logs cannot be stored. Logs that cannot be stored are lost.
          *  To route logs using the ``splunk`` log router, you need to specify a ``splunk-token`` and a ``splunk-url``.
          *  When you use the ``awsfirelens`` log router to route logs to an AWS Service or AWS Partner Network destination for log storage and analytics, you can set the ``log-driver-buffer-limit`` option to limit the number of events that are buffered in memory, before being sent to the log router container. It can help to resolve potential log loss issue because high throughput might result in memory running out for the buffer inside of Docker.
          *  Other options you can specify when using ``awsfirelens`` to route logs depend on the destination. When you export logs to Amazon Data Firehose, you can specify the AWS Region with ``region`` and a name for the log stream with ``delivery_stream``.
@@ -28616,9 +28756,9 @@ export declare namespace ecs {
         /**
          * The number of I/O operations per second (IOPS). For ``gp3``, ``io1``, and ``io2`` volumes, this represents the number of IOPS that are provisioned for the volume. For ``gp2`` volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting.
          *  The following are the supported values for each volume type.
-         *   +   ``gp3``: 3,000 - 16,000 IOPS
-         *   +   ``io1``: 100 - 64,000 IOPS
-         *   +   ``io2``: 100 - 256,000 IOPS
+         *   +  ``gp3``: 3,000 - 16,000 IOPS
+         *   +  ``io1``: 100 - 64,000 IOPS
+         *   +  ``io2``: 100 - 256,000 IOPS
          *
          *  This parameter is required for ``io1`` and ``io2`` volume types. The default for ``gp3`` volumes is ``3,000 IOPS``. This parameter is not supported for ``st1``, ``sc1``, or ``standard`` volume types.
          *  This parameter maps 1:1 with the ``Iops`` parameter of the [CreateVolume API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html) in the *Amazon EC2 API Reference*.
@@ -28626,7 +28766,7 @@ export declare namespace ecs {
         iops?: number;
         /**
          * The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the ``KmsKeyId`` parameter of the [CreateVolume API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html) in the *Amazon EC2 API Reference*.
-         *    AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails.
+         *   AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails.
          */
         kmsKeyId?: string;
         /**
@@ -28636,10 +28776,10 @@ export declare namespace ecs {
         /**
          * The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the ``Size`` parameter of the [CreateVolume API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html) in the *Amazon EC2 API Reference*.
          *  The following are the supported volume size values for each volume type.
-         *   +   ``gp2`` and ``gp3``: 1-16,384
-         *   +   ``io1`` and ``io2``: 4-16,384
-         *   +   ``st1`` and ``sc1``: 125-16,384
-         *   +   ``standard``: 1-1,024
+         *   +  ``gp2`` and ``gp3``: 1-16,384
+         *   +  ``io1`` and ``io2``: 4-16,384
+         *   +  ``st1`` and ``sc1``: 125-16,384
+         *   +  ``standard``: 1-1,024
          */
         sizeInGiB?: number;
         /**
@@ -28786,7 +28926,7 @@ export declare namespace ecs {
          */
         idleTimeoutSeconds?: number;
         /**
-         * The amount of time waiting for the upstream to respond with a complete response per request. A value of ``0`` can be set to disable ``perRequestTimeout``. ``perRequestTimeout`` can only be set if Service Connect ``appProtocol`` isn't ``TCP``. Only ``idleTimeout`` is allowed for ``TCP`` ``appProtocol``.
+         * The amount of time waiting for the upstream to respond with a complete response per request. A value of ``0`` can be set to disable ``perRequestTimeout``. ``perRequestTimeout`` can only be set if Service Connect ``appProtocol`` isn't ``TCP``. Only ``idleTimeout`` is allowed for ``TCP````appProtocol``.
          */
         perRequestTimeoutSeconds?: number;
     }
@@ -28848,9 +28988,9 @@ export declare namespace ecs {
          *   You can determine the number of CPU units that are available per EC2 instance type by multiplying the vCPUs listed for that instance type on the [Amazon EC2 Instances](https://docs.aws.amazon.com/ec2/instance-types/) detail page by 1,024.
          *   Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount. For example, if you run a single-container task on a single-core instance type with 512 CPU units specified for that container, and that's the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time. However, if you launched another copy of the same task on that container instance, each task is guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float to higher CPU usage if the other container was not using it. If both tasks were 100% active all of the time, they would be limited to 512 CPU units.
          *  On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers. The minimum valid CPU share value that the Linux kernel allows is 2, and the maximum valid CPU share value that the Linux kernel allows is 262144. However, the CPU parameter isn't required, and you can use CPU values below 2 or above 262144 in your container definitions. For CPU values below 2 (including null) or above 262144, the behavior varies based on your Amazon ECS container agent version:
-         *   +   *Agent versions less than or equal to 1.1.0:* Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares.
-         *   +   *Agent versions greater than or equal to 1.2.0:* Null, zero, and CPU values of 1 are passed to Docker as 2.
-         *   +   *Agent versions greater than or equal to 1.84.0:* CPU values greater than 256 vCPU are passed to Docker as 256, which is equivalent to 262144 CPU shares.
+         *   +  *Agent versions less than or equal to 1.1.0:* Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares.
+         *   +  *Agent versions greater than or equal to 1.2.0:* Null, zero, and CPU values of 1 are passed to Docker as 2.
+         *   +  *Agent versions greater than or equal to 1.84.0:* CPU values greater than 256 vCPU are passed to Docker as 256, which is equivalent to 262144 CPU shares.
          *
          *  On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota. Windows containers only have access to the specified amount of CPU that's described in the task definition. A null or zero CPU value is passed to Docker as ``0``, which Windows interprets as 1% of one CPU.
          */
@@ -29104,10 +29244,10 @@ export declare namespace ecs {
     interface TaskDefinitionContainerDependency {
         /**
          * The dependency condition of the container. The following are the available conditions and their behavior:
-         *   +   ``START`` - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.
-         *   +   ``COMPLETE`` - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.
-         *   +   ``SUCCESS`` - This condition is the same as ``COMPLETE``, but it also requires that the container exits with a ``zero`` status. This condition can't be set on an essential container.
-         *   +   ``HEALTHY`` - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.
+         *   +  ``START`` - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.
+         *   +  ``COMPLETE`` - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.
+         *   +  ``SUCCESS`` - This condition is the same as ``COMPLETE``, but it also requires that the container exits with a ``zero`` status. This condition can't be set on an essential container.
+         *   +  ``HEALTHY`` - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.
          */
         condition?: string;
         /**
@@ -29262,9 +29402,9 @@ export declare namespace ecs {
         /**
          * The options to use when configuring the log router. This field is optional and can be used to add additional metadata, such as the task, task definition, cluster, and container instance details to the log event.
          *   If specified, valid option keys are:
-         *   +   ``enable-ecs-log-metadata``, which can be ``true`` or ``false``
-         *   +   ``config-file-type``, which can be ``s3`` or ``file``
-         *   +   ``config-file-value``, which is either an S3 ARN or a file path
+         *   +  ``enable-ecs-log-metadata``, which can be ``true`` or ``false``
+         *   +  ``config-file-type``, which can be ``s3`` or ``file``
+         *   +  ``config-file-value``, which is either an S3 ARN or a file path
          */
         options?: {
             [key: string]: string;
@@ -29440,7 +29580,9 @@ export declare namespace ecs {
         /**
          * The configuration options to send to the log driver.
          *  The options you can specify depend on the log driver. Some of the options you can specify when you use the ``awslogs`` log driver to route logs to Amazon CloudWatch include the following:
-         *   + awslogs-create-group Required: No Specify whether you want the log group to be created automatically. If this option isn't specified, it defaults to false. Your IAM policy must include the logs:CreateLogGroup permission before you attempt to use awslogs-create-group. + awslogs-region Required: Yes Specify the Region that the awslogs log driver is to send your Docker logs to. You can choose to send all of your logs from clusters in different Regions to a single region in CloudWatch Logs. This is so that they're all visible in one location. Otherwise, you can separate them by Region for more granularity. Make sure that the specified log group exists in the Region that you specify with this option. + awslogs-group Required: Yes Make sure to specify a log group that the awslogs log driver sends its log streams to. + awslogs-stream-prefix Required: Yes, when using the Fargate launch type.Optional for the EC2 launch type, required for the Fargate launch type. Use the awslogs-stream-prefix option to associate a log stream with the specified prefix, the container name, and the ID of the Amazon ECS task that the container belongs to. If you specify a prefix with this option, then the log stream takes the format prefix-name/container-name/ecs-task-id. If you don't specify a prefix with this option, then the log stream is named after the container ID that's assigned by the Docker daemon on the container instance. Because it's difficult to trace logs back to the container that sent them with just the Docker container ID (which is only available on the container instance), we recommend that you specify a prefix with this option. For Amazon ECS services, you can use the service name as the prefix. Doing so, you can trace log streams to the service that the container belongs to, the name of the container that sent them, and the ID of the task that the container belongs to. You must specify a stream-prefix for your logs to have your logs appear in the Log pane when using the Amazon ECS console. + awslogs-datetime-format Required: No This option defines a multiline start pattern in Python strftime format. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. One example of a use case for using this format is for parsing output such as a stack dump, which might otherwise be logged in multiple entries. The correct pattern allows it to be captured in a single entry. For more information, see awslogs-datetime-format. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + awslogs-multiline-pattern Required: No This option defines a multiline start pattern that uses a regular expression. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. For more information, see awslogs-multiline-pattern. This option is ignored if awslogs-datetime-format is also configured. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + mode Required: No Valid values: non-blocking | blocking This option defines the delivery mode of log messages from the container to CloudWatch Logs. The delivery mode you choose affects application availability when the flow of logs from container to CloudWatch is interrupted. If you use the blocking mode and the flow of logs to CloudWatch is interrupted, calls from container code to write to the stdout and stderr streams will block. The logging thread of the application will block as a result. This may cause the application to become unresponsive and lead to container healthcheck failure. If you use the non-blocking mode, the container's logs are instead stored in an in-memory intermediate buffer configured with the max-buffer-size option. This prevents the application from becoming unresponsive when logs cannot be sent to CloudWatch. We recommend using this mode if you want to ensure service availability and are okay with some log loss. For more information, see Preventing log loss with non-blocking mode in the awslogs container log driver. + max-buffer-size Required: No Default value: 1m When non-blocking mode is used, the max-buffer-size log option controls the size of the buffer that's used for intermediate message storage. Make sure to specify an adequate buffer size based on your application. When the buffer fills up, further logs cannot be stored. Logs that cannot be stored are lost.
+         *   + awslogs-create-group Required: No Specify whether you want the log group to be created automatically. If this option isn't specified, it defaults to false. Your IAM policy must include the logs:CreateLogGroup permission before you attempt to use awslogs-create-group. + awslogs-region Required: Yes Specify the Region that the awslogs log driver is to send your Docker logs to. You can choose to send all of your logs from clusters in different Regions to a single region in CloudWatch Logs. This is so that they're all visible in one location. Otherwise, you can separate them by Region for more granularity. Make sure that the specified log group exists in the Region that you specify with this option. + awslogs-group Required: Yes Make sure to specify a log group that the awslogs log driver sends its log streams to. + awslogs-stream-prefix Required: Yes, when using Fargate.Optional when using EC2. Use the awslogs-stream-prefix option to associate a log stream with the specified prefix, the container name, and the ID of the Amazon ECS task that the container belongs to. If you specify a prefix with this option, then the log stream takes the format prefix-name/container-name/ecs-task-id. If you don't specify a prefix with this option, then the log stream is named after the container ID that's assigned by the Docker daemon on the container instance. Because it's difficult to trace logs back to the container that sent them with just the Docker container ID (which is only available on the container instance), we recommend that you specify a prefix with this option. For Amazon ECS services, you can use the service name as the prefix. Doing so, you can trace log streams to the service that the container belongs to, the name of the container that sent them, and the ID of the task that the container belongs to. You must specify a stream-prefix for your logs to have your logs appear in the Log pane when using the Amazon ECS console. + awslogs-datetime-format Required: No This option defines a multiline start pattern in Python strftime format. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. One example of a use case for using this format is for parsing output such as a stack dump, which might otherwise be logged in multiple entries. The correct pattern allows it to be captured in a single entry. For more information, see awslogs-datetime-format. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + awslogs-multiline-pattern Required: No This option defines a multiline start pattern that uses a regular expression. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. For more information, see awslogs-multiline-pattern. This option is ignored if awslogs-datetime-format is also configured. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance.
+         *  The following options apply to all supported log drivers.
+         *   + mode Required: No Valid values: non-blocking | blocking This option defines the delivery mode of log messages from the container to the log driver specified using logDriver. The delivery mode you choose affects application availability when the flow of logs from container is interrupted. If you use the blocking mode and the flow of logs is interrupted, calls from container code to write to the stdout and stderr streams will block. The logging thread of the application will block as a result. This may cause the application to become unresponsive and lead to container healthcheck failure. If you use the non-blocking mode, the container's logs are instead stored in an in-memory intermediate buffer configured with the max-buffer-size option. This prevents the application from becoming unresponsive when logs cannot be sent. We recommend using this mode if you want to ensure service availability and are okay with some log loss. For more information, see Preventing log loss with non-blocking mode in the awslogs container log driver. You can set a default mode for all containers in a specific Region by using the defaultLogDriverMode account setting. If you don't specify the mode option or configure the account setting, Amazon ECS will default to the blocking mode. For more information about the account setting, see Default log driver mode in the Amazon Elastic Container Service Developer Guide. + max-buffer-size Required: No Default value: 1m When non-blocking mode is used, the max-buffer-size log option controls the size of the buffer that's used for intermediate message storage. Make sure to specify an adequate buffer size based on your application. When the buffer fills up, further logs cannot be stored. Logs that cannot be stored are lost.
          *  To route logs using the ``splunk`` log router, you need to specify a ``splunk-token`` and a ``splunk-url``.
          *  When you use the ``awsfirelens`` log router to route logs to an AWS Service or AWS Partner Network destination for log storage and analytics, you can set the ``log-driver-buffer-limit`` option to limit the number of events that are buffered in memory, before being sent to the log router container. It can help to resolve potential log loss issue because high throughput might result in memory running out for the buffer inside of Docker.
          *  Other options you can specify when using ``awsfirelens`` to route logs depend on the destination. When you export logs to Amazon Data Firehose, you can specify the AWS Region with ``region`` and a name for the log stream with ``delivery_stream``.
@@ -29497,7 +29639,7 @@ export declare namespace ecs {
         /**
          * The application protocol that's used for the port mapping. This parameter only applies to Service Connect. We recommend that you set this parameter to be consistent with the protocol that your application uses. If you set this parameter, Amazon ECS adds protocol-specific connection handling to the Service Connect proxy. If you set this parameter, Amazon ECS adds protocol-specific telemetry in the Amazon ECS console and CloudWatch.
          *  If you don't set a value for this parameter, then TCP is used. However, Amazon ECS doesn't add protocol-specific telemetry for TCP.
-         *   ``appProtocol`` is immutable in a Service Connect service. Updating this field requires a service deletion and redeployment.
+         *  ``appProtocol`` is immutable in a Service Connect service. Updating this field requires a service deletion and redeployment.
          *  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 [Service Connect](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) in the *Amazon Elastic Container Service Developer Guide*.
          */
         appProtocol?: enums.ecs.TaskDefinitionPortMappingAppProtocol;
@@ -29562,13 +29704,13 @@ export declare namespace ecs {
         containerName: string;
         /**
          * The set of network configuration parameters to provide the Container Network Interface (CNI) plugin, specified as key-value pairs.
-         *   +   ``IgnoredUID`` - (Required) The user ID (UID) of the proxy container as defined by the ``user`` parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If ``IgnoredGID`` is specified, this field can be empty.
-         *   +   ``IgnoredGID`` - (Required) The group ID (GID) of the proxy container as defined by the ``user`` parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If ``IgnoredUID`` is specified, this field can be empty.
-         *   +   ``AppPorts`` - (Required) The list of ports that the application uses. Network traffic to these ports is forwarded to the ``ProxyIngressPort`` and ``ProxyEgressPort``.
-         *   +   ``ProxyIngressPort`` - (Required) Specifies the port that incoming traffic to the ``AppPorts`` is directed to.
-         *   +   ``ProxyEgressPort`` - (Required) Specifies the port that outgoing traffic from the ``AppPorts`` is directed to.
-         *   +   ``EgressIgnoredPorts`` - (Required) The egress traffic going to the specified ports is ignored and not redirected to the ``ProxyEgressPort``. It can be an empty list.
-         *   +   ``EgressIgnoredIPs`` - (Required) The egress traffic going to the specified IP addresses is ignored and not redirected to the ``ProxyEgressPort``. It can be an empty list.
+         *   +  ``IgnoredUID`` - (Required) The user ID (UID) of the proxy container as defined by the ``user`` parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If ``IgnoredGID`` is specified, this field can be empty.
+         *   +  ``IgnoredGID`` - (Required) The group ID (GID) of the proxy container as defined by the ``user`` parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If ``IgnoredUID`` is specified, this field can be empty.
+         *   +  ``AppPorts`` - (Required) The list of ports that the application uses. Network traffic to these ports is forwarded to the ``ProxyIngressPort`` and ``ProxyEgressPort``.
+         *   +  ``ProxyIngressPort`` - (Required) Specifies the port that incoming traffic to the ``AppPorts`` is directed to.
+         *   +  ``ProxyEgressPort`` - (Required) Specifies the port that outgoing traffic from the ``AppPorts`` is directed to.
+         *   +  ``EgressIgnoredPorts`` - (Required) The egress traffic going to the specified ports is ignored and not redirected to the ``ProxyEgressPort``. It can be an empty list.
+         *   +  ``EgressIgnoredIPs`` - (Required) The egress traffic going to the specified IP addresses is ignored and not redirected to the ``ProxyEgressPort``. It can be an empty list.
          */
         proxyConfigurationProperties?: outputs.ecs.TaskDefinitionKeyValuePair[];
         /**
@@ -50406,11 +50548,11 @@ export declare namespace mediapackagev2 {
      */
     interface OriginEndpointForceEndpointErrorConfiguration {
         /**
-         * <p>The failover settings for the endpoint. The options are:</p>
+         * <p>The failover conditions for the endpoint. The options are:</p>
          *          <ul>
          *             <li>
          *                <p>
-         *                   <code>STALE_MANIFEST</code> - The manifest stalled and there a no new segments or parts.</p>
+         *                   <code>STALE_MANIFEST</code> - The manifest stalled and there are no new segments or parts.</p>
          *             </li>
          *             <li>
          *                <p>
@@ -50420,6 +50562,10 @@ export declare namespace mediapackagev2 {
          *                <p>
          *                   <code>MISSING_DRM_KEY</code> - Key rotation is enabled but we're unable to fetch the key for the current key period.</p>
          *             </li>
+         *             <li>
+         *                <p>
+         *                   <code>SLATE_INPUT</code> - The segments which contain slate content are considered to be missing content.</p>
+         *             </li>
          *          </ul>
          */
         endpointErrorConditions?: enums.mediapackagev2.OriginEndpointEndpointErrorCondition[];
@@ -50444,8 +50590,7 @@ export declare namespace mediapackagev2 {
         /**
          * <p>Inserts EXT-X-PROGRAM-DATE-TIME tags in the output manifest at the interval that you specify. If you don't enter an interval,
          *          EXT-X-PROGRAM-DATE-TIME tags aren't included in the manifest.
-         *          The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.
-         *          ID3Timed metadata messages generate every 5 seconds whenever the content is ingested.</p>
+         *          The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.</p>
          *          <p>Irrespective of this parameter, if any ID3Timed metadata is in the HLS input, it is passed through to the HLS output.</p>
          */
         programDateTimeIntervalSeconds?: number;
@@ -50458,6 +50603,11 @@ export declare namespace mediapackagev2 {
          * <p>The egress domain URL for stream delivery from MediaPackage.</p>
          */
         url?: string;
+        /**
+         * <p>When enabled, MediaPackage URL-encodes the query string for API requests for HLS child manifests to comply with Amazon Web Services Signature Version 4 (SigV4) signature signing protocol.
+         *          For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html">Amazon Web Services Signature Version 4 for API requests</a> in <i>Identity and Access Management User Guide</i>.</p>
+         */
+        urlEncodeChildManifest?: boolean;
     }
     /**
      * <p>Retrieve the low-latency HTTP live streaming (HLS) manifest configuration.</p>
@@ -50479,8 +50629,7 @@ export declare namespace mediapackagev2 {
         /**
          * <p>Inserts EXT-X-PROGRAM-DATE-TIME tags in the output manifest at the interval that you specify. If you don't enter an interval,
          *          EXT-X-PROGRAM-DATE-TIME tags aren't included in the manifest.
-         *          The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.
-         *          ID3Timed metadata messages generate every 5 seconds whenever the content is ingested.</p>
+         *          The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.</p>
          *          <p>Irrespective of this parameter, if any ID3Timed metadata is in the HLS input, it is passed through to the HLS output.</p>
          */
         programDateTimeIntervalSeconds?: number;
@@ -50493,6 +50642,11 @@ export declare namespace mediapackagev2 {
          * <p>The egress domain URL for stream delivery from MediaPackage.</p>
          */
         url?: string;
+        /**
+         * <p>When enabled, MediaPackage URL-encodes the query string for API requests for LL-HLS child manifests to comply with Amazon Web Services Signature Version 4 (SigV4) signature signing protocol.
+         *          For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html">Amazon Web Services Signature Version 4 for API requests</a> in <i>Identity and Access Management User Guide</i>.</p>
+         */
+        urlEncodeChildManifest?: boolean;
     }
     /**
      * <p>The SCTE configuration.</p>
@@ -55654,7 +55808,7 @@ export declare namespace qbusiness {
          */
         invocationCondition?: outputs.qbusiness.DataSourceDocumentAttributeCondition;
         /**
-         * The Amazon Resource Name (ARN) of the Lambda function sduring ingestion. For more information, see [Using Lambda functions for Amazon Q Business document enrichment](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/cde-lambda-operations.html) .
+         * The Amazon Resource Name (ARN) of the Lambda function during ingestion. For more information, see [Using Lambda functions for Amazon Q Business document enrichment](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/cde-lambda-operations.html) .
          */
         lambdaArn?: string;
         /**
@@ -96794,7 +96948,7 @@ export declare namespace vpclattice {
     }
     interface ListenerFixedResponse {
         /**
-         * The HTTP response code.
+         * The HTTP response code. Only `404` and `500` status codes are supported.
          */
         statusCode: number;
     }
@@ -96862,7 +97016,7 @@ export declare namespace vpclattice {
     }
     interface RuleFixedResponse {
         /**
-         * The HTTP response code.
+         * The HTTP response code. Only `404` and `500` status codes are supported.
          */
         statusCode: number;
     }