@pulumi/aws-native 1.30.0-alpha.1749274537 → 1.30.0-alpha.1749561139

package/types/input.d.ts

@@ -846,9 +846,9 @@ export declare namespace amplify {
         /**
          * The type of cache configuration to use for an Amplify app.
          *
-         * The `AMPLIFY_MANAGED` cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.
+         * The `AMPLIFY_MANAGED` cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules.
          *
-         * The `AMPLIFY_MANAGED_NO_COOKIES` cache configuration type is the same as `AMPLIFY_MANAGED` , except that it excludes all cookies from the cache key.
+         * The `AMPLIFY_MANAGED_NO_COOKIES` cache configuration type is the same as `AMPLIFY_MANAGED` , except that it excludes all cookies from the cache key. This is the default setting.
          */
         type?: pulumi.Input<enums.amplify.AppCacheConfigType>;
     }
@@ -1909,7 +1909,7 @@ export declare namespace apigateway {
             [key: string]: pulumi.Input<string>;
         }>;
         /**
-         * Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds.
+         * Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds. You can increase the default value to longer than 29 seconds for Regional or private APIs only.
          */
         timeoutInMillis?: pulumi.Input<number>;
         /**
@@ -11364,6 +11364,13 @@ export declare namespace bedrock {
      * Input to a node in a flow
      */
     interface FlowNodeInputArgs {
+        /**
+         * Specifies how input data flows between iterations in a DoWhile loop.
+         *
+         * - `LoopCondition` - Controls whether the loop continues by evaluating condition expressions against the input data. Use this category to define the condition that determines if the loop should continue.
+         * - `ReturnValueToLoopStart` - Defines data to pass back to the start of the loop's next iteration. Use this category for variables that you want to update for each loop iteration.
+         * - `ExitLoop` - Defines the value that's available once the loop ends. Use this category to expose loop results to nodes outside the loop.
+         */
         category?: pulumi.Input<enums.bedrock.FlowNodeInputCategory>;
         /**
          * Expression for a node input in a flow
@@ -23308,6 +23315,28 @@ export declare namespace ec2 {
          */
         cpu?: pulumi.Input<inputs.ec2.Ec2FleetCpuPerformanceFactorRequestArgs>;
     }
+    interface Ec2FleetBlockDeviceMappingArgs {
+        /**
+         * The device name (for example, `/dev/sdh` or `xvdh` ).
+         */
+        deviceName?: pulumi.Input<string>;
+        /**
+         * Parameters used to automatically set up EBS volumes when the instance is launched.
+         */
+        ebs?: pulumi.Input<inputs.ec2.Ec2FleetEbsBlockDeviceArgs>;
+        /**
+         * To omit the device from the block device mapping, specify an empty string. When this property is specified, the device is removed from the block device mapping regardless of the assigned value.
+         */
+        noDevice?: pulumi.Input<string>;
+        /**
+         * The virtual device name ( `ephemeral` N). Instance store volumes are numbered starting from 0. An instance type with 2 available instance store volumes can specify mappings for `ephemeral0` and `ephemeral1` . The number of available instance store volumes depends on the instance type. After you connect to the instance, you must mount the volume.
+         *
+         * NVMe instance store volumes are automatically enumerated and assigned a device name. Including them in your block device mapping has no effect.
+         *
+         * Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
+         */
+        virtualName?: pulumi.Input<string>;
+    }
     interface Ec2FleetCapacityRebalanceArgs {
         /**
          * The replacement strategy to use. Only available for fleets of type `maintain` .
@@ -23346,6 +23375,69 @@ export declare namespace ec2 {
          */
         references?: pulumi.Input<pulumi.Input<inputs.ec2.Ec2FleetPerformanceFactorReferenceRequestArgs>[]>;
     }
