@awboost/cfn-resource-types 0.1.190 → 0.1.192

package/lib/AWS-ApplicationInsights-Application.d.ts

@@ -54,6 +54,13 @@ export type ApplicationInsightsApplicationProperties = {
      * @pattern `[a-zA-Z0-9.-_]*`
      */
     ResourceGroupName: string;
+    /**
+     * Application Insights sends notifications to this SNS topic whenever there is a problem update in the associated application.
+     * @minLength `20`
+     * @maxLength `300`
+     * @pattern `^arn:aws(-[\w]+)*:[\w\d-]+:([\w\d-]*)?:[\w\d_-]*([:/].+)*$`
+     */
+    SNSNotificationArn?: string;
     /**
      * The tags of Application Insights application.
      * @minLength `1`

package/lib/AWS-Batch-ComputeEnvironment.d.ts

@@ -78,6 +78,17 @@ export type EksConfiguration = {
 export type LaunchTemplateSpecification = {
     LaunchTemplateId?: string;
     LaunchTemplateName?: string;
+    Overrides?: LaunchTemplateSpecificationOverride[];
+    Version?: string;
+};
+/**
+ * Type definition for `AWS::Batch::ComputeEnvironment.LaunchTemplateSpecificationOverride`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-batch-computeenvironment-launchtemplatespecificationoverride.html}
+ */
+export type LaunchTemplateSpecificationOverride = {
+    LaunchTemplateId?: string;
+    LaunchTemplateName?: string;
+    TargetInstanceTypes?: string[];
     Version?: string;
 };
 /**

package/lib/AWS-DynamoDB-GlobalTable.d.ts

@@ -25,6 +25,7 @@ export type DynamoDBGlobalTableProperties = {
     StreamSpecification?: StreamSpecification;
     TableName?: string;
     TimeToLiveSpecification?: TimeToLiveSpecification;
+    WarmThroughput?: WarmThroughput;
     WriteOnDemandThroughputSettings?: WriteOnDemandThroughputSettings;
     WriteProvisionedThroughputSettings?: WriteProvisionedThroughputSettings;
 };
@@ -91,6 +92,7 @@ export type GlobalSecondaryIndex = {
      */
     KeySchema: KeySchema[];
     Projection: Projection;
+    WarmThroughput?: WarmThroughput;
     WriteOnDemandThroughputSettings?: WriteOnDemandThroughputSettings;
     WriteProvisionedThroughputSettings?: WriteProvisionedThroughputSettings;
 };
@@ -270,6 +272,20 @@ export type TimeToLiveSpecification = {
     AttributeName?: string;
     Enabled: boolean;
 };
+/**
+ * Type definition for `AWS::DynamoDB::GlobalTable.WarmThroughput`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-dynamodb-globaltable-warmthroughput.html}
+ */
+export type WarmThroughput = {
+    /**
+     * @min `1`
+     */
+    ReadUnitsPerSecond?: number;
+    /**
+     * @min `1`
+     */
+    WriteUnitsPerSecond?: number;
+};
 /**
  * Type definition for `AWS::DynamoDB::GlobalTable.WriteOnDemandThroughputSettings`.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-dynamodb-globaltable-writeondemandthroughputsettings.html}

package/lib/AWS-DynamoDB-Table.d.ts

@@ -5,7 +5,7 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  You should be aware of the following behaviors when working with DDB tables:
   +   CFNlong typically creates DDB tables in parallel. However, if your template includes multiple DDB tables with indexes, you must declare dependencies so that the tables are created sequentially. DDBlong limits the number of tables with secondary indexes that are in the creating state. If you create multiple tables with indexes at the same time, DDB returns an error and the stack operation fails. For an example, see [DynamoDB Table with a DependsOn Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html#aws-resource-dynamodb-table--examples--DynamoDB_Table_with_a_DependsOn_Attribute).
   
-   Our guidance is to use the latest schema documented here for your CFNlong templates. This schema supports the provisioning of all table settings below. When using this schema in your CFNlong templates, please ensure that your Identity and Access Management (IAM) policies are updated with appropriate permissions to allow for the authorization of these setting changes.
+   Our guidance is to use the latest schema documented for your CFNlong templates. This schema supports the provisioning of all table settings below. When using this schema in your CFNlong templates, please ensure that your Identity and Access Management (IAM) policies are updated with appropriate permissions to allow for the authorization of these setting changes.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html}
  */
 export type DynamoDBTableProperties = {
@@ -103,6 +103,7 @@ export type DynamoDBTableProperties = {
         For detailed information about the limits in DynamoDB, see [Limits in Amazon DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html) in the Amazon DynamoDB Developer Guide.
        */
     TimeToLiveSpecification?: TimeToLiveSpecification;
+    WarmThroughput?: WarmThroughput;
 };
 /**
  * Attribute type definition for `AWS::DynamoDB::Table`.
@@ -192,6 +193,7 @@ export type GlobalSecondaryIndex = {
        For current minimum and maximum provisioned throughput values, see [Service, Account, and Table Quotas](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html) in the *Amazon DynamoDB Developer Guide*.
        */
     ProvisionedThroughput?: ProvisionedThroughput;
+    WarmThroughput?: WarmThroughput;
 };
 /**
  * Type definition for `AWS::DynamoDB::Table.ImportSourceSpecification`.
@@ -470,12 +472,26 @@ export type TimeToLiveSpecification = {
      */
     Enabled: boolean;
 };
