@awboost/cfn-resource-types 0.1.318 → 0.1.319

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

@@ -3,7 +3,7 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
 /**
  * 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).
+  +  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 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}
@@ -18,8 +18,8 @@ export type DynamoDBTableProperties = {
     /**
        * Specify how you are charged for read and write throughput and how you manage capacity.
        Valid values include:
-        +   ``PAY_PER_REQUEST`` - We recommend using ``PAY_PER_REQUEST`` for most DynamoDB workloads. ``PAY_PER_REQUEST`` sets the billing mode to [On-demand capacity mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html).
-        +   ``PROVISIONED`` - We recommend using ``PROVISIONED`` for steady workloads with predictable growth where capacity requirements can be reliably forecasted. ``PROVISIONED`` sets the billing mode to [Provisioned capacity mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html).
+        +  ``PAY_PER_REQUEST`` - We recommend using ``PAY_PER_REQUEST`` for most DynamoDB workloads. ``PAY_PER_REQUEST`` sets the billing mode to [On-demand capacity mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html).
+        +  ``PROVISIONED`` - We recommend using ``PROVISIONED`` for steady workloads with predictable growth where capacity requirements can be reliably forecasted. ``PROVISIONED`` sets the billing mode to [Provisioned capacity mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html).
         
        If not specified, the default is ``PROVISIONED``.
        */
@@ -128,9 +128,9 @@ export type AttributeDefinition = {
     AttributeName: string;
     /**
        * The data type for the attribute, where:
-        +   ``S`` - the attribute is of type String
-        +   ``N`` - the attribute is of type Number
-        +   ``B`` - the attribute is of type Binary
+        +  ``S`` - the attribute is of type String
+        +  ``N`` - the attribute is of type Number
+        +  ``B`` - the attribute is of type Binary
        */
     AttributeType: string;
 };