+    interface Ec2FleetEbsBlockDeviceArgs {
+        /**
+         * Indicates whether the EBS volume is deleted on instance termination. For more information, see [Preserving Amazon EBS volumes on instance termination](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/terminating-instances.html#preserving-volumes-on-termination) in the *Amazon EC2 User Guide* .
+         */
+        deleteOnTermination?: pulumi.Input<boolean>;
+        /**
+         * Indicates whether the encryption state of an EBS volume is changed while being restored from a backing snapshot. The effect of setting the encryption state to `true` depends on the volume origin (new or from a snapshot), starting encryption state, ownership, and whether encryption by default is enabled. For more information, see [Amazon EBS encryption](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-encryption.html#encryption-parameters) in the *Amazon EBS User Guide* .
+         *
+         * In no case can you remove encryption from an encrypted volume.
+         *
+         * Encrypted volumes can only be attached to instances that support Amazon EBS encryption. For more information, see [Supported instance types](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-encryption-requirements.html#ebs-encryption_supported_instances) .
+         *
+         * This parameter is not returned by `DescribeImageAttribute` .
+         *
+         * For `CreateImage` and `RegisterImage` , whether you can include this parameter, and the allowed values differ depending on the type of block device mapping you are creating.
+         *
+         * - If you are creating a block device mapping for a *new (empty) volume* , you can include this parameter, and specify either `true` for an encrypted volume, or `false` for an unencrypted volume. If you omit this parameter, it defaults to `false` (unencrypted).
+         * - If you are creating a block device mapping from an *existing encrypted or unencrypted snapshot* , you must omit this parameter. If you include this parameter, the request will fail, regardless of the value that you specify.
+         * - If you are creating a block device mapping from an *existing unencrypted volume* , you can include this parameter, but you must specify `false` . If you specify `true` , the request will fail. In this case, we recommend that you omit the parameter.
+         * - If you are creating a block device mapping from an *existing encrypted volume* , you can include this parameter, and specify either `true` or `false` . However, if you specify `false` , the parameter is ignored and the block device mapping is always encrypted. In this case, we recommend that you omit the parameter.
+         */
+        encrypted?: pulumi.Input<boolean>;
+        /**
+         * 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
+         *
+         * For `io2` volumes, you can achieve up to 256,000 IOPS on [instances built on the Nitro System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances) . On other instances, you can achieve performance up to 32,000 IOPS.
+         *
+         * This parameter is required for `io1` and `io2` volumes. The default for `gp3` volumes is 3,000 IOPS.
+         */
+        iops?: pulumi.Input<number>;
+        /**
+         * Identifier (key ID, key alias, key ARN, or alias ARN) of the customer managed KMS key to use for EBS encryption.
+         *
+         * This parameter is only supported on `BlockDeviceMapping` objects called by [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html) , [RequestSpotFleet](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RequestSpotFleet.html) , and [RequestSpotInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RequestSpotInstances.html) .
+         */
+        kmsKeyId?: pulumi.Input<string>;
+        /**
+         * The ID of the snapshot.
+         */
+        snapshotId?: pulumi.Input<string>;
+        /**
+         * The size of the volume, in GiBs. You must specify either a snapshot ID or a volume size. If you specify a snapshot, the default is the snapshot size. You can specify a volume size that is equal to or larger than the snapshot size.
+         *
+         * The following are the supported sizes for each volume type:
+         *
+         * - `gp2` and `gp3` : 1 - 16,384 GiB
+         * - `io1` : 4 - 16,384 GiB
+         * - `io2` : 4 - 65,536 GiB
+         * - `st1` and `sc1` : 125 - 16,384 GiB
+         * - `standard` : 1 - 1024 GiB
+         */
+        volumeSize?: pulumi.Input<number>;
+        /**
+         * The volume type. For more information, see [Amazon EBS volume types](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volume-types.html) in the *Amazon EBS User Guide* .
+         */
+        volumeType?: pulumi.Input<enums.ec2.Ec2FleetEbsBlockDeviceVolumeType>;
+    }
     interface Ec2FleetFleetLaunchTemplateConfigRequestArgs {
         /**
          * The launch template to use. You must specify either the launch template ID or launch template name in the request.
@@ -23363,6 +23455,14 @@ export declare namespace ec2 {
          * The Availability Zone in which to launch the instances.
          */
         availabilityZone?: pulumi.Input<string>;
+        /**
+         * The block device mappings, which define the EBS volumes and instance store volumes to attach to the instance at launch.
+         *
+         * Supported only for fleets of type `instant` .
+         *
+         * For more information, see [Block device mappings for volumes on Amazon EC2 instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html) in the *Amazon EC2 User Guide* .
+         */
+        blockDeviceMappings?: pulumi.Input<pulumi.Input<inputs.ec2.Ec2FleetBlockDeviceMappingArgs>[]>;
         /**
          * The attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with those attributes.
          *
@@ -27882,7 +27982,7 @@ export declare namespace ecs {
          *  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 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.
+         *   + 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. On June 25, 2025, Amazon ECS is changing the default log driver mode from blocking to non-blocking to prioritize task availability over logging. To continue using the blocking mode after this change, do one of the following: Set the mode option in your container definition's logConfiguration as blocking. Set the defaultLogDriverMode account setting to blocking. + 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``.
@@ -51338,6 +51438,16 @@ export declare namespace networkfirewall {
          */
         serverCertificateConfigurations?: pulumi.Input<pulumi.Input<inputs.networkfirewall.TlsInspectionConfigurationServerCertificateConfigurationArgs>[]>;
     }
