@awboost/cfn-resource-types 0.1.123 → 0.1.124

package/lib/AWS-KinesisFirehose-DeliveryStream.d.ts

@@ -527,7 +527,6 @@ export type MSKSourceConfiguration = {
      * @pattern `arn:.*`
      */
     MSKClusterARN: string;
-    ReadFromTimestamp?: string;
     /**
      * @minLength `1`
      * @maxLength `255`

package/lib/AWS-NetworkFirewall-LoggingConfiguration.d.ts

@@ -30,7 +30,7 @@ export type LogDestinationConfig = {
      */
     LogDestination: Record<string, string>;
     LogDestinationType: "S3" | "CloudWatchLogs" | "KinesisDataFirehose";
-    LogType: "ALERT" | "FLOW";
+    LogType: "ALERT" | "FLOW" | "TLS";
 };
 /**
  * Type definition for `AWS::NetworkFirewall::LoggingConfiguration.LoggingConfiguration`.

package/lib/AWS-OSIS-Pipeline.d.ts

@@ -98,6 +98,20 @@ export type OSISPipelineAttributes = {
              * A list of subnet IDs associated with the VPC endpoint.
              */
             SubnetIds: string[];
+            /**
+             * Options for attaching a VPC to the pipeline.
+             */
+            VpcAttachmentOptions: {
+                /**
+                 * Whether the pipeline should be attached to the provided VPC
+                 */
+                AttachToVpc: boolean;
+                /**
+                 * The CIDR block to be reserved for OpenSearch Ingestion to create elastic network interfaces (ENIs).
+                 * @pattern `^((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)/(3[0-2]|[12]?[0-9])$`
+                 */
+                CidrBlock: string;
+            };
             /**
              * Defines whether you or Amazon OpenSearch Ingestion service create and manage the VPC endpoint configured for the pipeline.
              */
