From 4a3e848775ccf4d2792365f9a80e671d06152dc5 Mon Sep 17 00:00:00 2001
From: awstools <awstools@amazon.com>
Date: Fri, 2 Feb 2024 19:13:06 +0000
Subject: [PATCH] docs(client-dynamodb): Any number of users can execute up to
 50 concurrent restores (any type of restore) in a given account.

---
 .../src/commands/RestoreTableToPointInTimeCommand.ts        | 6 +++---
 clients/client-dynamodb/src/models/models_0.ts              | 4 ++--
 codegen/sdk-codegen/aws-models/dynamodb.json                | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/clients/client-dynamodb/src/commands/RestoreTableToPointInTimeCommand.ts b/clients/client-dynamodb/src/commands/RestoreTableToPointInTimeCommand.ts
index 1e65be9369c2..67bb586ddfec 100644
--- a/clients/client-dynamodb/src/commands/RestoreTableToPointInTimeCommand.ts
+++ b/clients/client-dynamodb/src/commands/RestoreTableToPointInTimeCommand.ts
@@ -31,10 +31,10 @@ export interface RestoreTableToPointInTimeCommandOutput extends RestoreTableToPo
  * <p>Restores the specified table to the specified point in time within
  *                 <code>EarliestRestorableDateTime</code> and <code>LatestRestorableDateTime</code>.
  *             You can restore your table to any point in time during the last 35 days. Any number of
- *             users can execute up to 4 concurrent restores (any type of restore) in a given account. </p>
- *          <p> When you restore using point in time recovery, DynamoDB restores your table data to
+ *             users can execute up to 50 concurrent restores (any type of restore) in a given account. </p>
+ *          <p>When you restore using point in time recovery, DynamoDB restores your table data to
  *             the state based on the selected date and time (day:hour:minute:second) to a new table. </p>
- *          <p> Along with data, the following are also included on the new restored table using
+ *          <p>Along with data, the following are also included on the new restored table using
  *             point in time recovery: </p>
  *          <ul>
  *             <li>
diff --git a/clients/client-dynamodb/src/models/models_0.ts b/clients/client-dynamodb/src/models/models_0.ts
index 679c3d30f1c4..61bbef07b006 100644
--- a/clients/client-dynamodb/src/models/models_0.ts
+++ b/clients/client-dynamodb/src/models/models_0.ts
@@ -6736,8 +6736,8 @@ export interface UpdateTableInput {
    * @public
    * <p>Represents the DynamoDB Streams configuration for the table.</p>
    *          <note>
-   *             <p>You receive a <code>ResourceInUseException</code> if you try to enable a stream on
-   *                 a table that already has a stream, or if you try to disable a stream on a table that
+   *             <p>You receive a <code>ValidationException</code> if you try to enable a stream on a
+   *                 table that already has a stream, or if you try to disable a stream on a table that
    *                 doesn't have a stream.</p>
    *          </note>
    */
diff --git a/codegen/sdk-codegen/aws-models/dynamodb.json b/codegen/sdk-codegen/aws-models/dynamodb.json
index d1a4c4d88c5e..4fecd48f1aa9 100644
--- a/codegen/sdk-codegen/aws-models/dynamodb.json
+++ b/codegen/sdk-codegen/aws-models/dynamodb.json
@@ -9447,7 +9447,7 @@
         "aws.api#clientDiscoveredEndpoint": {
           "required": false
         },
-        "smithy.api#documentation": "<p>Restores the specified table to the specified point in time within\n                <code>EarliestRestorableDateTime</code> and <code>LatestRestorableDateTime</code>.\n            You can restore your table to any point in time during the last 35 days. Any number of\n            users can execute up to 4 concurrent restores (any type of restore) in a given account. </p>\n         <p> When you restore using point in time recovery, DynamoDB restores your table data to\n            the state based on the selected date and time (day:hour:minute:second) to a new table. </p>\n         <p> Along with data, the following are also included on the new restored table using\n            point in time recovery: </p>\n         <ul>\n            <li>\n               <p>Global secondary indexes (GSIs)</p>\n            </li>\n            <li>\n               <p>Local secondary indexes (LSIs)</p>\n            </li>\n            <li>\n               <p>Provisioned read and write capacity</p>\n            </li>\n            <li>\n               <p>Encryption settings</p>\n               <important>\n                  <p> All these settings come from the current settings of the source table at\n                        the time of restore. </p>\n               </important>\n            </li>\n         </ul>\n         <p>You must manually set up the following on the restored table:</p>\n         <ul>\n            <li>\n               <p>Auto scaling policies</p>\n            </li>\n            <li>\n               <p>IAM policies</p>\n            </li>\n            <li>\n               <p>Amazon CloudWatch metrics and alarms</p>\n            </li>\n            <li>\n               <p>Tags</p>\n            </li>\n            <li>\n               <p>Stream settings</p>\n            </li>\n            <li>\n               <p>Time to Live (TTL) settings</p>\n            </li>\n            <li>\n               <p>Point in time recovery settings</p>\n            </li>\n         </ul>"
+        "smithy.api#documentation": "<p>Restores the specified table to the specified point in time within\n                <code>EarliestRestorableDateTime</code> and <code>LatestRestorableDateTime</code>.\n            You can restore your table to any point in time during the last 35 days. Any number of\n            users can execute up to 50 concurrent restores (any type of restore) in a given account. </p>\n         <p>When you restore using point in time recovery, DynamoDB restores your table data to\n            the state based on the selected date and time (day:hour:minute:second) to a new table. </p>\n         <p>Along with data, the following are also included on the new restored table using\n            point in time recovery: </p>\n         <ul>\n            <li>\n               <p>Global secondary indexes (GSIs)</p>\n            </li>\n            <li>\n               <p>Local secondary indexes (LSIs)</p>\n            </li>\n            <li>\n               <p>Provisioned read and write capacity</p>\n            </li>\n            <li>\n               <p>Encryption settings</p>\n               <important>\n                  <p> All these settings come from the current settings of the source table at\n                        the time of restore. </p>\n               </important>\n            </li>\n         </ul>\n         <p>You must manually set up the following on the restored table:</p>\n         <ul>\n            <li>\n               <p>Auto scaling policies</p>\n            </li>\n            <li>\n               <p>IAM policies</p>\n            </li>\n            <li>\n               <p>Amazon CloudWatch metrics and alarms</p>\n            </li>\n            <li>\n               <p>Tags</p>\n            </li>\n            <li>\n               <p>Stream settings</p>\n            </li>\n            <li>\n               <p>Time to Live (TTL) settings</p>\n            </li>\n            <li>\n               <p>Point in time recovery settings</p>\n            </li>\n         </ul>"
       }
     },
     "com.amazonaws.dynamodb#RestoreTableToPointInTimeInput": {
@@ -12006,7 +12006,7 @@
         "StreamSpecification": {
           "target": "com.amazonaws.dynamodb#StreamSpecification",
           "traits": {
-            "smithy.api#documentation": "<p>Represents the DynamoDB Streams configuration for the table.</p>\n         <note>\n            <p>You receive a <code>ResourceInUseException</code> if you try to enable a stream on\n                a table that already has a stream, or if you try to disable a stream on a table that\n                doesn't have a stream.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Represents the DynamoDB Streams configuration for the table.</p>\n         <note>\n            <p>You receive a <code>ValidationException</code> if you try to enable a stream on a\n                table that already has a stream, or if you try to disable a stream on a table that\n                doesn't have a stream.</p>\n         </note>"
           }
         },
         "SSESpecification": {