@propulsionworks/cloudformation 0.1.17 → 0.1.19

package/out/exports/resources.generated/aws-customerprofiles-segmentdefinition.d.ts

@@ -340,7 +340,7 @@ export type ProfileAttributes = {
      */
     PhoneNumber?: ProfileDimension | undefined;
     /**
-     * Specifies profile type based criteria for a segment.
+     * The type of profile.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-customerprofiles-segmentdefinition-profileattributes.html#cfn-customerprofiles-segmentdefinition-profileattributes-profiletype}
      */
     ProfileType?: ProfileTypeDimension | undefined;
@@ -376,11 +376,12 @@ export type ProfileType = "ACCOUNT_PROFILE" | "PROFILE";
  */
 export type ProfileTypeDimension = {
     /**
-     * The type of segment dimension to use for a profile type dimension.
+     * The action to segment on.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-customerprofiles-segmentdefinition-profiletypedimension.html#cfn-customerprofiles-segmentdefinition-profiletypedimension-dimensiontype}
      */
     DimensionType: ProfileTypeDimensionType;
     /**
+     * The values to apply the DimensionType on.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-customerprofiles-segmentdefinition-profiletypedimension.html#cfn-customerprofiles-segmentdefinition-profiletypedimension-values}
      */
     Values: ProfileType[];

package/out/exports/resources.generated/aws-datasync-locationnfs.d.ts

@@ -23,7 +23,7 @@ export type DataSyncLocationNFSProps = {
      */
     OnPremConfig: OnPremConfig;
     /**
-     * Specifies the DNS name or IP version 4 address of the NFS file server that your DataSync agent connects to.
+     * Specifies the DNS name or IP address (IPv4 or IPv6) of the NFS file server that your DataSync agent connects to.
      * @maxLength 255
      * @pattern ^(([a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z0-9\-]*[A-Za-z0-9])$
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-datasync-locationnfs.html#cfn-datasync-locationnfs-serverhostname}

package/out/exports/resources.generated/aws-datasync-locationobjectstorage.d.ts

@@ -79,7 +79,7 @@ export type DataSyncLocationObjectStorageProps = {
      */
     ServerCertificate?: string | undefined;
     /**
-     * Specifies the domain name or IP version 4 (IPv4) address of the object storage server that your DataSync agent connects to.
+     * Specifies the domain name or IP address (IPv4 or IPv6) of the object storage server that your DataSync agent connects to.
      * @maxLength 255
      * @pattern ^(([a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z0-9\-]*[A-Za-z0-9])$
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-datasync-locationobjectstorage.html#cfn-datasync-locationobjectstorage-serverhostname}

package/out/exports/resources.generated/aws-datasync-locationsmb.d.ts

@@ -68,12 +68,9 @@ export type DataSyncLocationSMBProps = {
      */
     Password?: string | undefined;
     /**
-     * Specifies the domain name or IP address of the SMB file server that your DataSync agent connects to.
+     * Specifies the domain name or IP address (IPv4 or IPv6) of the SMB file server that your DataSync agent connects to.
      *
-     * Remember the following when configuring this parameter:
-     *
-     * - You can't specify an IP version 6 (IPv6) address.
-     * - If you're using Kerberos authentication, you must specify a domain name.
+     * > If you're using Kerberos authentication, you must specify a domain name.
      * @maxLength 255
      * @pattern ^(([a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z0-9\-]*[A-Za-z0-9])$
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-datasync-locationsmb.html#cfn-datasync-locationsmb-serverhostname}

package/out/exports/resources.generated/aws-datazone-connection.d.ts

@@ -530,7 +530,7 @@ export type RedshiftPropertiesInput = {
      * The Amazon Redshift database name.
      * @minLength 1
      * @maxLength 64
-     * @pattern ^[a-z0-9_]+$
+     * @pattern ^[a-z0-9_-]+$
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-datazone-connection-redshiftpropertiesinput.html#cfn-datazone-connection-redshiftpropertiesinput-databasename}
      */
     DatabaseName?: string | undefined;

package/out/exports/resources.generated/aws-dax-cluster.d.ts

@@ -39,6 +39,10 @@ export type DAXClusterProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dax-cluster.html#cfn-dax-cluster-iamrolearn}
      */
     IAMRoleARN: string;
+    /**
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dax-cluster.html#cfn-dax-cluster-networktype}
+     */
+    NetworkType?: string | undefined;
     /**
      * The node type for the nodes in the cluster. (All nodes in a DAX cluster are of the same type.)
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dax-cluster.html#cfn-dax-cluster-nodetype}

package/out/exports/resources.generated/aws-docdb-dbcluster.d.ts

@@ -74,6 +74,11 @@ export type DocDBDBClusterProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-docdb-dbcluster.html#cfn-docdb-dbcluster-engineversion}
      */
     EngineVersion?: string | undefined;
+    /**
+     * The cluster identifier of the new global cluster.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-docdb-dbcluster.html#cfn-docdb-dbcluster-globalclusteridentifier}
+     */
+    GlobalClusterIdentifier?: string | undefined;
     /**
      * The AWS KMS key identifier for an encrypted cluster.
      *
@@ -123,6 +128,10 @@ export type DocDBDBClusterProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-docdb-dbcluster.html#cfn-docdb-dbcluster-masterusername}
      */
     MasterUsername?: string | undefined;
+    /**
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-docdb-dbcluster.html#cfn-docdb-dbcluster-networktype}
+     */
+    NetworkType?: string | undefined;
     /**
      * Specifies the port that the database engine is listening on.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-docdb-dbcluster.html#cfn-docdb-dbcluster-port}

package/out/exports/resources.generated/aws-ec2-capacityreservation.d.ts

@@ -51,7 +51,7 @@ export type EC2CapacityReservationProps = {
     /**
      * The number of instances for which to reserve capacity.
      *
-     * > You can request future-dated Capacity Reservations for an instance count with a minimum of 100 vCPUs. For example, if you request a future-dated Capacity Reservation for `m5.xlarge` instances, you must request at least 25 instances ( *25 * m5.xlarge = 100 vCPUs* ).
+     * > You can request future-dated Capacity Reservations for an instance count with a minimum of 64 vCPUs. For example, if you request a future-dated Capacity Reservation for `m5.xlarge` instances, you must request at least 25 instances ( *16 * m5.xlarge = 64 vCPUs* ).
      *
      * Valid range: 1 - 1000
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-capacityreservation.html#cfn-ec2-capacityreservation-instancecount}
@@ -77,7 +77,7 @@ export type EC2CapacityReservationProps = {
     /**
      * The instance type for which to reserve capacity.
      *
-     * > You can request future-dated Capacity Reservations for instance types in the C, M, R, I, and T instance families only.
+     * > You can request future-dated Capacity Reservations for instance types in the C, M, R, I, T, and G instance families only.
      *
      * For more information, see [Instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html) in the *Amazon EC2 User Guide* .
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-capacityreservation.html#cfn-ec2-capacityreservation-instancetype}

package/out/exports/resources.generated/aws-ec2-instance.d.ts

@@ -165,7 +165,7 @@ export type EC2InstanceProps = {
      */
     KernelId?: string | undefined;
     /**
-     * The name of the key pair. You can create a key pair using [CreateKeyPair](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateKeyPair.html) or [ImportKeyPair](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ImportKeyPair.html) .
+     * The name of the key pair. For more information, see [Create a key pair for your EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-key-pairs.html) .
      *
      * > If you do not specify a key pair, you can't connect to the instance unless you choose an AMI that is configured to allow users another way to log in.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-instance.html#cfn-ec2-instance-keyname}

package/out/exports/resources.generated/aws-ec2-instanceconnectendpoint.d.ts

@@ -28,6 +28,8 @@ export type EC2InstanceConnectEndpointProps = {
      * - `true` - Use the client IP address as the source.
      * - `false` - Use the network interface IP address as the source.
      *
+     * > `PreserveClientIp` is only supported on IPv4 EC2 Instance Connect Endpoints. To use `PreserveClientIp` , the value for `IpAddressType` must be `ipv4` .
+     *
      * Default: `false`
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-instanceconnectendpoint.html#cfn-ec2-instanceconnectendpoint-preserveclientip}
      */

package/out/exports/resources.generated/aws-ec2-trafficmirrorsession.d.ts

@@ -31,6 +31,11 @@ export type EC2TrafficMirrorSessionProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-trafficmirrorsession.html#cfn-ec2-trafficmirrorsession-networkinterfaceid}
      */
     NetworkInterfaceId: string;
+    /**
+     * The ID of the account that owns the Traffic Mirror session.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-trafficmirrorsession.html#cfn-ec2-trafficmirrorsession-ownerid}
+     */
+    OwnerId?: string | undefined;
     /**
      * The number of bytes in each packet to mirror. These are bytes after the VXLAN header. Do not specify this parameter when you want to mirror the entire packet. To mirror a subset of the packet, set this to the length (in bytes) that you want to mirror. For example, if you set this value to 100, then the first 100 bytes that meet the filter criteria are copied to the target.
      *
@@ -73,6 +78,7 @@ export type EC2TrafficMirrorSessionProps = {
  */
 export type EC2TrafficMirrorSessionAttribs = {
     /**
+     * The ID of a Traffic Mirror session.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-trafficmirrorsession.html#cfn-ec2-trafficmirrorsession-id}
      */
     Id: string;

package/out/exports/resources.generated/aws-ecs-service.d.ts

@@ -101,7 +101,7 @@ export type ECSServiceProps = {
      */
     DeploymentConfiguration?: DeploymentConfiguration | undefined;
     /**
-     * The deployment controller to use for the service. If no deployment controller is specified, the default value of `ECS` is used.
+     * The deployment controller to use for the service.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-deploymentcontroller}
      */
     DeploymentController?: DeploymentController | undefined;
@@ -117,7 +117,7 @@ export type ECSServiceProps = {
     /**
      * Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see [Tagging your Amazon ECS resources](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html) in the *Amazon Elastic Container Service Developer Guide* .
      *
-     * When you use Amazon ECS managed tags, you need to set the `propagateTags` request parameter.
+     * When you use Amazon ECS managed tags, you must set the `propagateTags` request parameter.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-enableecsmanagedtags}
      */
     EnableECSManagedTags?: boolean | undefined;
@@ -273,6 +273,32 @@ export type ECSServiceAttribs = {
      */
     ServiceArn: string;
 };
+/**
+ * The advanced settings for a load balancer used in blue/green deployments. Specify the alternate target group, listener rules, and IAM role required for traffic shifting during blue/green deployments. For more information, see [Required resources for Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-deployment-implementation.html) in the *Amazon Elastic Container Service Developer Guide* .
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-advancedconfiguration.html}
+ */
+export type AdvancedConfiguration = {
+    /**
+     * The Amazon Resource Name (ARN) of the alternate target group for Amazon ECS blue/green deployments.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-advancedconfiguration.html#cfn-ecs-service-advancedconfiguration-alternatetargetgrouparn}
+     */
+    AlternateTargetGroupArn: string;
+    /**
+     * The Amazon Resource Name (ARN) that that identifies the production listener rule (in the case of an Application Load Balancer) or listener (in the case for an Network Load Balancer) for routing production traffic.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-advancedconfiguration.html#cfn-ecs-service-advancedconfiguration-productionlistenerrule}
+     */
+    ProductionListenerRule?: string | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of the IAM role that grants Amazon ECS permission to call the Elastic Load Balancing APIs for you.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-advancedconfiguration.html#cfn-ecs-service-advancedconfiguration-rolearn}
+     */
+    RoleArn?: string | undefined;
+    /**
+     * The Amazon Resource Name (ARN) that identifies ) that identifies the test listener rule (in the case of an Application Load Balancer) or listener (in the case for an Network Load Balancer) for routing test traffic.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-advancedconfiguration.html#cfn-ecs-service-advancedconfiguration-testlistenerrule}
+     */
+    TestListenerRule?: string | undefined;
+};
 /**
  * An object representing the networking details for a task or service. For example `awsVpcConfiguration={subnets=["subnet-12344321"],securityGroups=["sg-12344321"]}` .
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-awsvpcconfiguration.html}
@@ -339,7 +365,7 @@ export type CapacityProviderStrategyItem = {
  *
  * When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure.
  *
- * You can only use the `DeploymentAlarms` method to detect failures when the `DeploymentController` is set to `ECS` (rolling update).
+ * You can only use the `DeploymentAlarms` method to detect failures when the `DeploymentController` is set to `ECS` .
  *
  * For more information, see [Rolling update](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html) in the **Amazon Elastic Container Service Developer Guide** .
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentalarms.html}
@@ -391,6 +417,19 @@ export type DeploymentConfiguration = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html#cfn-ecs-service-deploymentconfiguration-alarms}
      */
     Alarms?: DeploymentAlarms | undefined;
+    /**
+     * The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted.
+     *
+     * The following rules apply when you don't specify a value:
+     *
+     * - For rolling deployments, the value is set to 3 hours (180 minutes).
+     * - When you use an external deployment controller ( `EXTERNAL` ), or the CodeDeploy blue/green deployment controller ( `CODE_DEPLOY` ), the value is set to 3 hours (180 minutes).
+     * - For all other cases, the value is set to 36 hours (2160 minutes).
+     * @min 0
+     * @max 1440
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html#cfn-ecs-service-deploymentconfiguration-baketimeinminutes}
+     */
+    BakeTimeInMinutes?: number | undefined;
     /**
      * > The deployment circuit breaker can only be used for services using the rolling update ( `ECS` ) deployment type.
      *
@@ -398,6 +437,11 @@ export type DeploymentConfiguration = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html#cfn-ecs-service-deploymentconfiguration-deploymentcircuitbreaker}
      */
     DeploymentCircuitBreaker?: DeploymentCircuitBreaker | undefined;
+    /**
+     * An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html#cfn-ecs-service-deploymentconfiguration-lifecyclehooks}
+     */
+    LifecycleHooks?: DeploymentLifecycleHook[] | undefined;
     /**
      * If a service is using the rolling update ( `ECS` ) deployment type, the `maximumPercent` parameter represents an upper limit on the number of your service's tasks that are allowed in the `RUNNING` or `PENDING` state during a deployment, as a percentage of the `desiredCount` (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the `REPLICA` service scheduler and has a `desiredCount` of four tasks and a `maximumPercent` value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default `maximumPercent` value for a service using the `REPLICA` service scheduler is 200%.
      *
@@ -439,6 +483,14 @@ export type DeploymentConfiguration = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html#cfn-ecs-service-deploymentconfiguration-minimumhealthypercent}
      */
     MinimumHealthyPercent?: number | undefined;
+    /**
+     * The deployment strategy for the service. Choose from these valid values:
+     *
+     * - `ROLLING` - When you create a service which uses the rolling update ( `ROLLING` ) deployment strategy, the Amazon ECS service scheduler replaces the currently running tasks with new tasks. The number of tasks that Amazon ECS adds or removes from the service during a rolling update is controlled by the service deployment configuration.
+     * - `BLUE_GREEN` - A blue/green deployment strategy ( `BLUE_GREEN` ) is a release methodology that reduces downtime and risk by running two identical production environments called blue and green. With Amazon ECS blue/green deployments, you can validate new service revisions before directing production traffic to them. This approach provides a safer way to deploy changes with the ability to quickly roll back if needed.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html#cfn-ecs-service-deploymentconfiguration-strategy}
+     */
+    Strategy?: "ROLLING" | "BLUE_GREEN" | undefined;
 };
 /**
  * The deployment controller to use for the service.
@@ -446,15 +498,119 @@ export type DeploymentConfiguration = {
  */
 export type DeploymentController = {
     /**
-     * The deployment controller type to use. There are three deployment controller types available:
+     * The deployment controller type to use.
+     *
+     * The deployment controller is the mechanism that determines how tasks are deployed for your service. The valid options are:
      *
-     * - **ECS** - The rolling update ( `ECS` ) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the [DeploymentConfiguration](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeploymentConfiguration.html) .
-     * - **CODE_DEPLOY** - The blue/green ( `CODE_DEPLOY` ) deployment type uses the blue/green deployment model powered by AWS CodeDeploy , which allows you to verify a new deployment of a service before sending production traffic to it.
-     * - **EXTERNAL** - The external ( `EXTERNAL` ) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
+     * - ECS
+     *
+     * When you create a service which uses the `ECS` deployment controller, you can choose between the following deployment strategies:
+     *
+     * - `ROLLING` : When you create a service which uses the *rolling update* ( `ROLLING` ) deployment strategy, the Amazon ECS service scheduler replaces the currently running tasks with new tasks. The number of tasks that Amazon ECS adds or removes from the service during a rolling update is controlled by the service deployment configuration.
+     *
+     * Rolling update deployments are best suited for the following scenarios:
+     *
+     * - Gradual service updates: You need to update your service incrementally without taking the entire service offline at once.
+     * - Limited resource requirements: You want to avoid the additional resource costs of running two complete environments simultaneously (as required by blue/green deployments).
+     * - Acceptable deployment time: Your application can tolerate a longer deployment process, as rolling updates replace tasks one by one.
+     * - No need for instant roll back: Your service can tolerate a rollback process that takes minutes rather than seconds.
+     * - Simple deployment process: You prefer a straightforward deployment approach without the complexity of managing multiple environments, target groups, and listeners.
+     * - No load balancer requirement: Your service doesn't use or require a load balancer, Application Load Balancer , Network Load Balancer , or Service Connect (which are required for blue/green deployments).
+     * - Stateful applications: Your application maintains state that makes it difficult to run two parallel environments.
+     * - Cost sensitivity: You want to minimize deployment costs by not running duplicate environments during deployment.
+     *
+     * Rolling updates are the default deployment strategy for services and provide a balance between deployment safety and resource efficiency for many common application scenarios.
+     * - `BLUE_GREEN` : A *blue/green* deployment strategy ( `BLUE_GREEN` ) is a release methodology that reduces downtime and risk by running two identical production environments called blue and green. With Amazon ECS blue/green deployments, you can validate new service revisions before directing production traffic to them. This approach provides a safer way to deploy changes with the ability to quickly roll back if needed.
+     *
+     * Amazon ECS blue/green deployments are best suited for the following scenarios:
+     *
+     * - Service validation: When you need to validate new service revisions before directing production traffic to them
+     * - Zero downtime: When your service requires zero-downtime deployments
+     * - Instant roll back: When you need the ability to quickly roll back if issues are detected
+     * - Load balancer requirement: When your service uses Application Load Balancer , Network Load Balancer , or Service Connect
+     * - External
+     *
+     * Use a third-party deployment controller.
+     * - Blue/green deployment (powered by CodeDeploy )
+     *
+     * CodeDeploy installs an updated version of the application as a new replacement task set and reroutes production traffic from the original application task set to the replacement task set. The original task set is terminated after a successful deployment. Use this deployment controller to verify a new deployment of a service before sending production traffic to it.
+     *
+     * When updating the deployment controller for a service, consider the following depending on the type of migration you're performing.
+     *
+     * - If you have a template that contains the `EXTERNAL` deployment controller information as well as `TaskSet` and `PrimaryTaskSet` resources, and you remove the task set resources from the template when updating from `EXTERNAL` to `ECS` , the `DescribeTaskSet` and `DeleteTaskSet` API calls will return a 400 error after the deployment controller is updated to `ECS` . This results in a delete failure on the task set resources, even though the stack transitions to `UPDATE_COMPLETE` status. For more information, see [Resource removed from stack but not deleted](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-resource-removed-not-deleted) in the AWS CloudFormation User Guide. To fix this issue, delete the task sets directly using the Amazon ECS `DeleteTaskSet` API. For more information about how to delete a task set, see [DeleteTaskSet](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteTaskSet.html) in the Amazon Elastic Container Service API Reference.
+     * - If you're migrating from `CODE_DEPLOY` to `ECS` with a new task definition and AWS CloudFormation performs a rollback operation, the Amazon ECS `UpdateService` request fails with the following error:
+     *
+     * Resource handler returned message: "Invalid request provided: Unable to update task definition on services with a CODE_DEPLOY deployment controller.
+     * - After a successful migration from `ECS` to `EXTERNAL` deployment controller, you need to manually remove the `ACTIVE` task set, because Amazon ECS no longer manages the deployment. For information about how to delete a task set, see [DeleteTaskSet](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteTaskSet.html) in the Amazon Elastic Container Service API Reference.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentcontroller.html#cfn-ecs-service-deploymentcontroller-type}
      */
     Type?: "CODE_DEPLOY" | "ECS" | "EXTERNAL" | undefined;
 };
+/**
+ * A deployment lifecycle hook runs custom logic at specific stages of the deployment process. Currently, you can use Lambda functions as hook targets.
+ *
+ * For more information, see [Lifecycle hooks for Amazon ECS service deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html) in the *Amazon Elastic Container Service Developer Guide* .
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentlifecyclehook.html}
+ */
+export type DeploymentLifecycleHook = {
+    /**
+     * The Amazon Resource Name (ARN) of the hook target. Currently, only Lambda function ARNs are supported.
+     *
+     * You must provide this parameter when configuring a deployment lifecycle hook.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentlifecyclehook.html#cfn-ecs-service-deploymentlifecyclehook-hooktargetarn}
+     */
+    HookTargetArn: string;
+    /**
+     * The lifecycle stages at which to run the hook. Choose from these valid values:
+     *
+     * - RECONCILE_SERVICE
+     *
+     * The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state.
+     *
+     * You can use a lifecycle hook for this stage.
+     * - PRE_SCALE_UP
+     *
+     * The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic.
+     *
+     * You can use a lifecycle hook for this stage.
+     * - POST_SCALE_UP
+     *
+     * The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.
+     *
+     * You can use a lifecycle hook for this stage.
+     * - TEST_TRAFFIC_SHIFT
+     *
+     * The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic.
+     *
+     * You can use a lifecycle hook for this stage.
+     * - POST_TEST_TRAFFIC_SHIFT
+     *
+     * The test traffic shift is complete. The green service revision handles 100% of the test traffic.
+     *
+     * You can use a lifecycle hook for this stage.
+     * - PRODUCTION_TRAFFIC_SHIFT
+     *
+     * Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic.
+     *
+     * You can use a lifecycle hook for this stage.
+     * - POST_PRODUCTION_TRAFFIC_SHIFT
+     *
+     * The production traffic shift is complete.
+     *
+     * You can use a lifecycle hook for this stage.
+     *
+     * You must provide this parameter when configuring a deployment lifecycle hook.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentlifecyclehook.html#cfn-ecs-service-deploymentlifecyclehook-lifecyclestages}
+     */
+    LifecycleStages: ("RECONCILE_SERVICE" | "PRE_SCALE_UP" | "POST_SCALE_UP" | "TEST_TRAFFIC_SHIFT" | "POST_TEST_TRAFFIC_SHIFT" | "PRODUCTION_TRAFFIC_SHIFT" | "POST_PRODUCTION_TRAFFIC_SHIFT")[];
+    /**
+     * The Amazon Resource Name (ARN) of the IAM role that grants Amazon ECS permission to call Lambda functions on your behalf.
+     *
+     * For more information, see [Permissions required for Lambda functions in Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-permissions.html) in the *Amazon Elastic Container Service Developer Guide* .
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentlifecyclehook.html#cfn-ecs-service-deploymentlifecyclehook-rolearn}
+     */
+    RoleArn: string;
+};
 /**
  * The tag specifications of an Amazon EBS volume.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-ebstagspecification.html}
@@ -485,6 +641,11 @@ export type EBSTagSpecification = {
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-loadbalancer.html}
  */
 export type LoadBalancer = {
+    /**
+     * The advanced settings for the load balancer used in blue/green deployments. Specify the alternate target group, listener rules, and IAM role required for traffic shifting during blue/green deployments.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-loadbalancer.html#cfn-ecs-service-loadbalancer-advancedconfiguration}
+     */
+    AdvancedConfiguration?: AdvancedConfiguration | undefined;
     /**
      * The name of the container (as it appears in a container definition) to associate with the load balancer.
      *
@@ -742,6 +903,11 @@ export type ServiceConnectClientAlias = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnectclientalias.html#cfn-ecs-service-serviceconnectclientalias-port}
      */
     Port: number;
+    /**
+     * The configuration for test traffic routing rules used during blue/green deployments with Amazon ECS Service Connect. This allows you to route a portion of traffic to the new service revision of your service for testing before shifting all production traffic.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnectclientalias.html#cfn-ecs-service-serviceconnectclientalias-testtrafficrules}
+     */
+    TestTrafficRules?: ServiceConnectTestTrafficRules | undefined;
 };
 /**
  * The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.
@@ -836,6 +1002,41 @@ export type ServiceConnectService = {
      */
     Tls?: ServiceConnectTlsConfiguration | undefined;
 };
+/**
+ * The test traffic routing configuration for Amazon ECS blue/green deployments. This configuration allows you to define rules for routing specific traffic to the new service revision during the deployment process, allowing for safe testing before full production traffic shift.
+ *
+ * For more information, see [Service Connect for Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-blue-green.html) in the *Amazon Elastic Container Service Developer Guide* .
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrules.html}
+ */
+export type ServiceConnectTestTrafficRules = {
+    /**
+     * The HTTP header-based routing rules that determine which requests should be routed to the new service version during blue/green deployment testing. These rules provide fine-grained control over test traffic routing based on request headers.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrules.html#cfn-ecs-service-serviceconnecttesttrafficrules-header}
+     */
+    Header: ServiceConnectTestTrafficRulesHeader;
+};
+/**
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrulesheader.html}
+ */
+export type ServiceConnectTestTrafficRulesHeader = {
+    /**
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrulesheader.html#cfn-ecs-service-serviceconnecttesttrafficrulesheader-name}
+     */
+    Name: string;
+    /**
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrulesheader.html#cfn-ecs-service-serviceconnecttesttrafficrulesheader-value}
+     */
+    Value?: ServiceConnectTestTrafficRulesHeaderValue | undefined;
+};
+/**
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrulesheadervalue.html}
+ */
+export type ServiceConnectTestTrafficRulesHeaderValue = {
+    /**
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttesttrafficrulesheadervalue.html#cfn-ecs-service-serviceconnecttesttrafficrulesheadervalue-exact}
+     */
+    Exact: string;
+};
 /**
  * The certificate root authority that secures your service.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-serviceconnecttlscertificateauthority.html}

package/out/exports/resources.generated/aws-events-eventbus.d.ts

@@ -50,6 +50,22 @@ export type EventsEventBusProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-events-eventbus.html#cfn-events-eventbus-kmskeyidentifier}
      */
     KmsKeyIdentifier?: string | undefined;
+    /**
+     * The logging configuration settings for the event bus.
+     *
+     * For more information, see [Configuring logs for event buses](https://docs.aws.amazon.com/eb-event-bus-logs.html) in the *EventBridge User Guide* .
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-events-eventbus.html#cfn-events-eventbus-logconfig}
+     */
+    LogConfig?: {
+        /**
+         * Configures whether or not to include event detail, input transformer details, target properties, and target input in the applicable log messages.
+         */
+        IncludeDetail?: "FULL" | "NONE" | undefined;
+        /**
+         * Configures the log level of the EventBus and determines which log messages are sent to Ingestion Hub for delivery.
+         */
+        Level?: "INFO" | "ERROR" | "TRACE" | "OFF" | undefined;
+    } | undefined;
     /**
      * The name of the new event bus.
      *

package/out/exports/resources.generated/aws-gamelift-containerfleet.d.ts

@@ -289,7 +289,7 @@ export type IpPermission = {
  */
 export type LocationCapacity = {
     /**
-     * The number of EC2 instances you want to maintain in the specified fleet location. This value must fall between the minimum and maximum size limits.
+     * The number of EC2 instances you want to maintain in the specified fleet location. This value must fall between the minimum and maximum size limits. If any auto-scaling policy is defined for the container fleet, the desired instance will only be applied once during fleet creation and will be ignored in updates to avoid conflicts with auto-scaling. During updates with any auto-scaling policy defined, if current desired instance is lower than the new MinSize, it will be increased to the new MinSize; if current desired instance is larger than the new MaxSize, it will be decreased to the new MaxSize.
      * @min 0
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-gamelift-containerfleet-locationcapacity.html#cfn-gamelift-containerfleet-locationcapacity-desiredec2instances}
      */

package/out/exports/resources.generated/aws-guardduty-ipset.d.ts

@@ -24,6 +24,13 @@ export type GuardDutyIPSetProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-guardduty-ipset.html#cfn-guardduty-ipset-detectorid}
      */
     DetectorId?: string | undefined;
+    /**
+     * The AWS account ID that owns the Amazon S3 bucket specified in the *Location* field.
+     *
+     * When you provide this account ID, GuardDuty will validate that the S3 bucket belongs to this account. If you don't specify an account ID owner, GuardDuty doesn't perform any validation.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-guardduty-ipset.html#cfn-guardduty-ipset-expectedbucketowner}
+     */
+    ExpectedBucketOwner?: string | undefined;
     /**
      * The format of the file that contains the IPSet.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-guardduty-ipset.html#cfn-guardduty-ipset-format}

package/out/exports/resources.generated/aws-guardduty-threatintelset.d.ts

@@ -24,6 +24,13 @@ export type GuardDutyThreatIntelSetProps = {
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-guardduty-threatintelset.html#cfn-guardduty-threatintelset-detectorid}
      */
     DetectorId?: string | undefined;
+    /**
+     * The AWS account ID that owns the Amazon S3 bucket specified in the *Location* field.
+     *
+     * When you provide this account ID, GuardDuty will validate that the S3 bucket belongs to this account. If you don't specify an account ID owner, GuardDuty doesn't perform any validation.
+     * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-guardduty-threatintelset.html#cfn-guardduty-threatintelset-expectedbucketowner}
+     */
+    ExpectedBucketOwner?: string | undefined;
     /**
      * The format of the file that contains the ThreatIntelSet.
      * @minLength 1

package/out/exports/resources.generated/aws-iotsitewise-gateway.d.ts

@@ -25,7 +25,7 @@ export type IoTSiteWiseGatewayProps = {
      */
     GatewayPlatform: GatewayPlatform;
     /**
-     * The version of the gateway. A value of `3` indicates an MQTT-enabled, V3 gateway, while `2` indicates a Classic streams, V2 gateway.
+     * The version of the gateway you want to create.
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iotsitewise-gateway.html#cfn-iotsitewise-gateway-gatewayversion}
      */
     GatewayVersion?: string | undefined;
@@ -56,13 +56,19 @@ export type GatewayCapabilitySummary = {
      */
     CapabilityConfiguration?: string | undefined;
     /**
-     * The namespace of the capability configuration. For example, if you configure OPC-UA sources from the AWS IoT SiteWise console, your OPC-UA capability configuration has the namespace `iotsitewise:opcuacollector:version` , where `version` is a number such as `1` .
+     * The namespace of the capability configuration. For example, if you configure OPC UA sources for an MQTT-enabled gateway, your OPC-UA capability configuration has the namespace `iotsitewise:opcuacollector:3` .
      * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iotsitewise-gateway-gatewaycapabilitysummary.html#cfn-iotsitewise-gateway-gatewaycapabilitysummary-capabilitynamespace}
      */
     CapabilityNamespace: string;
 };
 /**
- * Contains a gateway's platform information.
+ * The gateway's platform configuration. You can only specify one platform type in a gateway.
+ *
+ * (Legacy only) For Greengrass V1 gateways, specify the `greengrass` parameter with a valid Greengrass group ARN.
+ *
+ * For Greengrass V2 gateways, specify the `greengrassV2` parameter with a valid core device thing name. If creating a V3 gateway ( `gatewayVersion=3` ), you must also specify the `coreDeviceOperatingSystem` .
+ *
+ * For Siemens Industrial Edge gateways, specify the `siemensIE` parameter with a valid IoT Core thing name.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iotsitewise-gateway-gatewayplatform.html}
  */
 export type GatewayPlatform = {