@@ -176,8 +176,8 @@ export type GlobalSecondaryIndex = {
     IndexName: string;
     /**
        * The complete key schema for a global secondary index, which consists of one or more pairs of attribute names and key types:
-        +   ``HASH`` - partition key
-        +   ``RANGE`` - sort key
+        +  ``HASH`` - partition key
+        +  ``RANGE`` - sort key
         
         The partition key of an item is also known as its *hash attribute*. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values.
        The sort key of an item is also known as its *range attribute*. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
@@ -249,8 +249,8 @@ export type KeySchema = {
     AttributeName: string;
     /**
        * The role that this key attribute will assume:
-        +   ``HASH`` - partition key
-        +   ``RANGE`` - sort key
+        +  ``HASH`` - partition key
+        +  ``RANGE`` - sort key
         
         The partition key of an item is also known as its *hash attribute*. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values.
        The sort key of an item is also known as its *range attribute*. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
@@ -285,8 +285,8 @@ export type LocalSecondaryIndex = {
     IndexName: string;
     /**
        * The complete key schema for the local secondary index, consisting of one or more pairs of attribute names and key types:
-        +   ``HASH`` - partition key
-        +   ``RANGE`` - sort key
+        +  ``HASH`` - partition key
+        +  ``RANGE`` - sort key
         
         The partition key of an item is also known as its *hash attribute*. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values.
        The sort key of an item is also known as its *range attribute*. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
@@ -346,9 +346,9 @@ export type Projection = {
     NonKeyAttributes?: string[];
     /**
        * The set of attributes that are projected into the index:
-        +   ``KEYS_ONLY`` - Only the index and primary keys are projected into the index.
-        +   ``INCLUDE`` - In addition to the attributes described in ``KEYS_ONLY``, the secondary index will include other non-key attributes that you specify.
-        +   ``ALL`` - All of the table attributes are projected into the index.
+        +  ``KEYS_ONLY`` - Only the index and primary keys are projected into the index.
+        +  ``INCLUDE`` - In addition to the attributes described in ``KEYS_ONLY``, the secondary index will include other non-key attributes that you specify.
+        +  ``ALL`` - All of the table attributes are projected into the index.
         
        When using the DynamoDB console, ``ALL`` is selected by default.
        */
@@ -426,7 +426,7 @@ export type SSESpecification = {
     SSEEnabled: boolean;
     /**
        * Server-side encryption type. The only supported value is:
-        +   ``KMS`` - Server-side encryption that uses KMSlong. The key is stored in your account and is managed by KMS (KMS charges apply).
+        +  ``KMS`` - Server-side encryption that uses KMSlong. The key is stored in your account and is managed by KMS (KMS charges apply).
        */
     SSEType?: string;
 };
@@ -443,17 +443,17 @@ export type StreamSpecification = {
     ResourcePolicy?: ResourcePolicy;
     /**
        * When an item in the table is modified, ``StreamViewType`` determines what information is written to the stream for this table. Valid values for ``StreamViewType`` are:
-        +   ``KEYS_ONLY`` - Only the key attributes of the modified item are written to the stream.
-        +   ``NEW_IMAGE`` - The entire item, as it appears after it was modified, is written to the stream.
-        +   ``OLD_IMAGE`` - The entire item, as it appeared before it was modified, is written to the stream.
-        +   ``NEW_AND_OLD_IMAGES`` - Both the new and the old item images of the item are written to the stream.
+        +  ``KEYS_ONLY`` - Only the key attributes of the modified item are written to the stream.
+        +  ``NEW_IMAGE`` - The entire item, as it appears after it was modified, is written to the stream.
+        +  ``OLD_IMAGE`` - The entire item, as it appeared before it was modified, is written to the stream.
+        +  ``NEW_AND_OLD_IMAGES`` - Both the new and the old item images of the item are written to the stream.
        */
     StreamViewType: string;
 };
 /**
  * Type definition for `AWS::DynamoDB::Table.Tag`.
  * Describes a tag. A tag is a key-value pair. You can add up to 50 tags to a single DynamoDB table.
-  AWS-assigned tag names and values are automatically assigned the ``aws:`` prefix, which the user cannot assign. AWS-assigned tag names do not count towards the tag limit of 50. User-assigned tag names have the prefix ``user:`` in the Cost Allocation Report. You cannot backdate the application of a tag.
+ AWS-assigned tag names and values are automatically assigned the ``aws:`` prefix, which the user cannot assign. AWS-assigned tag names do not count towards the tag limit of 50. User-assigned tag names have the prefix ``user:`` in the Cost Allocation Report. You cannot backdate the application of a tag.
  For an overview on tagging DynamoDB resources, see [Tagging for DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-dynamodb-table-tag.html}
  */
@@ -504,7 +504,7 @@ export type WarmThroughput = {
 /**
  * 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).
+  +  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 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}

package/lib/AWS-DynamoDB-Table.js

@@ -2,7 +2,7 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
 /**
  * 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).
+  +  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 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}

package/lib/AWS-MediaPackageV2-OriginEndpoint.d.ts

@@ -299,11 +299,11 @@ export type FilterConfiguration = {
  */
 export type ForceEndpointErrorConfiguration = {
     /**
-       * <p>The failover settings for the endpoint. The options are:</p>
+       * <p>The failover conditions for the endpoint. The options are:</p>
                <ul>
                   <li>
                      <p>
-                        <code>STALE_MANIFEST</code> - The manifest stalled and there a no new segments or parts.</p>
+                        <code>STALE_MANIFEST</code> - The manifest stalled and there are no new segments or parts.</p>
                   </li>
                   <li>
                      <p>
@@ -313,6 +313,10 @@ export type ForceEndpointErrorConfiguration = {
                      <p>
                         <code>MISSING_DRM_KEY</code> - Key rotation is enabled but we're unable to fetch the key for the current key period.</p>
                   </li>
+                  <li>
+                     <p>
+                        <code>SLATE_INPUT</code> - The segments which contain slate content are considered to be missing content.</p>
+                  </li>
                </ul>
        */
     EndpointErrorConditions?: EndpointErrorCondition[];
@@ -348,8 +352,7 @@ export type HlsManifestConfiguration = {
     /**
        * <p>Inserts EXT-X-PROGRAM-DATE-TIME tags in the output manifest at the interval that you specify. If you don't enter an interval,
                EXT-X-PROGRAM-DATE-TIME tags aren't included in the manifest.
-               The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.
-               ID3Timed metadata messages generate every 5 seconds whenever the content is ingested.</p>
+               The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.</p>
                <p>Irrespective of this parameter, if any ID3Timed metadata is in the HLS input, it is passed through to the HLS output.</p>
        */
     ProgramDateTimeIntervalSeconds?: number;
@@ -361,6 +364,11 @@ export type HlsManifestConfiguration = {
      * <p>To insert an EXT-X-START tag in your HLS playlist, specify a StartTag configuration object with a valid TimeOffset. When you do, you can also optionally specify whether to include a PRECISE value in the EXT-X-START tag.</p>
      */
     StartTag?: StartTag;
+    /**
+       * <p>When enabled, MediaPackage URL-encodes the query string for API requests for HLS child manifests to comply with Amazon Web Services Signature Version 4 (SigV4) signature signing protocol.
+               For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html">Amazon Web Services Signature Version 4 for API requests</a> in <i>Identity and Access Management User Guide</i>.</p>
+       */
+    UrlEncodeChildManifest?: boolean;
 };
 /**
  * Type definition for `AWS::MediaPackageV2::OriginEndpoint.LowLatencyHlsManifestConfiguration`.
@@ -393,8 +401,7 @@ export type LowLatencyHlsManifestConfiguration = {
     /**
        * <p>Inserts EXT-X-PROGRAM-DATE-TIME tags in the output manifest at the interval that you specify. If you don't enter an interval,
                EXT-X-PROGRAM-DATE-TIME tags aren't included in the manifest.
-               The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.
-               ID3Timed metadata messages generate every 5 seconds whenever the content is ingested.</p>
+               The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player.</p>
                <p>Irrespective of this parameter, if any ID3Timed metadata is in the HLS input, it is passed through to the HLS output.</p>
        */
     ProgramDateTimeIntervalSeconds?: number;
@@ -406,6 +413,11 @@ export type LowLatencyHlsManifestConfiguration = {
      * <p>To insert an EXT-X-START tag in your HLS playlist, specify a StartTag configuration object with a valid TimeOffset. When you do, you can also optionally specify whether to include a PRECISE value in the EXT-X-START tag.</p>
      */
     StartTag?: StartTag;
+    /**
+       * <p>When enabled, MediaPackage URL-encodes the query string for API requests for LL-HLS child manifests to comply with Amazon Web Services Signature Version 4 (SigV4) signature signing protocol.
+               For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html">Amazon Web Services Signature Version 4 for API requests</a> in <i>Identity and Access Management User Guide</i>.</p>
+       */
+    UrlEncodeChildManifest?: boolean;
 };
 /**
  * Type definition for `AWS::MediaPackageV2::OriginEndpoint.PresetSpeke20Audio`.

package/lib/AWS-Route53Resolver-ResolverRule.d.ts

@@ -5,6 +5,12 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-route53resolver-resolverrule.html}
  */
 export type Route53ResolverResolverRuleProperties = {
+    /**
+     * The name server domain for queries to be delegated to if a query matches the delegation record.
+     * @minLength `1`
+     * @maxLength `256`
+     */
+    DelegationRecord?: string;
     /**
      * DNS queries for this domain name are forwarded to the IP addresses that are specified in TargetIps
      * @minLength `1`

package/package.json

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