+    interface VpcEndpointAssociationSubnetMappingArgs {
+        /**
+         * A IPAddressType
+         */
+        ipAddressType?: pulumi.Input<string>;
+        /**
+         * A SubnetId.
+         */
+        subnetId: pulumi.Input<string>;
+    }
 }
 export declare namespace networkmanager {
     /**

package/types/output.d.ts

@@ -723,9 +723,9 @@ export declare namespace amplify {
         /**
          * The type of cache configuration to use for an Amplify app.
          *
-         * The `AMPLIFY_MANAGED` cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.
+         * The `AMPLIFY_MANAGED` cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules.
          *
-         * The `AMPLIFY_MANAGED_NO_COOKIES` cache configuration type is the same as `AMPLIFY_MANAGED` , except that it excludes all cookies from the cache key.
+         * The `AMPLIFY_MANAGED_NO_COOKIES` cache configuration type is the same as `AMPLIFY_MANAGED` , except that it excludes all cookies from the cache key. This is the default setting.
          */
         type?: enums.amplify.AppCacheConfigType;
     }
@@ -1806,7 +1806,7 @@ export declare namespace apigateway {
             [key: string]: string;
         };
         /**
-         * Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds.
+         * Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds. You can increase the default value to longer than 29 seconds for Regional or private APIs only.
          */
         timeoutInMillis?: number;
         /**
@@ -11300,6 +11300,13 @@ export declare namespace bedrock {
      * Input to a node in a flow
      */
     interface FlowNodeInput {
+        /**
+         * Specifies how input data flows between iterations in a DoWhile loop.
+         *
+         * - `LoopCondition` - Controls whether the loop continues by evaluating condition expressions against the input data. Use this category to define the condition that determines if the loop should continue.
+         * - `ReturnValueToLoopStart` - Defines data to pass back to the start of the loop's next iteration. Use this category for variables that you want to update for each loop iteration.
+         * - `ExitLoop` - Defines the value that's available once the loop ends. Use this category to expose loop results to nodes outside the loop.
+         */
         category?: enums.bedrock.FlowNodeInputCategory;
         /**
          * Expression for a node input in a flow
@@ -24354,6 +24361,28 @@ export declare namespace ec2 {
          */
         cpu?: outputs.ec2.Ec2FleetCpuPerformanceFactorRequest;
     }