@@ -201,6 +215,20 @@ export type VpcOptions = {
      * A list of subnet IDs associated with the VPC endpoint.
      */
     SubnetIds: string[];
+    /**
+     * Options for attaching a VPC to the pipeline.
+     */
+    VpcAttachmentOptions?: {
+        /**
+         * Whether the pipeline should be attached to the provided VPC
+         */
+        AttachToVpc: boolean;
+        /**
+         * The CIDR block to be reserved for OpenSearch Ingestion to create elastic network interfaces (ENIs).
+         * @pattern `^((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)/(3[0-2]|[12]?[0-9])$`
+         */
+        CidrBlock: string;
+    };
     /**
      * Defines whether you or Amazon OpenSearch Ingestion service create and manage the VPC endpoint configured for the pipeline.
      */

package/lib/AWS-RDS-DBCluster.d.ts

@@ -5,11 +5,11 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide*.
  For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide*.
   You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported.
-    *Updating DB clusters*
+   *Updating DB clusters*
  When properties labeled "*Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)" are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster.
   We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure:
   1.  Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance.
-  1.  Create a snapshot of the DB cluster. For more information, see [Creating a DB Cluster Snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html).
+  1.  Create a snapshot of the DB cluster. For more information, see [Creating a DB cluster snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html).
   1.  If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the ``SnapshotIdentifier`` property with the ID of the DB cluster snapshot that you want to use.
  After you restore a DB cluster with a ``SnapshotIdentifier`` property, you must specify the same ``SnapshotIdentifier`` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the ``SnapshotIdentifier`` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified ``SnapshotIdentifier`` property, and the original DB cluster is deleted.
   1.  Update the stack.
@@ -43,13 +43,11 @@ export type RDSDBClusterProperties = {
        */
     AvailabilityZones?: string[];
     /**
-       * The target backtrack window, in seconds. To disable backtracking, set this value to 0.
-        Currently, Backtrack is only supported for Aurora MySQL DB clusters.
-        Default: 0
+       * The target backtrack window, in seconds. To disable backtracking, set this value to ``0``.
+       Valid for Cluster Type: Aurora MySQL DB clusters only
+       Default: ``0``
        Constraints:
         +  If specified, this value must be set to a number from 0 to 259,200 (72 hours).
-        
-       Valid for: Aurora MySQL DB clusters only
        * @min `0`
        */
     BacktrackWindow?: number;
@@ -408,7 +406,7 @@ export type RDSDBClusterProperties = {
         +   ``full-copy`` - The new DB cluster is restored as a full copy of the source DB cluster.
         +   ``copy-on-write`` - The new DB cluster is restored as a clone of the source DB cluster.
         
-        If you don't specify a ``RestoreType`` value, then the new DB cluster is restored as a full copy of the source DB cluster.
+       If you don't specify a ``RestoreType`` value, then the new DB cluster is restored as a full copy of the source DB cluster.
        Valid for: Aurora DB clusters and Multi-AZ DB clusters
        */
     RestoreType?: string;
@@ -486,8 +484,8 @@ export type RDSDBClusterProperties = {
        */
     StorageType?: string;
     /**
-       * An optional array of key-value pairs to apply to this DB cluster.
-       Valid for: Aurora DB clusters and Multi-AZ DB clusters
+       * Tags to assign to the DB cluster.
+       Valid for Cluster Type: Aurora DB clusters and Multi-AZ DB clusters
        * @maxLength `50`
        */
     Tags?: Tag[];
@@ -668,11 +666,11 @@ export type Tag = {
  For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide*.
  For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide*.
   You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported.
-    *Updating DB clusters*
+   *Updating DB clusters*
  When properties labeled "*Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)" are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster.
   We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure:
   1.  Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance.
-  1.  Create a snapshot of the DB cluster. For more information, see [Creating a DB Cluster Snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html).
+  1.  Create a snapshot of the DB cluster. For more information, see [Creating a DB cluster snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html).
   1.  If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the ``SnapshotIdentifier`` property with the ID of the DB cluster snapshot that you want to use.
  After you restore a DB cluster with a ``SnapshotIdentifier`` property, you must specify the same ``SnapshotIdentifier`` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the ``SnapshotIdentifier`` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified ``SnapshotIdentifier`` property, and the original DB cluster is deleted.
   1.  Update the stack.

package/lib/AWS-RDS-DBCluster.js

@@ -4,11 +4,11 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
  For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide*.
  For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide*.
   You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported.
-    *Updating DB clusters*
+   *Updating DB clusters*
  When properties labeled "*Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)" are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster.
   We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure:
   1.  Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance.
-  1.  Create a snapshot of the DB cluster. For more information, see [Creating a DB Cluster Snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html).
+  1.  Create a snapshot of the DB cluster. For more information, see [Creating a DB cluster snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html).
   1.  If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the ``SnapshotIdentifier`` property with the ID of the DB cluster snapshot that you want to use.
  After you restore a DB cluster with a ``SnapshotIdentifier`` property, you must specify the same ``SnapshotIdentifier`` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the ``SnapshotIdentifier`` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified ``SnapshotIdentifier`` property, and the original DB cluster is deleted.
   1.  Update the stack.

package/lib/AWS-RDS-DBClusterParameterGroup.d.ts

@@ -4,7 +4,7 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  * The ``AWS::RDS::DBClusterParameterGroup`` resource creates a new Amazon RDS DB cluster parameter group.
  For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide*.
   If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting.
- If you apply a change to parameter group associated with a stopped DB cluster, then the update stack waits until the DB cluster is started.
+ If you apply a change to parameter group associated with a stopped DB cluster, then the updated stack waits until the DB cluster is started.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbclusterparametergroup.html}
  */
 export type RDSDBClusterParameterGroupProperties = {
@@ -13,22 +13,34 @@ export type RDSDBClusterParameterGroupProperties = {
        Constraints:
         +  Must not match the name of an existing DB cluster parameter group.
         
-       If you don't specify a value for ``DBClusterParameterGroupName`` property, a name is automatically created for the DB cluster parameter group.
         This value is stored as a lowercase string.
        * @pattern `^[a-zA-Z]{1}(?:-?[a-zA-Z0-9])*$`
        */
     DBClusterParameterGroupName?: string;
     /**
-     * A friendly description for this DB cluster parameter group.
+     * The description for the DB cluster parameter group.
      */
     Description: string;
     /**
-       * The DB cluster parameter group family name. A DB cluster parameter group can be associated with one and only one DB cluster parameter group family, and can be applied only to a DB cluster running a DB engine and engine version compatible with that DB cluster parameter group family.
-        The DB cluster parameter group family can't be changed when updating a DB cluster parameter group.
-        To list all of the available parameter group families, use the following command:
-        ``aws rds describe-db-engine-versions --query "DBEngineVersions[].DBParameterGroupFamily"``
-       The output contains duplicates.
-       For more information, see ``CreateDBClusterParameterGroup``.
+       * The DB cluster parameter group family name. A DB cluster parameter group can be associated with one and only one DB cluster parameter group family, and can be applied only to a DB cluster running a database engine and engine version compatible with that DB cluster parameter group family.
+        *Aurora MySQL*
+       Example: ``aurora-mysql5.7``, ``aurora-mysql8.0``
+        *Aurora PostgreSQL*
+       Example: ``aurora-postgresql14``
+        *RDS for MySQL*
+       Example: ``mysql8.0``
+        *RDS for PostgreSQL*
+       Example: ``postgres13``
+       To list all of the available parameter group families for a DB engine, use the following command:
+        ``aws rds describe-db-engine-versions --query "DBEngineVersions[].DBParameterGroupFamily" --engine <engine>``
+       For example, to list all of the available parameter group families for the Aurora PostgreSQL DB engine, use the following command:
+        ``aws rds describe-db-engine-versions --query "DBEngineVersions[].DBParameterGroupFamily" --engine aurora-postgresql``
+        The output contains duplicates.
+        The following are the valid DB engine values:
+        +   ``aurora-mysql``
+        +   ``aurora-postgresql``
+        +   ``mysql``
+        +   ``postgres``
        */
     Family: string;
     /**
@@ -36,7 +48,7 @@ export type RDSDBClusterParameterGroupProperties = {
      */
     Parameters: Record<string, any>;
     /**
-     * An optional array of key-value pairs to apply to this DB cluster parameter group.
+     * Tags to assign to the DB cluster parameter group.
      * @maxLength `50`
      */
     Tags?: Tag[];
@@ -65,7 +77,7 @@ export type Tag = {
  * The ``AWS::RDS::DBClusterParameterGroup`` resource creates a new Amazon RDS DB cluster parameter group.
  For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide*.
   If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting.
- If you apply a change to parameter group associated with a stopped DB cluster, then the update stack waits until the DB cluster is started.
+ If you apply a change to parameter group associated with a stopped DB cluster, then the updated stack waits until the DB cluster is started.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbclusterparametergroup.html}
  */
 export declare class RDSDBClusterParameterGroup extends $Resource<"AWS::RDS::DBClusterParameterGroup", RDSDBClusterParameterGroupProperties, Record<string, never>> {

package/lib/AWS-RDS-DBClusterParameterGroup.js

@@ -3,7 +3,7 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
  * The ``AWS::RDS::DBClusterParameterGroup`` resource creates a new Amazon RDS DB cluster parameter group.
  For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide*.
   If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting.
- If you apply a change to parameter group associated with a stopped DB cluster, then the update stack waits until the DB cluster is started.
+ If you apply a change to parameter group associated with a stopped DB cluster, then the updated stack waits until the DB cluster is started.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbclusterparametergroup.html}
  */
 export class RDSDBClusterParameterGroup extends $Resource {

package/lib/AWS-RDS-DBInstance.d.ts

@@ -6,7 +6,7 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  For more information about creating a DB instance in an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide*.
  If you import an existing DB instance, and the template configuration doesn't match the actual configuration of the DB instance, AWS CloudFormation applies the changes in the template during the import operation.
   If a DB instance is deleted or replaced during an update, AWS CloudFormation deletes all automated snapshots. However, it retains manual DB snapshots. During an update that requires replacement, you can apply a stack policy to prevent DB instances from being replaced. For more information, see [Prevent Updates to Stack Resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/protect-stack-resources.html).
-    *Updating DB instances*
+   *Updating DB instances*
  When properties labeled "*Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)" are updated, AWS CloudFormation first creates a replacement DB instance, then changes references from other dependent resources to point to the replacement DB instance, and finally deletes the old DB instance.
   We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB instance. To preserve your data, perform the following procedure:
   1.  Deactivate any applications that are using the DB instance so that there's no activity on the DB instance.
@@ -156,8 +156,9 @@ export type RDSDBInstanceProperties = {
        */
     CustomIAMInstanceProfile?: string;
     /**
-     * The identifier of the DB cluster that the instance will belong to.
-     */
+       * The identifier of the DB cluster that this DB instance will belong to.
+       This setting doesn't apply to RDS Custom DB instances.
+       */
     DBClusterIdentifier?: string;
     /**
        * The identifier for the Multi-AZ DB cluster snapshot to restore from.
@@ -288,9 +289,8 @@ export type RDSDBInstanceProperties = {
     /**
        * A DB subnet group to associate with the DB instance. If you update this value, the new subnet group must be a subnet group in a new VPC.
        If there's no DB subnet group, then the DB instance isn't a VPC DB instance.
-       For more information about using Amazon RDS in a VPC, see [Using Amazon RDS with Amazon Virtual Private Cloud (VPC)](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.html) in the *Amazon RDS User Guide*.
-        *Amazon Aurora*
-       Not applicable. The DB subnet group is managed by the DB cluster. If specified, the setting must match the DB cluster setting.
+       For more information about using Amazon RDS in a VPC, see [Amazon VPC and Amazon RDS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.html) in the *Amazon RDS User Guide*.
+       This setting doesn't apply to Amazon Aurora DB instances. The DB subnet group is managed by the DB cluster. If specified, the setting must match the DB cluster setting.
        */
     DBSubnetGroupName?: string;
     /**
@@ -304,9 +304,8 @@ export type RDSDBInstanceProperties = {
        */
     DeleteAutomatedBackups?: boolean;
     /**
-       * A value that indicates whether the DB instance has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection is disabled. For more information, see [Deleting a DB Instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DeleteInstance.html).
-        *Amazon Aurora*
-       Not applicable. You can enable or disable deletion protection for the DB cluster. For more information, see ``CreateDBCluster``. DB instances in a DB cluster can be deleted even when deletion protection is enabled for the DB cluster.
+       * Specifies whether the DB instance has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection isn't enabled. For more information, see [Deleting a DB Instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DeleteInstance.html).
+       This setting doesn't apply to Amazon Aurora DB instances. You can enable or disable deletion protection for the DB cluster. For more information, see ``CreateDBCluster``. DB instances in a DB cluster can be deleted even when deletion protection is enabled for the DB cluster.
        */
     DeletionProtection?: boolean;
     /**
@@ -516,30 +515,30 @@ export type RDSDBInstanceProperties = {
         
         *RDS for MariaDB*
        Constraints:
-         +  Must be 1 to 16 letters or numbers.
+        +  Must be 1 to 16 letters or numbers.
         +  Can't be a reserved word for the chosen database engine.
         
         *RDS for Microsoft SQL Server*
        Constraints:
-         +  Must be 1 to 128 letters or numbers.
+        +  Must be 1 to 128 letters or numbers.
         +  First character must be a letter.
         +  Can't be a reserved word for the chosen database engine.
         
         *RDS for MySQL*
        Constraints:
-         +  Must be 1 to 16 letters or numbers.
+        +  Must be 1 to 16 letters or numbers.
         +  First character must be a letter.
         +  Can't be a reserved word for the chosen database engine.
         
         *RDS for Oracle*
        Constraints:
-         +  Must be 1 to 30 letters or numbers.
+        +  Must be 1 to 30 letters or numbers.
         +  First character must be a letter.
         +  Can't be a reserved word for the chosen database engine.
         
         *RDS for PostgreSQL*
        Constraints:
-         +  Must be 1 to 63 letters or numbers.
+        +  Must be 1 to 63 letters or numbers.
         +  First character must be a letter.
         +  Can't be a reserved word for the chosen database engine.
        * @minLength `1`
@@ -556,10 +555,11 @@ export type RDSDBInstanceProperties = {
        */
     MaxAllocatedStorage?: number;
     /**
-       * The interval, in seconds, between points when Enhanced Monitoring metrics are collected for the DB instance. To disable collection of Enhanced Monitoring metrics, specify 0. The default is 0.
-       If ``MonitoringRoleArn`` is specified, then you must set ``MonitoringInterval`` to a value other than 0.
-       This setting doesn't apply to RDS Custom.
-       Valid Values: ``0, 1, 5, 10, 15, 30, 60``
+       * The interval, in seconds, between points when Enhanced Monitoring metrics are collected for the DB instance. To disable collection of Enhanced Monitoring metrics, specify ``0``.
+       If ``MonitoringRoleArn`` is specified, then you must set ``MonitoringInterval`` to a value other than ``0``.
+       This setting doesn't apply to RDS Custom DB instances.
+       Valid Values: ``0 | 1 | 5 | 10 | 15 | 30 | 60``
+       Default: ``0``
        */
     MonitoringInterval?: number;
     /**
@@ -569,10 +569,10 @@ export type RDSDBInstanceProperties = {
        */
     MonitoringRoleArn?: string;
     /**
-       * Specifies whether the database instance is a Multi-AZ DB instance deployment. You can't set the ``AvailabilityZone`` parameter if the ``MultiAZ`` parameter is set to true.
-        For more information, see [Multi-AZ deployments for high availability](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html) in the *Amazon RDS User Guide*.
-        *Amazon Aurora*
-       Not applicable. Amazon Aurora storage is replicated across all of the Availability Zones and doesn't require the ``MultiAZ`` option to be set.
+       * Specifies whether the DB instance is a Multi-AZ deployment. You can't set the ``AvailabilityZone`` parameter if the DB instance is a Multi-AZ deployment.
+       This setting doesn't apply to the following DB instances:
+        +  Amazon Aurora (DB instance Availability Zones (AZs) are managed by the DB cluster.)
+        +  RDS Custom
        */
     MultiAZ?: boolean;
     /**
@@ -616,10 +616,18 @@ export type RDSDBInstanceProperties = {
     PerformanceInsightsRetentionPeriod?: number;
     /**
        * The port number on which the database accepts connections.
-        *Amazon Aurora*
-       Not applicable. The port number is managed by the DB cluster.
-        *Db2*
-       Default value: ``50000``
+       This setting doesn't apply to Aurora DB instances. The port number is managed by the cluster.
+       Valid Values: ``1150-65535``
+       Default:
+        +  RDS for Db2 - ``50000``
+        +  RDS for MariaDB - ``3306``
+        +  RDS for Microsoft SQL Server - ``1433``
+        +  RDS for MySQL - ``3306``
+        +  RDS for Oracle - ``1521``
+        +  RDS for PostgreSQL - ``5432``
+        
+       Constraints:
+        +  For RDS for Microsoft SQL Server, the value can't be ``1234``, ``1434``, ``3260``, ``3343``, ``3389``, ``47001``, or ``49152-49156``.
        * @pattern `^\d*$`
        */
     Port?: string;
@@ -737,7 +745,7 @@ export type RDSDBInstanceProperties = {
        */
     StorageType?: string;
     /**
-     * An optional array of key-value pairs to apply to this DB instance.
+     * Tags to assign to the DB instance.
      */
     Tags?: Tag[];
     TdeCredentialArn?: string;
@@ -893,7 +901,7 @@ export type Tag = {
  For more information about creating a DB instance in an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide*.
  If you import an existing DB instance, and the template configuration doesn't match the actual configuration of the DB instance, AWS CloudFormation applies the changes in the template during the import operation.
   If a DB instance is deleted or replaced during an update, AWS CloudFormation deletes all automated snapshots. However, it retains manual DB snapshots. During an update that requires replacement, you can apply a stack policy to prevent DB instances from being replaced. For more information, see [Prevent Updates to Stack Resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/protect-stack-resources.html).
-    *Updating DB instances*
+   *Updating DB instances*
  When properties labeled "*Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)" are updated, AWS CloudFormation first creates a replacement DB instance, then changes references from other dependent resources to point to the replacement DB instance, and finally deletes the old DB instance.
   We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB instance. To preserve your data, perform the following procedure:
   1.  Deactivate any applications that are using the DB instance so that there's no activity on the DB instance.

package/lib/AWS-RDS-DBInstance.js

@@ -5,7 +5,7 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
  For more information about creating a DB instance in an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide*.
  If you import an existing DB instance, and the template configuration doesn't match the actual configuration of the DB instance, AWS CloudFormation applies the changes in the template during the import operation.
   If a DB instance is deleted or replaced during an update, AWS CloudFormation deletes all automated snapshots. However, it retains manual DB snapshots. During an update that requires replacement, you can apply a stack policy to prevent DB instances from being replaced. For more information, see [Prevent Updates to Stack Resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/protect-stack-resources.html).
-    *Updating DB instances*
+   *Updating DB instances*
  When properties labeled "*Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)" are updated, AWS CloudFormation first creates a replacement DB instance, then changes references from other dependent resources to point to the replacement DB instance, and finally deletes the old DB instance.
   We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB instance. To preserve your data, perform the following procedure:
   1.  Deactivate any applications that are using the DB instance so that there's no activity on the DB instance.

package/lib/AWS-RDS-DBParameterGroup.d.ts

@@ -26,27 +26,39 @@ export type RDSDBParameterGroupProperties = {
      */
     Description: string;
     /**
-       * The DB parameter group family name. A DB parameter group can be associated with one and only one DB parameter group family, and can be applied only to a DB instance running a DB engine and engine version compatible with that DB parameter group family.
-        The DB parameter group family can't be changed when updating a DB parameter group.
-        To list all of the available parameter group families, use the following command:
-        ``aws rds describe-db-engine-versions --query "DBEngineVersions[].DBParameterGroupFamily"``
-       The output contains duplicates.
-       For more information, see ``CreateDBParameterGroup``.
+       * The DB parameter group family name. A DB parameter group can be associated with one and only one DB parameter group family, and can be applied only to a DB instance running a database engine and engine version compatible with that DB parameter group family.
+       To list all of the available parameter group families for a DB engine, use the following command:
+        ``aws rds describe-db-engine-versions --query "DBEngineVersions[].DBParameterGroupFamily" --engine <engine>``
+       For example, to list all of the available parameter group families for the MySQL DB engine, use the following command:
+        ``aws rds describe-db-engine-versions --query "DBEngineVersions[].DBParameterGroupFamily" --engine mysql``
+        The output contains duplicates.
+        The following are the valid DB engine values:
+        +   ``aurora-mysql``
+        +   ``aurora-postgresql``
+        +   ``db2-ae``
+        +   ``db2-se``
+        +   ``mysql``
+        +   ``oracle-ee``
+        +   ``oracle-ee-cdb``
+        +   ``oracle-se2``
+        +   ``oracle-se2-cdb``
+        +   ``postgres``
+        +   ``sqlserver-ee``
+        +   ``sqlserver-se``
+        +   ``sqlserver-ex``
+        +   ``sqlserver-web``
        */
     Family: string;
     /**
-       * An array of parameter names and values for the parameter update. At least one parameter name and value must be supplied. Subsequent arguments are optional.
-       RDS for Db2 requires you to bring your own Db2 license. You must enter your IBM customer ID (``rds.ibm_customer_id``) and site number (``rds.ibm_site_id``) before starting a Db2 instance.
-       For more information about DB parameters and DB parameter groups for Amazon RDS DB engines, see [Working with DB Parameter Groups](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html) in the *Amazon RDS User Guide*.
-       For more information about DB cluster and DB instance parameters and parameter groups for Amazon Aurora DB engines, see [Working with DB Parameter Groups and DB Cluster Parameter Groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide*.
+       * An array of parameter names and values for the parameter update. You must specify at least one parameter name and value.
+       For more information about parameter groups, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html) in the *Amazon RDS User Guide*, or [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide*.
          AWS CloudFormation doesn't support specifying an apply method for each individual parameter. The default apply method for each parameter is used.
        */
     Parameters?: Record<string, any>;
     /**
-       * An optional array of key-value pairs to apply to this DB parameter group.
-         Currently, this is the only property that supports drift detection.
-       * @maxLength `50`
-       */
+     * Tags to assign to the DB parameter group.
+     * @maxLength `50`
+     */
     Tags?: Tag[];
 };
 /**

package/lib/AWS-RDS-DBSubnetGroup.d.ts

@@ -12,8 +12,12 @@ export type RDSDBSubnetGroupProperties = {
     DBSubnetGroupDescription: string;
     /**
        * The name for the DB subnet group. This value is stored as a lowercase string.
-       Constraints: Must contain no more than 255 lowercase alphanumeric characters or hyphens. Must not be "Default".
-       Example: ``mysubnetgroup``
+       Constraints:
+        +  Must contain no more than 255 letters, numbers, periods, underscores, spaces, or hyphens.
+        +  Must not be default.
+        +  First character must be a letter.
+        
+       Example: ``mydbsubnetgroup``
        */
     DBSubnetGroupName?: string;
     /**
@@ -21,7 +25,7 @@ export type RDSDBSubnetGroupProperties = {
      */
     SubnetIds: string[];
     /**
-     * An optional array of key-value pairs to apply to this DB subnet group.
+     * Tags to assign to the DB subnet group.
      * @maxLength `50`
      */
     Tags?: Tag[];

package/lib/AWS-RDS-EventSubscription.d.ts

@@ -21,18 +21,19 @@ export type RDSEventSubscriptionProperties = {
     /**
        * The list of identifiers of the event sources for which events are returned. If not specified, then all sources are included in the response. An identifier must begin with a letter and must contain only ASCII letters, digits, and hyphens. It can't end with a hyphen or contain two consecutive hyphens.
        Constraints:
-        +  If a ``SourceIds`` value is supplied, ``SourceType`` must also be provided.
+        +  If ``SourceIds`` are supplied, ``SourceType`` must also be provided.
         +  If the source type is a DB instance, a ``DBInstanceIdentifier`` value must be supplied.
         +  If the source type is a DB cluster, a ``DBClusterIdentifier`` value must be supplied.
         +  If the source type is a DB parameter group, a ``DBParameterGroupName`` value must be supplied.
         +  If the source type is a DB security group, a ``DBSecurityGroupName`` value must be supplied.
         +  If the source type is a DB snapshot, a ``DBSnapshotIdentifier`` value must be supplied.
         +  If the source type is a DB cluster snapshot, a ``DBClusterSnapshotIdentifier`` value must be supplied.
+        +  If the source type is an RDS Proxy, a ``DBProxyName`` value must be supplied.
        */
     SourceIds?: string[];
     /**
-       * The type of source that is generating the events. For example, if you want to be notified of events generated by a DB instance, set this parameter to ``db-instance``. If this value isn't specified, all events are returned.
-       Valid values: ``db-instance`` | ``db-cluster`` | ``db-parameter-group`` | ``db-security-group`` | ``db-snapshot`` | ``db-cluster-snapshot``
+       * The type of source that is generating the events. For example, if you want to be notified of events generated by a DB instance, you set this parameter to ``db-instance``. For RDS Proxy events, specify ``db-proxy``. If this value isn't specified, all events are returned.
+       Valid Values:``db-instance | db-cluster | db-parameter-group | db-security-group | db-snapshot | db-cluster-snapshot | db-proxy | zero-etl | custom-engine-version | blue-green-deployment``
        */
     SourceType?: string;
     /**

package/lib/AWS-RDS-OptionGroup.d.ts

@@ -26,7 +26,7 @@ export type RDSOptionGroupProperties = {
      */
     MajorEngineVersion: string;
     /**
-     * A list of options and the settings for each option.
+     * A list of all available options
      */
     OptionConfigurations?: OptionConfiguration[];
     /**
@@ -46,7 +46,7 @@ export type RDSOptionGroupProperties = {
        */
     OptionGroupName?: string;
     /**
-     * An optional array of key-value pairs to apply to this option group.
+     * Tags to assign to the option group.
      */
     Tags?: Tag[];
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awboost/cfn-resource-types",
-  "version": "0.1.123",
+  "version": "0.1.124",
   "publishConfig": {
     "access": "public"
   },