+/**
+ * Type definition for `AWS::DynamoDB::Table.WarmThroughput`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-dynamodb-table-warmthroughput.html}
+ */
+export type WarmThroughput = {
+    /**
+     * @min `1`
+     */
+    ReadUnitsPerSecond?: number;
+    /**
+     * @min `1`
+     */
+    WriteUnitsPerSecond?: number;
+};
 /**
  * The ``AWS::DynamoDB::Table`` resource creates a DDB table. For more information, see [CreateTable](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateTable.html) in the *API Reference*.
  You should be aware of the following behaviors when working with DDB tables:
   +   CFNlong typically creates DDB tables in parallel. However, if your template includes multiple DDB tables with indexes, you must declare dependencies so that the tables are created sequentially. DDBlong limits the number of tables with secondary indexes that are in the creating state. If you create multiple tables with indexes at the same time, DDB returns an error and the stack operation fails. For an example, see [DynamoDB Table with a DependsOn Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html#aws-resource-dynamodb-table--examples--DynamoDB_Table_with_a_DependsOn_Attribute).
   
-   Our guidance is to use the latest schema documented here for your CFNlong templates. This schema supports the provisioning of all table settings below. When using this schema in your CFNlong templates, please ensure that your Identity and Access Management (IAM) policies are updated with appropriate permissions to allow for the authorization of these setting changes.
+   Our guidance is to use the latest schema documented for your CFNlong templates. This schema supports the provisioning of all table settings below. When using this schema in your CFNlong templates, please ensure that your Identity and Access Management (IAM) policies are updated with appropriate permissions to allow for the authorization of these setting changes.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html}
  */
 export declare class DynamoDBTable extends $Resource<"AWS::DynamoDB::Table", DynamoDBTableProperties, DynamoDBTableAttributes> {

package/lib/AWS-DynamoDB-Table.js

@@ -4,7 +4,7 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
  You should be aware of the following behaviors when working with DDB tables:
   +   CFNlong typically creates DDB tables in parallel. However, if your template includes multiple DDB tables with indexes, you must declare dependencies so that the tables are created sequentially. DDBlong limits the number of tables with secondary indexes that are in the creating state. If you create multiple tables with indexes at the same time, DDB returns an error and the stack operation fails. For an example, see [DynamoDB Table with a DependsOn Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html#aws-resource-dynamodb-table--examples--DynamoDB_Table_with_a_DependsOn_Attribute).
   
-   Our guidance is to use the latest schema documented here for your CFNlong templates. This schema supports the provisioning of all table settings below. When using this schema in your CFNlong templates, please ensure that your Identity and Access Management (IAM) policies are updated with appropriate permissions to allow for the authorization of these setting changes.
+   Our guidance is to use the latest schema documented for your CFNlong templates. This schema supports the provisioning of all table settings below. When using this schema in your CFNlong templates, please ensure that your Identity and Access Management (IAM) policies are updated with appropriate permissions to allow for the authorization of these setting changes.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html}
  */
 export class DynamoDBTable extends $Resource {

package/lib/AWS-EC2-EC2Fleet.d.ts

@@ -117,7 +117,7 @@ export type InstanceRequirementsRequest = {
     BareMetal?: "included" | "required" | "excluded";
     BaselineEbsBandwidthMbps?: BaselineEbsBandwidthMbpsRequest;
     BurstablePerformance?: "included" | "required" | "excluded";
-    CpuManufacturers?: ("intel" | "amd" | "amazon-web-services")[];
+    CpuManufacturers?: ("intel" | "amd" | "amazon-web-services" | "apple")[];
     ExcludedInstanceTypes?: string[];
     InstanceGenerations?: ("current" | "previous")[];
     LocalStorage?: "included" | "required" | "excluded";

package/lib/AWS-EC2-LaunchTemplate.d.ts

@@ -22,7 +22,7 @@ export type EC2LaunchTemplateProperties = {
     LaunchTemplateName?: string;
     /**
        * The tags to apply to the launch template on creation. To tag the launch template, the resource type must be ``launch-template``.
-       To specify the tags for resources that are created during instance launch, use [TagSpecifications](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html#cfn-ec2-launchtemplate-launchtemplatedata-tagspecifications).
+       To specify the tags for the resources that are created when an instance is launched, you must use [TagSpecifications](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html#cfn-ec2-launchtemplate-launchtemplatedata-tagspecifications).
        */
     TagSpecifications?: LaunchTemplateTagSpecification[];
     /**
@@ -221,7 +221,7 @@ export type Ebs = {
        */
     Iops?: number;
     /**
-     * Identifier (key ID, key alias, key ARN, or alias ARN) of the customer managed KMS key to use for EBS encryption.
+     * The ARN of the symmetric KMSlong (KMS) CMK used for encryption.
      */
     KmsKeyId?: string;
     /**
@@ -355,7 +355,7 @@ export type InstanceMarketOptions = {
   
   If you specify ``InstanceRequirements``, you can't specify ``InstanceType``.
  Attribute-based instance type selection is only supported when using Auto Scaling groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in the [launch instance wizard](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-instance-wizard.html), or with the [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html) API or [AWS::EC2::Instance](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html) AWS CloudFormation resource, you can't specify ``InstanceRequirements``.
-  For more information, see [Specify attributes for instance type selection for EC2 Fleet or Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-attribute-based-instance-type-selection.html) and [Spot placement score](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-placement-score.html) in the *Amazon EC2 User Guide*.
+  For more information, see [Attribute-based instance type selection for EC2 Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-attribute-based-instance-type-selection.html), [Attribute-based instance type selection for Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-attribute-based-instance-type-selection.html), and [Spot placement score](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-placement-score.html) in the *Amazon EC2 User Guide*.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-instancerequirements.html}
  */
 export type InstanceRequirements = {
@@ -403,6 +403,7 @@ export type InstanceRequirements = {
        * The accelerator types that must be on the instance type.
         +  For instance types with GPU accelerators, specify ``gpu``.
         +  For instance types with FPGA accelerators, specify ``fpga``.
+        +  For instance types with inference accelerators, specify ``inference``.
         
        Default: Any accelerator type
        */
@@ -617,8 +618,7 @@ export type LaunchTemplateData = {
        */
     ElasticGpuSpecifications?: ElasticGpuSpecification[];
     /**
-       * Amazon Elastic Inference is no longer available.
-        An elastic inference accelerator to associate with the instance. Elastic inference accelerators are a resource you can attach to your Amazon EC2 instances to accelerate your Deep Learning (DL) inference workloads.
+       * An elastic inference accelerator to associate with the instance. Elastic inference accelerators are a resource you can attach to your Amazon EC2 instances to accelerate your Deep Learning (DL) inference workloads.
        You cannot specify accelerators from different generations in the same request.
         Starting April 15, 2023, AWS will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service.
        */
@@ -666,7 +666,7 @@ export type LaunchTemplateData = {
         
         If you specify ``InstanceRequirements``, you can't specify ``InstanceType``.
        Attribute-based instance type selection is only supported when using Auto Scaling groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in the [launch instance wizard](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-instance-wizard.html), or with the [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html) API or [AWS::EC2::Instance](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html) AWS CloudFormation resource, you can't specify ``InstanceRequirements``.
-        For more information, see [Specify attributes for instance type selection for EC2 Fleet or Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-attribute-based-instance-type-selection.html) and [Spot placement score](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-placement-score.html) in the *Amazon EC2 User Guide*.
+        For more information, see [Attribute-based instance type selection for EC2 Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-attribute-based-instance-type-selection.html), [Attribute-based instance type selection for Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-attribute-based-instance-type-selection.html), and [Spot placement score](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-placement-score.html) in the *Amazon EC2 User Guide*.
        */
     InstanceRequirements?: InstanceRequirements;
     /**
@@ -728,7 +728,8 @@ export type LaunchTemplateData = {
        */
     SecurityGroups?: string[];
     /**
-       * The tags to apply to resources that are created during instance launch.
+       * The tags to apply to the resources that are created during instance launch.
+       To tag a resource after it has been created, see [CreateTags](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTags.html).
        To tag the launch template itself, use [TagSpecifications](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html#cfn-ec2-launchtemplate-tagspecifications).
        */
     TagSpecifications?: TagSpecification[];
@@ -758,7 +759,6 @@ export type LaunchTemplateElasticInferenceAccelerator = {
 /**
  * Type definition for `AWS::EC2::LaunchTemplate.LaunchTemplateTagSpecification`.
  * Specifies the tags to apply to the launch template during creation.
- To specify the tags for the resources that are created during instance launch, use [AWS::EC2::LaunchTemplate TagSpecification](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-tagspecification.html).
   ``LaunchTemplateTagSpecification`` is a property of [AWS::EC2::LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html).
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatetagspecification.html}
  */
@@ -932,10 +932,9 @@ export type NetworkInterface = {
      */
     Groups?: string[];
     /**
-       * The type of network interface. To create an Elastic Fabric Adapter (EFA), specify ``efa`` or ``efa``. For more information, see [Elastic Fabric Adapter](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/efa.html) in the *Amazon EC2 User Guide*.
+       * The type of network interface. To create an Elastic Fabric Adapter (EFA), specify ``efa``. For more information, see [Elastic Fabric Adapter](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/efa.html) in the *Amazon EC2 User Guide*.
        If you are not creating an EFA, specify ``interface`` or omit this parameter.
-       If you specify ``efa-only``, do not assign any IP addresses to the network interface. EFA-only network interfaces do not support IP addresses.
-       Valid values: ``interface`` | ``efa`` | ``efa-only``
+       Valid values: ``interface`` | ``efa``
        */
     InterfaceType?: string;
     /**
@@ -1136,7 +1135,7 @@ export type Tag = {
 };
 /**
  * Type definition for `AWS::EC2::LaunchTemplate.TagSpecification`.
- * Specifies the tags to apply to resources that are created during instance launch.
+ * Specifies the tags to apply to a resource when the resource is created for the launch template.
   ``TagSpecification`` is a property type of [TagSpecifications](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html#cfn-ec2-launchtemplate-launchtemplatedata-tagspecifications). [TagSpecifications](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html#cfn-ec2-launchtemplate-launchtemplatedata-tagspecifications) is a property of [AWS::EC2::LaunchTemplate LaunchTemplateData](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html).
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-tagspecification.html}
  */

package/lib/AWS-EC2-SpotFleet.d.ts

@@ -140,7 +140,7 @@ export type InstanceRequirementsRequest = {
     BareMetal?: "included" | "required" | "excluded";
     BaselineEbsBandwidthMbps?: BaselineEbsBandwidthMbpsRequest;
     BurstablePerformance?: "included" | "required" | "excluded";
-    CpuManufacturers?: ("intel" | "amd" | "amazon-web-services")[];
+    CpuManufacturers?: ("intel" | "amd" | "amazon-web-services" | "apple")[];
     ExcludedInstanceTypes?: string[];
     InstanceGenerations?: ("current" | "previous")[];
     LocalStorage?: "included" | "required" | "excluded";

package/lib/AWS-ECR-RepositoryCreationTemplate.d.ts

@@ -87,7 +87,7 @@ export type EncryptionConfiguration = {
      */
     EncryptionType: EncryptionType;
     /**
-     * If you use the KMS encryption type, specify the CMK to use for encryption. The alias, key ID, or full ARN of the CMK can be specified. The key must exist in the same Region as the repository. If no key is specified, the default AWS managed CMK for Amazon ECR will be used.
+     * If you use the KMS or KMS_DSSE encryption type, specify the CMK to use for encryption. The alias, key ID, or full ARN of the CMK can be specified. The key must exist in the same Region as the repository. If no key is specified, the default AWS managed CMK for Amazon ECR will be used.
      * @minLength `1`
      * @maxLength `2048`
      */
@@ -98,7 +98,7 @@ export type EncryptionConfiguration = {
  * The encryption type to use.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecr-repositorycreationtemplate-encryptiontype.html}
  */
-export type EncryptionType = "AES256" | "KMS";
+export type EncryptionType = "AES256" | "KMS" | "KMS_DSSE";
 /**
  * Type definition for `AWS::ECR::RepositoryCreationTemplate.Tag`.
  * An array of key-value pairs to apply to this resource.

package/lib/AWS-ECS-Service.d.ts

@@ -7,6 +7,7 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html}
  */
 export type ECSServiceProperties = {
+    AvailabilityZoneRebalancing?: "ENABLED" | "DISABLED";
     /**
        * The capacity provider strategy to use for the service.
        If a ``capacityProviderStrategy`` is specified, the ``launchType`` parameter must be omitted. If no ``capacityProviderStrategy`` or ``launchType`` is specified, the ``defaultCapacityProviderStrategy`` for the cluster is used.
@@ -18,7 +19,7 @@ export type ECSServiceProperties = {
      */
     Cluster?: string;
     /**
-     * Optional deployment parameters that control how many tasks run during the deployment and the failure detection methods.
+     * Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
      */
     DeploymentConfiguration?: DeploymentConfiguration;
     /**
@@ -127,6 +128,7 @@ export type ECSServiceProperties = {
      * The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
      */
     VolumeConfigurations?: ServiceVolumeConfiguration[];
+    VpcLatticeConfigurations?: VpcLatticeConfiguration[];
 };
 /**
  * Attribute type definition for `AWS::ECS::Service`.
@@ -222,7 +224,7 @@ export type DeploymentCircuitBreaker = {
 };
 /**
  * Type definition for `AWS::ECS::Service.DeploymentConfiguration`.
- * Optional deployment parameters that control how many tasks run during the deployment and the failure detection methods.
+ * Optional deployment parameters that control how many tasks run during a deployment and the ordering of stopping and starting tasks.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentconfiguration.html}
  */
 export type DeploymentConfiguration = {
@@ -313,7 +315,7 @@ export type LoadBalancer = {
      */
     ContainerPort?: number;
     /**
-       * The name of the load balancer to associate with the service or task set.
+       * The name of the load balancer to associate with the Amazon ECS service or task set.
        If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
        */
     LoadBalancerName?: string;
@@ -705,6 +707,15 @@ export type TimeoutConfiguration = {
      */
     PerRequestTimeoutSeconds?: number;
 };
+/**
+ * Type definition for `AWS::ECS::Service.VpcLatticeConfiguration`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-vpclatticeconfiguration.html}
+ */
+export type VpcLatticeConfiguration = {
+    PortName: string;
+    RoleArn: string;
+    TargetGroupArn: string;
+};
 /**
  * The ``AWS::ECS::Service`` resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.
   The stack update fails if you change any properties that require replacement and at least one ECS Service Connect ``ServiceConnectConfiguration`` property the is configured. This is because AWS CloudFormation creates the replacement service first, but each ``ServiceConnectService`` must have a name that is unique in the namespace.

package/lib/AWS-ECS-TaskDefinition.d.ts

@@ -226,7 +226,7 @@ export type ContainerDefinition = {
     DockerSecurityOptions?: string[];
     /**
        * Early versions of the Amazon ECS container agent don't properly handle ``entryPoint`` parameters. If you have problems using ``entryPoint``, update your container agent or enter your commands and arguments as ``command`` array items instead.
-        The entry point that's passed to the container. This parameter maps to ``Entrypoint`` in tthe docker container create command and the ``--entrypoint`` option to docker run.
+        The entry point that's passed to the container. This parameter maps to ``Entrypoint`` in the docker container create command and the ``--entrypoint`` option to docker run.
        */
     EntryPoint?: string[];
     /**
@@ -259,7 +259,7 @@ export type ContainerDefinition = {
      */
     HealthCheck?: HealthCheck;
     /**
-       * The hostname to use for your container. This parameter maps to ``Hostname`` in thethe docker container create command and the ``--hostname`` option to docker run.
+       * The hostname to use for your container. This parameter maps to ``Hostname`` in the docker container create command and the ``--hostname`` option to docker run.
         The ``hostname`` parameter is not supported if you're using the ``awsvpc`` network mode.
        */
     Hostname?: string;
@@ -318,7 +318,7 @@ export type ContainerDefinition = {
        */
     MountPoints?: MountPoint[];
     /**
-     * The name of a container. If you're linking multiple containers together in a task definition, the ``name`` of one container can be entered in the ``links`` of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to ``name`` in tthe docker container create command and the ``--name`` option to docker run.
+     * The name of a container. If you're linking multiple containers together in a task definition, the ``name`` of one container can be entered in the ``links`` of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to ``name`` in the docker container create command and the ``--name`` option to docker run.
      */
     Name: string;
     /**
@@ -335,7 +335,7 @@ export type ContainerDefinition = {
        */
     Privileged?: boolean;
     /**
-     * When this parameter is ``true``, a TTY is allocated. This parameter maps to ``Tty`` in tthe docker container create command and the ``--tty`` option to docker run.
+     * When this parameter is ``true``, a TTY is allocated. This parameter maps to ``Tty`` in the docker container create command and the ``--tty`` option to docker run.
      */
     PseudoTerminal?: boolean;
     /**
@@ -376,13 +376,13 @@ export type ContainerDefinition = {
         +  Linux platform version ``1.3.0`` or later.
         +  Windows platform version ``1.0.0`` or later.
         
-       The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used.
+       For tasks that use the Fargate launch type, the max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used.
        For tasks that use the EC2 launch type, if the ``stopTimeout`` parameter isn't specified, the value set for the Amazon ECS container agent configuration variable ``ECS_CONTAINER_STOP_TIMEOUT`` is used. If neither the ``stopTimeout`` parameter or the ``ECS_CONTAINER_STOP_TIMEOUT`` agent configuration variable are set, then the default values of 30 seconds for Linux containers and 30 seconds on Windows containers are used. Your container instances require at least version 1.26.0 of the container agent to use a container stop timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see [Updating the Amazon ECS Container Agent](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html) in the *Amazon Elastic Container Service Developer Guide*. If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ``ecs-init`` package. If your container instances are launched from version ``20190301`` or later, then they contain the required versions of the container agent and ``ecs-init``. For more information, see [Amazon ECS-optimized Linux AMI](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) in the *Amazon Elastic Container Service Developer Guide*.
-       The valid values are 2-120 seconds.
+       The valid values for Fargate are 2-120 seconds.
        */
     StopTimeout?: number;
     /**
-     * A list of namespaced kernel parameters to set in the container. This parameter maps to ``Sysctls`` in tthe docker container create command and the ``--sysctl`` option to docker run. For example, you can configure ``net.ipv4.tcp_keepalive_time`` setting to maintain longer lived connections.
+     * A list of namespaced kernel parameters to set in the container. This parameter maps to ``Sysctls`` in the docker container create command and the ``--sysctl`` option to docker run. For example, you can configure ``net.ipv4.tcp_keepalive_time`` setting to maintain longer lived connections.
      */
     SystemControls?: SystemControl[];
     /**
@@ -404,8 +404,9 @@ export type ContainerDefinition = {
         This parameter is not supported for Windows containers.
        */
     User?: string;
+    VersionConsistency?: "enabled" | "disabled";
     /**
-     * Data volumes to mount from another container. This parameter maps to ``VolumesFrom`` in tthe docker container create command and the ``--volumes-from`` option to docker run.
+     * Data volumes to mount from another container. This parameter maps to ``VolumesFrom`` in the docker container create command and the ``--volumes-from`` option to docker run.
      */
     VolumesFrom?: VolumeFrom[];
     /**
@@ -621,7 +622,7 @@ export type HealthCheck = {
         ``[ "CMD-SHELL", "curl -f http://localhost/ || exit 1" ]``
        You don't include the double quotes and brackets when you use the AWS Management Console.
         ``CMD-SHELL, curl -f http://localhost/ || exit 1``
-       An exit code of 0 indicates success, and non-zero exit code indicates failure. For more information, see ``HealthCheck`` in tthe docker container create command
+       An exit code of 0 indicates success, and non-zero exit code indicates failure. For more information, see ``HealthCheck`` in the docker container create command
        */
     Command?: string[];
     /**
@@ -729,7 +730,7 @@ export type LinuxParameters = {
        */
     Capabilities?: KernelCapabilities;
     /**
-       * Any host devices to expose to the container. This parameter maps to ``Devices`` in tthe docker container create command and the ``--device`` option to docker run.
+       * Any host devices to expose to the container. This parameter maps to ``Devices`` in the docker container create command and the ``--device`` option to docker run.
         If you're using tasks that use the Fargate launch type, the ``devices`` parameter isn't supported.
        */
     Devices?: Device[];
@@ -777,8 +778,17 @@ export type LogConfiguration = {
        */
     LogDriver: string;
     /**
-     * The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: ``sudo docker version --format '{{.Server.APIVersion}}'``
-     */
+       * The configuration options to send to the log driver.
+       The options you can specify depend on the log driver. Some of the options you can specify when you use the ``awslogs`` log driver to route logs to Amazon CloudWatch include the following:
+        + awslogs-create-group Required: No Specify whether you want the log group to be created automatically. If this option isn't specified, it defaults to false. Your IAM policy must include the logs:CreateLogGroup permission before you attempt to use awslogs-create-group. + awslogs-region Required: Yes Specify the Region that the awslogs log driver is to send your Docker logs to. You can choose to send all of your logs from clusters in different Regions to a single region in CloudWatch Logs. This is so that they're all visible in one location. Otherwise, you can separate them by Region for more granularity. Make sure that the specified log group exists in the Region that you specify with this option. + awslogs-group Required: Yes Make sure to specify a log group that the awslogs log driver sends its log streams to. + awslogs-stream-prefix Required: Yes, when using the Fargate launch type.Optional for the EC2 launch type, required for the Fargate launch type. Use the awslogs-stream-prefix option to associate a log stream with the specified prefix, the container name, and the ID of the Amazon ECS task that the container belongs to. If you specify a prefix with this option, then the log stream takes the format prefix-name/container-name/ecs-task-id. If you don't specify a prefix with this option, then the log stream is named after the container ID that's assigned by the Docker daemon on the container instance. Because it's difficult to trace logs back to the container that sent them with just the Docker container ID (which is only available on the container instance), we recommend that you specify a prefix with this option. For Amazon ECS services, you can use the service name as the prefix. Doing so, you can trace log streams to the service that the container belongs to, the name of the container that sent them, and the ID of the task that the container belongs to. You must specify a stream-prefix for your logs to have your logs appear in the Log pane when using the Amazon ECS console. + awslogs-datetime-format Required: No This option defines a multiline start pattern in Python strftime format. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. One example of a use case for using this format is for parsing output such as a stack dump, which might otherwise be logged in multiple entries. The correct pattern allows it to be captured in a single entry. For more information, see awslogs-datetime-format. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + awslogs-multiline-pattern Required: No This option defines a multiline start pattern that uses a regular expression. A log message consists of a line that matches the pattern and any following lines that don’t match the pattern. The matched line is the delimiter between log messages. For more information, see awslogs-multiline-pattern. This option is ignored if awslogs-datetime-format is also configured. You cannot configure both the awslogs-datetime-format and awslogs-multiline-pattern options. Multiline logging performs regular expression parsing and matching of all log messages. This might have a negative impact on logging performance. + mode Required: No Valid values: non-blocking | blocking This option defines the delivery mode of log messages from the container to CloudWatch Logs. The delivery mode you choose affects application availability when the flow of logs from container to CloudWatch is interrupted. If you use the blocking mode and the flow of logs to CloudWatch is interrupted, calls from container code to write to the stdout and stderr streams will block. The logging thread of the application will block as a result. This may cause the application to become unresponsive and lead to container healthcheck failure. If you use the non-blocking mode, the container's logs are instead stored in an in-memory intermediate buffer configured with the max-buffer-size option. This prevents the application from becoming unresponsive when logs cannot be sent to CloudWatch. We recommend using this mode if you want to ensure service availability and are okay with some log loss. For more information, see Preventing log loss with non-blocking mode in the awslogs container log driver. + max-buffer-size Required: No Default value: 1m When non-blocking mode is used, the max-buffer-size log option controls the size of the buffer that's used for intermediate message storage. Make sure to specify an adequate buffer size based on your application. When the buffer fills up, further logs cannot be stored. Logs that cannot be stored are lost.
+       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``.
+       When you export logs to Amazon Kinesis Data Streams, you can specify an AWS Region with ``region`` and a data stream name with ``stream``.
+        When you export logs to Amazon OpenSearch Service, you can specify options like ``Name``, ``Host`` (OpenSearch Service endpoint without protocol), ``Port``, ``Index``, ``Type``, ``Aws_auth``, ``Aws_region``, ``Suppress_Type_Name``, and ``tls``.
+       When you export logs to Amazon S3, you can specify the bucket using the ``bucket`` option. You can also specify ``region``, ``total_file_size``, ``upload_timeout``, and ``use_put_object`` as options.
+       This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: ``sudo docker version --format '{{.Server.APIVersion}}'``
+       */
     Options?: Record<string, string>;
     /**
      * The secrets to pass to the log configuration. For more information, see [Specifying sensitive data](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html) in the *Amazon Elastic Container Service Developer Guide*.
@@ -985,7 +995,7 @@ export type Secret = {
 };
 /**
  * Type definition for `AWS::ECS::TaskDefinition.SystemControl`.
- * A list of namespaced kernel parameters to set in the container. This parameter maps to ``Sysctls`` in tthe docker container create command and the ``--sysctl`` option to docker run. For example, you can configure ``net.ipv4.tcp_keepalive_time`` setting to maintain longer lived connections.
+ * A list of namespaced kernel parameters to set in the container. This parameter maps to ``Sysctls`` in the docker container create command and the ``--sysctl`` option to docker run. For example, you can configure ``net.ipv4.tcp_keepalive_time`` setting to maintain longer lived connections.
  We don't recommend that you specify network-related ``systemControls`` parameters for multiple containers in a single task that also uses either the ``awsvpc`` or ``host`` network mode. Doing this has the following disadvantages:
   +  For tasks that use the ``awsvpc`` network mode including Fargate, if you set ``systemControls`` for any container, it applies to all containers in the task. If you set different ``systemControls`` for multiple containers in a single task, the container that's started last determines which ``systemControls`` take effect.
   +  For tasks that use the ``host`` network mode, the network namespace ``systemControls`` aren't supported.
@@ -1079,7 +1089,7 @@ export type Tmpfs = {
  */
 export type Ulimit = {
     /**
-     * The hard limit for the ``ulimit`` type.
+     * The hard limit for the ``ulimit`` type. The value can be specified in bytes, seconds, or as a count, depending on the ``type`` of the ``ulimit``.
      */
     HardLimit: number;
     /**
@@ -1087,7 +1097,7 @@ export type Ulimit = {
      */
     Name: string;
     /**
-     * The soft limit for the ``ulimit`` type.
+     * The soft limit for the ``ulimit`` type. The value can be specified in bytes, seconds, or as a count, depending on the ``type`` of the ``ulimit``.
      */
     SoftLimit: number;
 };

package/lib/AWS-Events-Connection.d.ts

@@ -32,7 +32,7 @@ export type EventsConnectionAttributes = {
     Arn: string;
     /**
      * The arn of the secrets manager secret created in the customer account.
-     * @pattern `^arn:aws([a-z]|\-)*:secretsmanager:([a-z]|\d|\-)*:([0-9]{12})?:secret:[\/_+=\.@\-A-Za-z0-9]+$`
+     * @pattern `^arn:aws([a-z]|\-)*:secretsmanager:([a-z]|\d|\-)*:([0-9]{12})?:secret:([a-z]|\d|\-)*(!)*[\/_+=\.@\-A-Za-z0-9]+$`
      */
     SecretArn: string;
 };

package/lib/AWS-FIS-ExperimentTemplate.d.ts

@@ -15,6 +15,7 @@ export type FISExperimentTemplateProperties = {
      */
     Description: string;
     ExperimentOptions?: ExperimentTemplateExperimentOptions;
+    ExperimentReportConfiguration?: ExperimentTemplateExperimentReportConfiguration;
     LogConfiguration?: ExperimentTemplateLogConfiguration;
     /**
      * The Amazon Resource Name (ARN) of an IAM role that grants the AWS FIS service permission to perform service actions on your behalf.
@@ -38,6 +39,17 @@ export type FISExperimentTemplateProperties = {
 export type FISExperimentTemplateAttributes = {
     Id: string;
 };
+/**
+ * Type definition for `AWS::FIS::ExperimentTemplate.CloudWatchDashboard`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-fis-experimenttemplate-cloudwatchdashboard.html}
+ */
+export type CloudWatchDashboard = {
+    /**
+     * @minLength `1`
+     * @maxLength `512`
+     */
+    DashboardIdentifier: string;
+};
 /**
  * Type definition for `AWS::FIS::ExperimentTemplate.ExperimentTemplateAction`.
  * Specifies an action for the experiment template.
@@ -87,6 +99,31 @@ export type ExperimentTemplateExperimentOptions = {
      */
     EmptyTargetResolutionMode?: "fail" | "skip";
 };
+/**
+ * Type definition for `AWS::FIS::ExperimentTemplate.ExperimentTemplateExperimentReportConfiguration`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-fis-experimenttemplate-experimenttemplateexperimentreportconfiguration.html}
+ */
+export type ExperimentTemplateExperimentReportConfiguration = {
+    DataSources: {
+        CloudWatchDashboards?: CloudWatchDashboard[];
+    };
+    Outputs: {
+        ExperimentReportS3Configuration: {
+            /**
+             * @minLength `3`
+             * @maxLength `63`
+             */
+            BucketName: string;
+            /**
+             * @minLength `1`
+             * @maxLength `1024`
+             */
+            Prefix?: string;
+        };
+    };
+    PostExperimentDuration?: string;
+    PreExperimentDuration?: string;
+};
 /**
  * Type definition for `AWS::FIS::ExperimentTemplate.ExperimentTemplateLogConfiguration`.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-fis-experimenttemplate-experimenttemplatelogconfiguration.html}