+    interface Ec2FleetBlockDeviceMapping {
+        /**
+         * The device name (for example, `/dev/sdh` or `xvdh` ).
+         */
+        deviceName?: string;
+        /**
+         * Parameters used to automatically set up EBS volumes when the instance is launched.
+         */
+        ebs?: outputs.ec2.Ec2FleetEbsBlockDevice;
+        /**
+         * To omit the device from the block device mapping, specify an empty string. When this property is specified, the device is removed from the block device mapping regardless of the assigned value.
+         */
+        noDevice?: string;
+        /**
+         * The virtual device name ( `ephemeral` N). Instance store volumes are numbered starting from 0. An instance type with 2 available instance store volumes can specify mappings for `ephemeral0` and `ephemeral1` . The number of available instance store volumes depends on the instance type. After you connect to the instance, you must mount the volume.
+         *
+         * NVMe instance store volumes are automatically enumerated and assigned a device name. Including them in your block device mapping has no effect.
+         *
+         * Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
+         */
+        virtualName?: string;
+    }
     interface Ec2FleetCapacityRebalance {
         /**
          * The replacement strategy to use. Only available for fleets of type `maintain` .
@@ -24392,6 +24421,69 @@ export declare namespace ec2 {
          */
         references?: outputs.ec2.Ec2FleetPerformanceFactorReferenceRequest[];
     }
+    interface Ec2FleetEbsBlockDevice {
+        /**
+         * Indicates whether the EBS volume is deleted on instance termination. For more information, see [Preserving Amazon EBS volumes on instance termination](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/terminating-instances.html#preserving-volumes-on-termination) in the *Amazon EC2 User Guide* .
+         */
+        deleteOnTermination?: boolean;
+        /**
+         * Indicates whether the encryption state of an EBS volume is changed while being restored from a backing snapshot. The effect of setting the encryption state to `true` depends on the volume origin (new or from a snapshot), starting encryption state, ownership, and whether encryption by default is enabled. For more information, see [Amazon EBS encryption](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-encryption.html#encryption-parameters) in the *Amazon EBS User Guide* .
+         *
+         * In no case can you remove encryption from an encrypted volume.
+         *
+         * Encrypted volumes can only be attached to instances that support Amazon EBS encryption. For more information, see [Supported instance types](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-encryption-requirements.html#ebs-encryption_supported_instances) .
+         *
+         * This parameter is not returned by `DescribeImageAttribute` .
+         *
+         * For `CreateImage` and `RegisterImage` , whether you can include this parameter, and the allowed values differ depending on the type of block device mapping you are creating.
+         *
+         * - If you are creating a block device mapping for a *new (empty) volume* , you can include this parameter, and specify either `true` for an encrypted volume, or `false` for an unencrypted volume. If you omit this parameter, it defaults to `false` (unencrypted).
+         * - If you are creating a block device mapping from an *existing encrypted or unencrypted snapshot* , you must omit this parameter. If you include this parameter, the request will fail, regardless of the value that you specify.
+         * - If you are creating a block device mapping from an *existing unencrypted volume* , you can include this parameter, but you must specify `false` . If you specify `true` , the request will fail. In this case, we recommend that you omit the parameter.
+         * - If you are creating a block device mapping from an *existing encrypted volume* , you can include this parameter, and specify either `true` or `false` . However, if you specify `false` , the parameter is ignored and the block device mapping is always encrypted. In this case, we recommend that you omit the parameter.
+         */
+        encrypted?: boolean;
+        /**
+         * 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
+         *
+         * For `io2` volumes, you can achieve up to 256,000 IOPS on [instances built on the Nitro System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances) . On other instances, you can achieve performance up to 32,000 IOPS.
+         *
+         * This parameter is required for `io1` and `io2` volumes. The default for `gp3` volumes is 3,000 IOPS.
+         */
+        iops?: number;
+        /**
+         * Identifier (key ID, key alias, key ARN, or alias ARN) of the customer managed KMS key to use for EBS encryption.
+         *
+         * This parameter is only supported on `BlockDeviceMapping` objects called by [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html) , [RequestSpotFleet](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RequestSpotFleet.html) , and [RequestSpotInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RequestSpotInstances.html) .
+         */
+        kmsKeyId?: string;
+        /**
+         * The ID of the snapshot.
+         */
+        snapshotId?: string;
+        /**
+         * The size of the volume, in GiBs. You must specify either a snapshot ID or a volume size. If you specify a snapshot, the default is the snapshot size. You can specify a volume size that is equal to or larger than the snapshot size.
+         *
+         * The following are the supported sizes for each volume type:
+         *
+         * - `gp2` and `gp3` : 1 - 16,384 GiB
+         * - `io1` : 4 - 16,384 GiB
+         * - `io2` : 4 - 65,536 GiB
+         * - `st1` and `sc1` : 125 - 16,384 GiB
+         * - `standard` : 1 - 1024 GiB
+         */
+        volumeSize?: number;
+        /**
+         * The volume type. For more information, see [Amazon EBS volume types](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volume-types.html) in the *Amazon EBS User Guide* .
+         */
+        volumeType?: enums.ec2.Ec2FleetEbsBlockDeviceVolumeType;
+    }
     interface Ec2FleetFleetLaunchTemplateConfigRequest {
         /**
          * The launch template to use. You must specify either the launch template ID or launch template name in the request.
@@ -24409,6 +24501,14 @@ export declare namespace ec2 {
          * The Availability Zone in which to launch the instances.
          */
         availabilityZone?: string;
+        /**
+         * The block device mappings, which define the EBS volumes and instance store volumes to attach to the instance at launch.
+         *
+         * Supported only for fleets of type `instant` .
+         *
+         * For more information, see [Block device mappings for volumes on Amazon EC2 instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html) in the *Amazon EC2 User Guide* .
+         */
+        blockDeviceMappings?: outputs.ec2.Ec2FleetBlockDeviceMapping[];
         /**
          * The attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with those attributes.
          *
@@ -29469,7 +29569,7 @@ export declare namespace ecs {
          *  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 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.
+         *   + 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. On June 25, 2025, Amazon ECS is changing the default log driver mode from blocking to non-blocking to prioritize task availability over logging. To continue using the blocking mode after this change, do one of the following: Set the mode option in your container definition's logConfiguration as blocking. Set the defaultLogDriverMode account setting to blocking. + 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``.
@@ -53126,6 +53226,16 @@ export declare namespace networkfirewall {
          */
         serverCertificateConfigurations?: outputs.networkfirewall.TlsInspectionConfigurationServerCertificateConfiguration[];
     }
