@pulumi/aws-native 1.33.0-alpha.1756792567 → 1.33.0-alpha.1756877694

package/types/input.d.ts

@@ -4192,7 +4192,7 @@ export declare namespace applicationautoscaling {
      *
      *  For an example of how creating new metrics can be useful, see [Scaling based on Amazon SQS](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-using-sqs-queue.html) in the *Amazon EC2 Auto Scaling User Guide*. This topic mentions Auto Scaling groups, but the same scenario for Amazon SQS can apply to the target tracking scaling policies that you create for a Spot Fleet by using Application Auto Scaling.
      *  For more information about the CloudWatch terminology below, see [Amazon CloudWatch concepts](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.html).
-     *   ``CustomizedMetricSpecification`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy TargetTrackingScalingPolicyConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-targettrackingscalingpolicyconfiguration.html) property type.
+     *  ``CustomizedMetricSpecification`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy TargetTrackingScalingPolicyConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-targettrackingscalingpolicyconfiguration.html) property type.
      */
     interface ScalingPolicyCustomizedMetricSpecificationArgs {
         /**
@@ -4236,7 +4236,7 @@ export declare namespace applicationautoscaling {
     }
     /**
      * Contains predefined metric specification information for a target tracking scaling policy for Application Auto Scaling.
-     *   ``PredefinedMetricSpecification`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy TargetTrackingScalingPolicyConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-targettrackingscalingpolicyconfiguration.html) property type.
+     *  ``PredefinedMetricSpecification`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy TargetTrackingScalingPolicyConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-targettrackingscalingpolicyconfiguration.html) property type.
      */
     interface ScalingPolicyPredefinedMetricSpecificationArgs {
         /**
@@ -4246,7 +4246,7 @@ export declare namespace applicationautoscaling {
         /**
          * Identifies the resource associated with the metric type. You can't specify a resource label unless the metric type is ``ALBRequestCountPerTarget`` and there is a target group attached to the Spot Fleet or ECS service.
          *  You create the resource label by appending the final portion of the load balancer ARN and the final portion of the target group ARN into a single value, separated by a forward slash (/). The format of the resource label is:
-         *   ``app/my-alb/778d41231b141a0f/targetgroup/my-alb-target-group/943f017f100becff``.
+         *  ``app/my-alb/778d41231b141a0f/targetgroup/my-alb-target-group/943f017f100becff``.
          *  Where:
          *   +  app/<load-balancer-name>/<load-balancer-id> is the final portion of the load balancer ARN
          *   +  targetgroup/<target-group-name>/<target-group-id> is the final portion of the target group ARN.
@@ -4391,7 +4391,7 @@ export declare namespace applicationautoscaling {
         unit?: pulumi.Input<string>;
     }
     /**
-     * Represents a predictive scaling policy configuration.
+     * Represents a predictive scaling policy configuration. Predictive scaling is supported on Amazon ECS services.
      */
     interface ScalingPolicyPredictiveScalingPolicyConfigurationArgs {
         /**
@@ -4421,6 +4421,16 @@ export declare namespace applicationautoscaling {
     /**
      * Describes a load metric for a predictive scaling policy.
      *  When returned in the output of ``DescribePolicies``, it indicates that a predictive scaling policy uses individually specified load and scaling metrics instead of a metric pair.
+     *  The following predefined metrics are available for predictive scaling:
+     *   +   ``ECSServiceAverageCPUUtilization``
+     *   +   ``ECSServiceAverageMemoryUtilization``
+     *   +   ``ECSServiceCPUUtilization``
+     *   +   ``ECSServiceMemoryUtilization``
+     *   +   ``ECSServiceTotalCPUUtilization``
+     *   +   ``ECSServiceTotalMemoryUtilization``
+     *   +   ``ALBRequestCount``
+     *   +   ``ALBRequestCountPerTarget``
+     *   +   ``TotalALBRequestCount``
      */
     interface ScalingPolicyPredictiveScalingPredefinedLoadMetricArgs {
         /**
@@ -4434,6 +4444,16 @@ export declare namespace applicationautoscaling {
     }
     /**
      * Represents a metric pair for a predictive scaling policy.
+     *  The following predefined metrics are available for predictive scaling:
+     *   +   ``ECSServiceAverageCPUUtilization``
+     *   +   ``ECSServiceAverageMemoryUtilization``
+     *   +   ``ECSServiceCPUUtilization``
+     *   +   ``ECSServiceMemoryUtilization``
+     *   +   ``ECSServiceTotalCPUUtilization``
+     *   +   ``ECSServiceTotalMemoryUtilization``
+     *   +   ``ALBRequestCount``
+     *   +   ``ALBRequestCountPerTarget``
+     *   +   ``TotalALBRequestCount``
      */
     interface ScalingPolicyPredictiveScalingPredefinedMetricPairArgs {
         /**
@@ -4448,6 +4468,16 @@ export declare namespace applicationautoscaling {
     /**
      * Describes a scaling metric for a predictive scaling policy.
      *  When returned in the output of ``DescribePolicies``, it indicates that a predictive scaling policy uses individually specified load and scaling metrics instead of a metric pair.
+     *  The following predefined metrics are available for predictive scaling:
+     *   +   ``ECSServiceAverageCPUUtilization``
+     *   +   ``ECSServiceAverageMemoryUtilization``
+     *   +   ``ECSServiceCPUUtilization``
+     *   +   ``ECSServiceMemoryUtilization``
+     *   +   ``ECSServiceTotalCPUUtilization``
+     *   +   ``ECSServiceTotalMemoryUtilization``
+     *   +   ``ALBRequestCount``
+     *   +   ``ALBRequestCountPerTarget``
+     *   +   ``TotalALBRequestCount``
      */
     interface ScalingPolicyPredictiveScalingPredefinedScalingMetricArgs {
         /**
@@ -4534,7 +4564,7 @@ export declare namespace applicationautoscaling {
      * The metric data to return. Also defines whether this call is returning data for one metric only, or whether it is performing a math expression on the values of returned metric statistics to create a new time series. A time series is a series of data points, each of which is associated with a timestamp.
      *  You can call for a single metric or perform math expressions on multiple metrics. Any expressions used in a metric specification must eventually return a single time series.
      *  For more information and examples, see [Create a target tracking scaling policy for Application Auto Scaling using metric math](https://docs.aws.amazon.com/autoscaling/application/userguide/application-auto-scaling-target-tracking-metric-math.html) in the *Application Auto Scaling User Guide*.
-     *   ``TargetTrackingMetricDataQuery`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy CustomizedMetricSpecification](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-customizedmetricspecification.html) property type.
+     *  ``TargetTrackingMetricDataQuery`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy CustomizedMetricSpecification](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-customizedmetricspecification.html) property type.
      */
     interface ScalingPolicyTargetTrackingMetricDataQueryArgs {
         /**
@@ -4577,7 +4607,7 @@ export declare namespace applicationautoscaling {
     }
     /**
      * This structure defines the CloudWatch metric to return, along with the statistic and unit.
-     *   ``TargetTrackingMetricStat`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy TargetTrackingMetricDataQuery](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-targettrackingmetricdataquery.html) property type.
+     *  ``TargetTrackingMetricStat`` is a property of the [AWS::ApplicationAutoScaling::ScalingPolicy TargetTrackingMetricDataQuery](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalingpolicy-targettrackingmetricdataquery.html) property type.
      *  For more information about the CloudWatch terminology below, see [Amazon CloudWatch concepts](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.html) in the *Amazon CloudWatch User Guide*.
      */
     interface ScalingPolicyTargetTrackingMetricStatArgs {
@@ -8166,7 +8196,15 @@ export declare namespace b2bi {
         wrapBy?: pulumi.Input<enums.b2bi.PartnershipWrapFormat>;
     }
     interface PartnershipX12AcknowledgmentOptionsArgs {
+        /**
+         * Specifies whether functional acknowledgments (997/999) should be generated for incoming X12 transactions. Valid values are `DO_NOT_GENERATE` , `GENERATE_ALL_SEGMENTS` and `GENERATE_WITHOUT_TRANSACTION_SET_RESPONSE_LOOP` .
+         *
+         * If you choose `GENERATE_WITHOUT_TRANSACTION_SET_RESPONSE_LOOP` , AWS B2B Data Interchange skips the AK2_Loop when generating an acknowledgment document.
+         */
         functionalAcknowledgment: pulumi.Input<enums.b2bi.PartnershipX12FunctionalAcknowledgment>;
+        /**
+         * Specifies whether technical acknowledgments (TA1) should be generated for incoming X12 interchanges. Valid values are `DO_NOT_GENERATE` and `GENERATE_ALL_SEGMENTS` and.
+         */
         technicalAcknowledgment: pulumi.Input<enums.b2bi.PartnershipX12TechnicalAcknowledgment>;
     }
     interface PartnershipX12ControlNumbersArgs {
@@ -8212,6 +8250,9 @@ export declare namespace b2bi {
         validateEdi?: pulumi.Input<boolean>;
     }
     interface TransformerAdvancedOptionsArgs {
+        /**
+         * A structure that contains X12-specific advanced options, such as split options for processing X12 EDI files.
+         */
         x12?: pulumi.Input<inputs.b2bi.TransformerX12AdvancedOptionsArgs>;
     }
     interface TransformerEdiTypePropertiesArgs {
@@ -8221,29 +8262,68 @@ export declare namespace b2bi {
         x12: pulumi.Input<inputs.b2bi.TransformerX12DetailsArgs>;
     }
     interface TransformerInputConversionArgs {
+        /**
+         * Specifies advanced options for the input conversion process. These options provide additional control over how EDI files are processed during transformation.
+         */
         advancedOptions?: pulumi.Input<inputs.b2bi.TransformerAdvancedOptionsArgs>;
+        /**
+         * A structure that contains the formatting options for an inbound transformer.
+         */
         formatOptions?: pulumi.Input<inputs.b2bi.TransformerFormatOptionsPropertiesArgs>;
+        /**
+         * The format for the transformer input: currently on `X12` is supported.
+         */
         fromFormat: pulumi.Input<enums.b2bi.TransformerFromFormat>;
     }
     interface TransformerMappingArgs {
+        /**
+         * A string that represents the mapping template, in the transformation language specified in `templateLanguage` .
+         */
         template?: pulumi.Input<string>;
+        /**
+         * The transformation language for the template, either XSLT or JSONATA.
+         */
         templateLanguage: pulumi.Input<enums.b2bi.TransformerMappingTemplateLanguage>;
     }
     interface TransformerOutputConversionArgs {
         advancedOptions?: pulumi.Input<inputs.b2bi.TransformerAdvancedOptionsArgs>;
+        /**
+         * A structure that contains the X12 transaction set and version for the transformer output.
+         */
         formatOptions?: pulumi.Input<inputs.b2bi.TransformerFormatOptionsPropertiesArgs>;
+        /**
+         * The format for the output from an outbound transformer: only X12 is currently supported.
+         */
         toFormat: pulumi.Input<enums.b2bi.TransformerToFormat>;
     }
     interface TransformerSampleDocumentKeysArgs {
+        /**
+         * An array of keys for your input sample documents.
+         */
         input?: pulumi.Input<string>;
+        /**
+         * An array of keys for your output sample documents.
+         */
         output?: pulumi.Input<string>;
     }
     interface TransformerSampleDocumentsArgs {
+        /**
+         * Contains the Amazon S3 bucket that is used to hold your sample documents.
+         */
         bucketName: pulumi.Input<string>;
+        /**
+         * Contains an array of the Amazon S3 keys used to identify the location for your sample documents.
+         */
         keys: pulumi.Input<pulumi.Input<inputs.b2bi.TransformerSampleDocumentKeysArgs>[]>;
     }
     interface TransformerX12AdvancedOptionsArgs {
+        /**
+         * Specifies options for splitting X12 EDI files. These options control how large X12 files are divided into smaller, more manageable units.
+         */
         splitOptions?: pulumi.Input<inputs.b2bi.TransformerX12SplitOptionsArgs>;
+        /**
+         * Specifies validation options for X12 EDI processing. These options control how validation rules are applied during EDI document processing, including custom validation rules for element length constraints, code list validations, and element requirement checks.
+         */
         validationOptions?: pulumi.Input<inputs.b2bi.TransformerX12ValidationOptionsArgs>;
     }
     interface TransformerX12CodeListValidationRuleArgs {
@@ -8265,9 +8345,15 @@ export declare namespace b2bi {
         requirement: pulumi.Input<enums.b2bi.TransformerElementRequirement>;
     }
     interface TransformerX12SplitOptionsArgs {
+        /**
+         * Specifies the method used to split X12 EDI files. Valid values include `TRANSACTION` (split by individual transaction sets), or `NONE` (no splitting).
+         */
         splitBy?: pulumi.Input<enums.b2bi.TransformerX12SplitBy>;
     }
     interface TransformerX12ValidationOptionsArgs {
+        /**
+         * Specifies a list of validation rules to apply during EDI document processing. These rules can include code list modifications, element length constraints, and element requirement changes.
+         */
         validationRules?: pulumi.Input<pulumi.Input<inputs.b2bi.TransformerX12ValidationRule0PropertiesArgs | inputs.b2bi.TransformerX12ValidationRule1PropertiesArgs | inputs.b2bi.TransformerX12ValidationRule2PropertiesArgs>[]>;
     }
     interface TransformerX12ValidationRule0PropertiesArgs {
@@ -8855,6 +8941,9 @@ export declare namespace batch {
          * - **ECS_AL2023** - [Amazon Linux 2023](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) : AWS Batch supports Amazon Linux 2023.
          *
          * > Amazon Linux 2023 does not support `A1` instances.
+         * - **ECS_AL2023_NVIDIA** - [Amazon Linux 2023 (GPU)](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#gpuami) : For all GPU instance families and can be used for all non AWS Graviton-based instance types.
+         *
+         * > ECS_AL2023_NVIDIA doesn't support `p3` and `g3` instance types.
          * - **ECS_AL1** - [Amazon Linux](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#alami) . Amazon Linux has reached the end-of-life of standard support. For more information, see [Amazon Linux AMI](https://docs.aws.amazon.com/amazon-linux-ami/) .
          * - **EKS** - If the `imageIdOverride` parameter isn't specified, then a recent [Amazon EKS-optimized Amazon Linux AMI](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html) ( `EKS_AL2` ) is used. If a new image type is specified in an update, but neither an `imageId` nor a `imageIdOverride` parameter is specified, then the latest Amazon EKS optimized AMI for that image type that AWS Batch supports is used.
          *
@@ -9605,7 +9694,7 @@ export declare namespace batch {
         /**
          * The log driver to use for the container. The valid values that are listed for this parameter are log drivers that the Amazon ECS container agent can communicate with by default.
          *
-         * The supported log drivers are `awslogs` , `fluentd` , `gelf` , `json-file` , `journald` , `logentries` , `syslog` , and `splunk` .
+         * The supported log drivers are `awsfirelens` , `awslogs` , `fluentd` , `gelf` , `json-file` , `journald` , `logentries` , `syslog` , and `splunk` .
          *
          * > Jobs that are running on Fargate resources are restricted to the `awslogs` and `splunk` log drivers.
          *
@@ -10567,6 +10656,76 @@ export declare namespace bedrock {
          */
         copyFrom: pulumi.Input<string>;
     }
+    interface AutomatedReasoningPolicyPolicyDefinitionArgs {
+        /**
+         * The rules definition block of an AutomatedReasoningPolicyDefinition.
+         */
+        rules?: pulumi.Input<pulumi.Input<inputs.bedrock.AutomatedReasoningPolicyPolicyDefinitionRuleArgs>[]>;
+        /**
+         * The types definition block of an AutomatedReasoningPolicyDefinition.
+         */
+        types?: pulumi.Input<pulumi.Input<inputs.bedrock.AutomatedReasoningPolicyPolicyDefinitionTypeArgs>[]>;
+        /**
+         * The variables definition block of an AutomatedReasoningPolicyDefinition.
+         */
+        variables?: pulumi.Input<pulumi.Input<inputs.bedrock.AutomatedReasoningPolicyPolicyDefinitionVariableArgs>[]>;
+        /**
+         * The policy format version.
+         */
+        version?: pulumi.Input<string>;
+    }
+    interface AutomatedReasoningPolicyPolicyDefinitionRuleArgs {
+        /**
+         * An alternate expression for this rule
+         */
+        alternateExpression?: pulumi.Input<string>;
+        /**
+         * The SMT expression for this rule
+         */
+        expression: pulumi.Input<string>;
+        /**
+         * A unique id within the PolicyDefinition
+         */
+        id: pulumi.Input<string>;
+    }
+    interface AutomatedReasoningPolicyPolicyDefinitionTypeArgs {
+        /**
+         * A natural language description of this type.
+         */
+        description?: pulumi.Input<string>;
+        /**
+         * A name for this type.
+         */
+        name: pulumi.Input<string>;
+        /**
+         * A list of valid values for this type.
+         */
+        values: pulumi.Input<pulumi.Input<inputs.bedrock.AutomatedReasoningPolicyPolicyDefinitionTypeValueArgs>[]>;
+    }
+    interface AutomatedReasoningPolicyPolicyDefinitionTypeValueArgs {
+        /**
+         * A natural language description of the type's value.
+         */
+        description?: pulumi.Input<string>;
+        /**
+         * The value of the type value.
+         */
+        value: pulumi.Input<string>;
+    }
+    interface AutomatedReasoningPolicyPolicyDefinitionVariableArgs {
+        /**
+         * A natural language description of this variable.
+         */
+        description: pulumi.Input<string>;
+        /**
+         * A name from this variable.
+         */
+        name: pulumi.Input<string>;
+        /**
+         * A type for this variable.
+         */
+        type: pulumi.Input<string>;
+    }
     interface DataAutomationProjectAudioExtractionCategoryArgs {
         /**
          * Whether generating categorical data from audio is enabled.
@@ -18069,7 +18228,7 @@ export declare namespace cognito {
          */
         noActionEmail?: pulumi.Input<inputs.cognito.UserPoolRiskConfigurationAttachmentNotifyEmailTypeArgs>;
         /**
-         * The reply-to email address of an email template.
+         * The reply-to email address of an email template. Can be an email address in the format `admin@example.com` or `Administrator <admin@example.com>` .
          */
         replyTo?: pulumi.Input<string>;
         /**
@@ -24347,7 +24506,7 @@ export declare namespace ec2 {
     }
     interface Ec2FleetBlockDeviceMappingArgs {
         /**
-         * The device name (for example, `/dev/sdh` or `xvdh` ).
+         * The device name. For available device names, see [Device names for volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html) .
          */
         deviceName?: pulumi.Input<string>;
         /**
@@ -24914,13 +25073,15 @@ export declare namespace ec2 {
         /**
          * The Availability Zone of the instance.
          *
-         * Either `AvailabilityZone` or `AvailabilityZoneId` can be specified, but not both. If neither is specified, Amazon EC2 automatically selects an Availability Zone based on the load balancing criteria for the Region.
+         * On input, you can specify `AvailabilityZone` or `AvailabilityZoneId` , but not both. If you specify neither one, Amazon EC2 automatically selects an Availability Zone for you.
          *
          * This parameter is not supported for [CreateFleet](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateFleet) .
          */
         availabilityZone?: pulumi.Input<string>;
         /**
-         * The name of the placement group that the instance is in. If you specify `GroupName` , you can't specify `GroupId` .
+         * The name of the placement group that the instance is in.
+         *
+         * On input, you can specify `GroupId` or `GroupName` , but not both.
          */
         groupName?: pulumi.Input<string>;
         /**
@@ -24932,7 +25093,7 @@ export declare namespace ec2 {
         /**
          * The ARN of the host resource group in which to launch the instances.
          *
-         * If you specify this parameter, either omit the *Tenancy* parameter or set it to `host` .
+         * On input, if you specify this parameter, either omit the *Tenancy* parameter or set it to `host` .
          *
          * This parameter is not supported for [CreateFleet](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateFleet) .
          */
@@ -26882,7 +27043,7 @@ export declare namespace ec2 {
     }
     interface SpotFleetBlockDeviceMappingArgs {
         /**
-         * The device name (for example, `/dev/sdh` or `xvdh` ).
+         * The device name. For available device names, see [Device names for volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html) .
          */
         deviceName: pulumi.Input<string>;
         /**
@@ -28553,7 +28714,12 @@ export declare namespace ecs {
      */
     interface ClusterCapacityProviderStrategyItemArgs {
         /**
-         * The *base* value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a *base* defined. If no value is specified, the default value of ``0`` is used.
+         * The *base* value designates how many tasks, at a minimum, to run on the specified capacity provider for each service. Only one capacity provider in a capacity provider strategy can have a *base* defined. If no value is specified, the default value of ``0`` is used.
+         *  Base value characteristics:
+         *   +  Only one capacity provider in a strategy can have a base defined
+         *   +  Default value is ``0`` if not specified
+         *   +  Valid range: 0 to 100,000
+         *   +  Base requirements are satisfied first before weight distribution
          */
         base?: pulumi.Input<number>;
         /**
@@ -28563,7 +28729,20 @@ export declare namespace ecs {
         /**
          * The *weight* value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The ``weight`` value is taken into consideration after the ``base`` value, if defined, is satisfied.
          *  If no ``weight`` value is specified, the default value of ``0`` is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of ``0`` can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of ``0``, any ``RunTask`` or ``CreateService`` actions using the capacity provider strategy will fail.
-         *  An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of ``1``, then when the ``base`` is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of ``1`` for *capacityProviderA* and a weight of ``4`` for *capacityProviderB*, then for every one task that's run using *capacityProviderA*, four tasks would use *capacityProviderB*.
+         *  Weight value characteristics:
+         *   +  Weight is considered after the base value is satisfied
+         *   +  Default value is ``0`` if not specified
+         *   +  Valid range: 0 to 1,000
+         *   +  At least one capacity provider must have a weight greater than zero
+         *   +  Capacity providers with weight of ``0`` cannot place tasks
+         *
+         *  Task distribution logic:
+         *   1.  Base satisfaction: The minimum number of tasks specified by the base value are placed on that capacity provider
+         *   1.  Weight distribution: After base requirements are met, additional tasks are distributed according to weight ratios
+         *
+         *  Examples:
+         *  Equal Distribution: Two capacity providers both with weight ``1`` will split tasks evenly after base requirements are met.
+         *  Weighted Distribution: If capacityProviderA has weight ``1`` and capacityProviderB has weight ``4``, then for every 1 task on A, 4 tasks will run on B.
          */
         weight?: pulumi.Input<number>;
     }
@@ -29072,6 +29251,16 @@ export declare namespace ecs {
          */
         tags?: pulumi.Input<pulumi.Input<inputs.ecs.ServiceTagArgs>[]>;
     }
+    interface ServiceForceNewDeploymentArgs {
+        /**
+         * Determines whether to force a new deployment of the service. By default, deployments aren't forced. You can use this option to start a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination ( `my_image:latest` ) or to roll Fargate tasks onto a newer platform version.
+         */
+        enableForceNewDeployment: pulumi.Input<boolean>;
+        /**
+         * When you change the `ForceNewDeploymentNonce` value in your template, it signals Amazon ECS to start a new deployment even though no other service parameters have changed. The value must be a unique, time- varying value like a timestamp, random string, or sequence number. Use this property when you want to ensure your tasks pick up the latest version of a Docker image that uses the same tag but has been updated in the registry.
+         */
+        forceNewDeploymentNonce?: pulumi.Input<string>;
+    }
     /**
      * The ``LoadBalancer`` property specifies details on a load balancer that is used with a service.
      *  If the service is using the ``CODE_DEPLOY`` deployment controller, the service is required to use either an Application Load Balancer or Network Load Balancer. When you are creating an ACDlong deployment group, you specify two target groups (referred to as a ``targetGroupPair``). Each target group binds to a separate task set in the deployment. The load balancer can also have up to two listeners, a required listener for production traffic and an optional listener that allows you to test new revisions of the service before routing production traffic to it.
@@ -29988,7 +30177,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 non-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 changed 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.
+         *   + 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 non-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 changed 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: 10m 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``.
@@ -35388,7 +35577,7 @@ export declare namespace gameliftstreams {
     }
     interface StreamGroupLocationConfigurationArgs {
         /**
-         * The streaming capacity that is allocated and ready to handle stream requests without delay. You pay for this capacity whether it's in use or not. Best for quickest time from streaming request to streaming session. Default is 1 when creating a stream group or adding a location.
+         * The streaming capacity that is allocated and ready to handle stream requests without delay. You pay for this capacity whether it's in use or not. Best for quickest time from streaming request to streaming session. Default is 1 (2 for high stream classes) when creating a stream group or adding a location.
          */
         alwaysOnCapacity?: pulumi.Input<number>;
         /**
@@ -46568,6 +46757,11 @@ export declare namespace lambda {
          */
         maximumConcurrency?: pulumi.Input<number>;
     }
+    /**
+     * Specific access configuration settings that tell Lambda how to authenticate with your schema registry.
+     *  If you're working with an GLU schema registry, don't provide authentication details in this object. Instead, ensure that your execution role has the required permissions for Lambda to access your cluster.
+     *  If you're working with a Confluent schema registry, choose the authentication method in the ``Type`` field, and provide the ASMlong secret ARN in the ``URI`` field.
+     */
     interface EventSourceMappingSchemaRegistryAccessConfigArgs {
         /**
          * The type of authentication Lambda uses to access your schema registry.
@@ -46578,6 +46772,9 @@ export declare namespace lambda {
          */
         uri?: pulumi.Input<string>;
     }
+    /**
+     * Specific configuration settings for a Kafka schema registry.
+     */
     interface EventSourceMappingSchemaRegistryConfigArgs {
         /**
          * An array of access configuration objects that tell Lambda how to authenticate with your schema registry.
@@ -46585,16 +46782,14 @@ export declare namespace lambda {
         accessConfigs?: pulumi.Input<pulumi.Input<inputs.lambda.EventSourceMappingSchemaRegistryAccessConfigArgs>[]>;
         /**
          * The record format that Lambda delivers to your function after schema validation.
-         *
-         * - Choose `JSON` to have Lambda deliver the record to your function as a standard JSON object.
-         * - Choose `SOURCE` to have Lambda deliver the record to your function in its original source format. Lambda removes all schema metadata, such as the schema ID, before sending the record to your function.
+         *   +  Choose ``JSON`` to have Lambda deliver the record to your function as a standard JSON object.
+         *   +  Choose ``SOURCE`` to have Lambda deliver the record to your function in its original source format. Lambda removes all schema metadata, such as the schema ID, before sending the record to your function.
          */
         eventRecordFormat?: pulumi.Input<enums.lambda.EventSourceMappingSchemaRegistryConfigEventRecordFormat>;
         /**
          * The URI for your schema registry. The correct URI format depends on the type of schema registry you're using.
-         *
-         * - For AWS Glue schema registries, use the ARN of the registry.
-         * - For Confluent schema registries, use the URL of the registry.
+         *   +  For GLU schema registries, use the ARN of the registry.
+         *   +  For Confluent schema registries, use the URL of the registry.
          */
         schemaRegistryUri?: pulumi.Input<string>;
         /**
@@ -46602,9 +46797,12 @@ export declare namespace lambda {
          */
         schemaValidationConfigs?: pulumi.Input<pulumi.Input<inputs.lambda.EventSourceMappingSchemaValidationConfigArgs>[]>;
     }
+    /**
+     * Specific schema validation configuration settings that tell Lambda the message attributes you want to validate and filter using your schema registry.
+     */
     interface EventSourceMappingSchemaValidationConfigArgs {
         /**
-         * The attributes you want your schema registry to validate and filter for. If you selected `JSON` as the `EventRecordFormat` , Lambda also deserializes the selected message attributes.
+         * The attributes you want your schema registry to validate and filter for. If you selected ``JSON`` as the ``EventRecordFormat``, Lambda also deserializes the selected message attributes.
          */
         attribute?: pulumi.Input<enums.lambda.EventSourceMappingSchemaValidationConfigAttribute>;
     }
@@ -54073,6 +54271,24 @@ export declare namespace omics {
          */
         type: pulumi.Input<enums.omics.VariantStoreEncryptionType>;
     }
+    interface WorkflowDefinitionRepositoryArgs {
+        /**
+         * The Amazon Resource Name (ARN) of the connection to the source code repository.
+         */
+        connectionArn?: pulumi.Input<string>;
+        /**
+         * A list of file patterns to exclude when retrieving the workflow definition from the repository.
+         */
+        excludeFilePatterns?: pulumi.Input<pulumi.Input<string>[]>;
+        /**
+         * The full repository identifier, including the repository owner and name. For example, 'repository-owner/repository-name'.
+         */
+        fullRepositoryId?: pulumi.Input<string>;
+        /**
+         * The source reference for the repository, such as a branch name, tag, or commit ID.
+         */
+        sourceReference?: pulumi.Input<inputs.omics.WorkflowSourceReferenceArgs>;
+    }
     interface WorkflowParameterArgs {
         /**
          * The parameter's description.
@@ -54083,6 +54299,16 @@ export declare namespace omics {
          */
         optional?: pulumi.Input<boolean>;
     }
+    interface WorkflowSourceReferenceArgs {
+        /**
+         * The type of source reference, such as branch, tag, or commit.
+         */
+        type?: pulumi.Input<enums.omics.WorkflowSourceReferencetype>;
+        /**
+         * The value of the source reference, such as the branch name, tag name, or commit ID.
+         */
+        value?: pulumi.Input<string>;
+    }
     interface WorkflowVersionWorkflowParameterArgs {
         /**
          * The parameter's description.
@@ -88864,12 +89090,18 @@ export declare namespace s3tables {
      * Contains details about the metadata for an Iceberg table.
      */
     interface TableIcebergMetadataArgs {
+        /**
+         * The schema for an Iceberg table.
+         */
         icebergSchema: pulumi.Input<inputs.s3tables.TableIcebergSchemaArgs>;
     }
     /**
      * Contains details about the schema for an Iceberg table
      */
     interface TableIcebergSchemaArgs {
+        /**
+         * The schema fields for the table
+         */
         schemaFieldList: pulumi.Input<pulumi.Input<inputs.s3tables.TableSchemaFieldArgs>[]>;
     }
     /**
@@ -97611,6 +97843,9 @@ export declare namespace synthetics {
          */
         screenshotName: pulumi.Input<string>;
     }
+    interface CanaryBrowserConfigArgs {
+        browserType: pulumi.Input<enums.synthetics.CanaryBrowserType>;
+    }
     interface CanaryCodeArgs {
         /**
          * List of Lambda layers to attach to the canary
@@ -97722,6 +97957,7 @@ export declare namespace synthetics {
          * List of screenshots used as base reference for visual testing
          */
         baseScreenshots?: pulumi.Input<pulumi.Input<inputs.synthetics.CanaryBaseScreenshotArgs>[]>;
+        browserType?: pulumi.Input<enums.synthetics.CanaryBrowserType>;
     }
     interface CanaryVpcConfigArgs {
         /**
@@ -98101,6 +98337,8 @@ export declare namespace transfer {
         /**
          * A list of security groups IDs that are available to attach to your server's endpoint.
          *
+         * > While `SecurityGroupIds` appears in the response syntax for consistency with `CreateServer` and `UpdateServer` operations, this field is not populated in `DescribeServer` responses. Security groups are managed at the VPC endpoint level and can be modified outside of the Transfer Family service. To retrieve current security group information, use the EC2 `DescribeVpcEndpoints` API with the `VpcEndpointId` returned in the response.
+         * >
          * > This property can only be set when `EndpointType` is set to `VPC` .
          * >
          * > You can edit the `SecurityGroupIds` property in the [UpdateServer](https://docs.aws.amazon.com/transfer/latest/userguide/API_UpdateServer.html) API only if you are changing the `EndpointType` from `PUBLIC` or `VPC_ENDPOINT` to `VPC` . To change security groups associated with your server's VPC endpoint after creation, use the Amazon EC2 [ModifyVpcEndpoint](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyVpcEndpoint.html) API.