+    interface VpcEndpointAssociationSubnetMapping {
+        /**
+         * A IPAddressType
+         */
+        ipAddressType?: string;
+        /**
+         * A SubnetId.
+         */
+        subnetId: string;
+    }
 }
 export declare namespace networkmanager {
     /**

package/types/output.js.map

@@ -1 +1 @@
-{"version":3,"file":"output.js","sourceRoot":"","sources":["../../types/output.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAivmBjF,IAAiB,MAAM,CAgHtB;AAhHD,WAAiB,MAAM;IAoDnB;;OAEG;IACH,SAAgB,yBAAyB,CAAC,GAAe;;QACrD,uCACO,GAAG,KACN,qBAAqB,EAAE,MAAA,CAAC,GAAG,CAAC,qBAAqB,CAAC,mCAAI,CAAC,IACzD;IACN,CAAC;IALe,gCAAyB,4BAKxC,CAAA;AAoDL,CAAC,EAhHgB,MAAM,GAAN,cAAM,KAAN,cAAM,QAgHtB"}
+{"version":3,"file":"output.js","sourceRoot":"","sources":["../../types/output.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAwvmBjF,IAAiB,MAAM,CAgHtB;AAhHD,WAAiB,MAAM;IAoDnB;;OAEG;IACH,SAAgB,yBAAyB,CAAC,GAAe;;QACrD,uCACO,GAAG,KACN,qBAAqB,EAAE,MAAA,CAAC,GAAG,CAAC,qBAAqB,CAAC,mCAAI,CAAC,IACzD;IACN,CAAC;IALe,gCAAyB,4BAKxC,CAAA;AAoDL,CAAC,EAhHgB,MAAM,GAAN,cAAM,KAAN,cAAM,QAgHtB"}