@aws-sdk/client-dynamodb 3.289.0 → 3.292.0

package/dist-types/commands/TransactWriteItemsCommand.d.ts

@@ -101,6 +101,329 @@ export interface TransactWriteItemsCommandOutput extends TransactWriteItemsOutpu
  * @see {@link TransactWriteItemsCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link IdempotentParameterMismatchException} (client fault)
+ *  <p>DynamoDB rejected the request because you retried a request with a
+ *             different payload but with an idempotent token that was already used.</p>
+ *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link ProvisionedThroughputExceededException} (client fault)
+ *  <p>Your request rate is too high. The Amazon Web Services SDKs for DynamoDB
+ *             automatically retry requests that receive this exception. Your request is eventually
+ *             successful, unless your retry queue is too large to finish. Reduce the frequency of
+ *             requests and use exponential backoff. For more information, go to <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html#Programming.Errors.RetryAndBackoff">Error Retries and Exponential Backoff</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
+ *
+ * @throws {@link RequestLimitExceeded} (client fault)
+ *  <p>Throughput exceeds the current throughput quota for your account. Please contact
+ *                 <a href="https://aws.amazon.com/support">Amazon Web Services Support</a> to request a
+ *             quota increase.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ * @throws {@link TransactionCanceledException} (client fault)
+ *  <p>The entire transaction request was canceled.</p>
+ *          <p>DynamoDB cancels a <code>TransactWriteItems</code> request under the following
+ *             circumstances:</p>
+ *          <ul>
+ *             <li>
+ *                <p>A condition in one of the condition expressions is not met.</p>
+ *             </li>
+ *             <li>
+ *                <p>A table in the <code>TransactWriteItems</code> request is in a different
+ *                     account or region.</p>
+ *             </li>
+ *             <li>
+ *                <p>More than one action in the <code>TransactWriteItems</code> operation
+ *                     targets the same item.</p>
+ *             </li>
+ *             <li>
+ *                <p>There is insufficient provisioned capacity for the transaction to be
+ *                     completed.</p>
+ *             </li>
+ *             <li>
+ *                <p>An item size becomes too large (larger than 400 KB), or a local secondary
+ *                     index (LSI) becomes too large, or a similar validation error occurs because of
+ *                     changes made by the transaction.</p>
+ *             </li>
+ *             <li>
+ *                <p>There is a user error, such as an invalid data format.</p>
+ *             </li>
+ *          </ul>
+ *          <p>DynamoDB cancels a <code>TransactGetItems</code> request under the
+ *             following circumstances:</p>
+ *          <ul>
+ *             <li>
+ *                <p>There is an ongoing <code>TransactGetItems</code> operation that conflicts
+ *                     with a concurrent <code>PutItem</code>, <code>UpdateItem</code>,
+ *                         <code>DeleteItem</code> or <code>TransactWriteItems</code> request. In this
+ *                     case the <code>TransactGetItems</code> operation fails with a
+ *                         <code>TransactionCanceledException</code>.</p>
+ *             </li>
+ *             <li>
+ *                <p>A table in the <code>TransactGetItems</code> request is in a different
+ *                     account or region.</p>
+ *             </li>
+ *             <li>
+ *                <p>There is insufficient provisioned capacity for the transaction to be
+ *                     completed.</p>
+ *             </li>
+ *             <li>
+ *                <p>There is a user error, such as an invalid data format.</p>
+ *             </li>
+ *          </ul>
+ *          <note>
+ *             <p>If using Java, DynamoDB lists the cancellation reasons on the
+ *                     <code>CancellationReasons</code> property. This property is not set for other
+ *                 languages. Transaction cancellation reasons are ordered in the order of requested
+ *                 items, if an item has no error it will have <code>None</code> code and
+ *                     <code>Null</code> message.</p>
+ *          </note>
+ *          <p>Cancellation reason codes and possible error messages:</p>
+ *          <ul>
+ *             <li>
+ *                <p>No Errors:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>None</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Message: <code>null</code>
+ *                      </p>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *             <li>
+ *                <p>Conditional Check Failed:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>ConditionalCheckFailed</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Message: The conditional request failed. </p>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *             <li>
+ *                <p>Item Collection Size Limit Exceeded:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>ItemCollectionSizeLimitExceeded</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Message: Collection size exceeded.</p>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *             <li>
+ *                <p>Transaction Conflict:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>TransactionConflict</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Message: Transaction is ongoing for the item.</p>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *             <li>
+ *                <p>Provisioned Throughput Exceeded:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>ProvisionedThroughputExceeded</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Messages:</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>The level of configured provisioned throughput for the
+ *                                     table was exceeded. Consider increasing your provisioning level
+ *                                     with the UpdateTable API.</p>
+ *                            <note>
+ *                               <p>This Message is received when provisioned throughput is
+ *                                         exceeded is on a provisioned DynamoDB
+ *                                         table.</p>
+ *                            </note>
+ *                         </li>
+ *                         <li>
+ *                            <p>The level of configured provisioned throughput for one or
+ *                                     more global secondary indexes of the table was exceeded.
+ *                                     Consider increasing your provisioning level for the
+ *                                     under-provisioned global secondary indexes with the UpdateTable
+ *                                     API.</p>
+ *                            <note>
+ *                               <p>This message is returned when provisioned throughput is
+ *                                         exceeded is on a provisioned GSI.</p>
+ *                            </note>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *             <li>
+ *                <p>Throttling Error:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>ThrottlingError</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Messages: </p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>Throughput exceeds the current capacity of your table or
+ *                                     index. DynamoDB is automatically scaling your table or
+ *                                     index so please try again shortly. If exceptions persist, check
+ *                                     if you have a hot key:
+ *                                     https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.</p>
+ *                            <note>
+ *                               <p>This message is returned when writes get throttled on an
+ *                                         On-Demand table as DynamoDB is automatically
+ *                                         scaling the table.</p>
+ *                            </note>
+ *                         </li>
+ *                         <li>
+ *                            <p>Throughput exceeds the current capacity for one or more
+ *                                     global secondary indexes. DynamoDB is automatically
+ *                                     scaling your index so please try again shortly.</p>
+ *                            <note>
+ *                               <p>This message is returned when writes get throttled on
+ *                                         an On-Demand GSI as DynamoDB is automatically
+ *                                         scaling the GSI.</p>
+ *                            </note>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *             <li>
+ *                <p>Validation Error:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Code: <code>ValidationError</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Messages: </p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>One or more parameter values were invalid.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>The update expression attempted to update the secondary
+ *                                     index key beyond allowed size limits.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>The update expression attempted to update the secondary
+ *                                     index key to unsupported type.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>An operand in the update expression has an incorrect data
+ *                                     type.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Item size to update has exceeded the maximum allowed
+ *                                     size.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Number overflow. Attempting to store a number with
+ *                                     magnitude larger than supported range.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Type mismatch for attribute to update.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Nesting Levels have exceeded supported limits.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>The document path provided in the update expression is
+ *                                     invalid for update.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>The provided expression refers to an attribute that does
+ *                                     not exist in the item.</p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
+ *             </li>
+ *          </ul>
+ *
+ * @throws {@link TransactionInProgressException} (client fault)
+ *  <p>The transaction with the given request token is already in progress.</p>
+ *          <p>
+ *             Recommended Settings
+ *         </p>
+ *          <note>
+ *             <p>
+ *                 This is a general recommendation for handling the <code>TransactionInProgressException</code>. These settings help
+ *                 ensure that the client retries will trigger completion of the ongoing <code>TransactWriteItems</code> request.
+ *             </p>
+ *          </note>
+ *          <ul>
+ *             <li>
+ *                <p>
+ *                     Set <code>clientExecutionTimeout</code> to a value that allows at least one retry to be processed after 5
+ *                     seconds have elapsed since the first attempt for the <code>TransactWriteItems</code> operation.
+ *                 </p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                     Set <code>socketTimeout</code> to a value a little lower than the <code>requestTimeout</code> setting.
+ *                 </p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <code>requestTimeout</code> should be set based on the time taken for the individual retries of a single
+ *                     HTTP request for your use case, but setting it to 1 second or higher should work well to reduce chances of
+ *                     retries and <code>TransactionInProgressException</code> errors.
+ *                 </p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                     Use exponential backoff when retrying and tune backoff if needed.
+ *                 </p>
+ *             </li>
+ *          </ul>
+ *          <p>
+ *             Assuming <a href="https://github.com/aws/aws-sdk-java/blob/fd409dee8ae23fb8953e0bb4dbde65536a7e0514/aws-java-sdk-core/src/main/java/com/amazonaws/retry/PredefinedRetryPolicies.java#L97">default retry policy</a>,
+ *             example timeout settings based on the guidelines above are as follows:
+ *         </p>
+ *          <p>Example timeline:</p>
+ *          <ul>
+ *             <li>
+ *                <p>0-1000 first attempt</p>
+ *             </li>
+ *             <li>
+ *                <p>1000-1500 first sleep/delay (default retry policy uses 500 ms as base delay for 4xx errors)</p>
+ *             </li>
+ *             <li>
+ *                <p>1500-2500 second attempt</p>
+ *             </li>
+ *             <li>
+ *                <p>2500-3500 second sleep/delay (500 * 2, exponential backoff)</p>
+ *             </li>
+ *             <li>
+ *                <p>3500-4500 third attempt</p>
+ *             </li>
+ *             <li>
+ *                <p>4500-6500 third sleep/delay (500 * 2^2)</p>
+ *             </li>
+ *             <li>
+ *                <p>6500-7500 fourth attempt (this can trigger inline recovery since 5 seconds have elapsed since the first attempt reached TC)</p>
+ *             </li>
+ *          </ul>
+ *
+ *
  */
 export declare class TransactWriteItemsCommand extends $Command<TransactWriteItemsCommandInput, TransactWriteItemsCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: TransactWriteItemsCommandInput;

package/dist-types/commands/UntagResourceCommand.d.ts

@@ -32,6 +32,34 @@ export interface UntagResourceCommandOutput extends __MetadataBearer {
  * @see {@link UntagResourceCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link LimitExceededException} (client fault)
+ *  <p>There is no limit to the number of daily on-demand backups that can be taken. </p>
+ *          <p>For most purposes, up to 500 simultaneous table operations are allowed per account. These operations
+ *             include <code>CreateTable</code>, <code>UpdateTable</code>,
+ *                 <code>DeleteTable</code>,<code>UpdateTimeToLive</code>,
+ *                 <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p>
+ *          <p>When you are creating a table with one or more secondary
+ *             indexes, you can have up to 250 such requests running at a time. However, if the table or
+ *             index specifications are complex, then DynamoDB might temporarily reduce the number
+ *             of concurrent operations.</p>
+ *          <p>When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.</p>
+ *          <p>There is a soft account quota of 2,500 tables.</p>
+ *
+ * @throws {@link ResourceInUseException} (client fault)
+ *  <p>The operation conflicts with the resource's availability. For example, you
+ *             attempted to recreate an existing table, or tried to delete a table currently in the
+ *                 <code>CREATING</code> state.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ *
  */
 export declare class UntagResourceCommand extends $Command<UntagResourceCommandInput, UntagResourceCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UntagResourceCommandInput;

package/dist-types/commands/UpdateContinuousBackupsCommand.d.ts

@@ -40,6 +40,19 @@ export interface UpdateContinuousBackupsCommandOutput extends UpdateContinuousBa
  * @see {@link UpdateContinuousBackupsCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link ContinuousBackupsUnavailableException} (client fault)
+ *  <p>Backups have not yet been enabled for this table.</p>
+ *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link TableNotFoundException} (client fault)
+ *  <p>A source table with the name <code>TableName</code> does not currently exist within
+ *             the subscriber's account or the subscriber is operating in the wrong Amazon Web Services Region.</p>
+ *
+ *
  */
 export declare class UpdateContinuousBackupsCommand extends $Command<UpdateContinuousBackupsCommandInput, UpdateContinuousBackupsCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UpdateContinuousBackupsCommandInput;

package/dist-types/commands/UpdateContributorInsightsCommand.d.ts

@@ -35,6 +35,14 @@ export interface UpdateContributorInsightsCommandOutput extends UpdateContributo
  * @see {@link UpdateContributorInsightsCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ *
  */
 export declare class UpdateContributorInsightsCommand extends $Command<UpdateContributorInsightsCommandInput, UpdateContributorInsightsCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UpdateContributorInsightsCommandInput;

package/dist-types/commands/UpdateGlobalTableCommand.d.ts

@@ -71,6 +71,25 @@ export interface UpdateGlobalTableCommandOutput extends UpdateGlobalTableOutput,
  * @see {@link UpdateGlobalTableCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link GlobalTableNotFoundException} (client fault)
+ *  <p>The specified global table does not exist.</p>
+ *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link ReplicaAlreadyExistsException} (client fault)
+ *  <p>The specified replica is already part of the global table.</p>
+ *
+ * @throws {@link ReplicaNotFoundException} (client fault)
+ *  <p>The specified replica is no longer part of the global table.</p>
+ *
+ * @throws {@link TableNotFoundException} (client fault)
+ *  <p>A source table with the name <code>TableName</code> does not currently exist within
+ *             the subscriber's account or the subscriber is operating in the wrong Amazon Web Services Region.</p>
+ *
+ *
  */
 export declare class UpdateGlobalTableCommand extends $Command<UpdateGlobalTableCommandInput, UpdateGlobalTableCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UpdateGlobalTableCommandInput;

package/dist-types/commands/UpdateGlobalTableSettingsCommand.d.ts

@@ -41,6 +41,39 @@ export interface UpdateGlobalTableSettingsCommandOutput extends UpdateGlobalTabl
  * @see {@link UpdateGlobalTableSettingsCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link GlobalTableNotFoundException} (client fault)
+ *  <p>The specified global table does not exist.</p>
+ *
+ * @throws {@link IndexNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent index.</p>
+ *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link LimitExceededException} (client fault)
+ *  <p>There is no limit to the number of daily on-demand backups that can be taken. </p>
+ *          <p>For most purposes, up to 500 simultaneous table operations are allowed per account. These operations
+ *             include <code>CreateTable</code>, <code>UpdateTable</code>,
+ *                 <code>DeleteTable</code>,<code>UpdateTimeToLive</code>,
+ *                 <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p>
+ *          <p>When you are creating a table with one or more secondary
+ *             indexes, you can have up to 250 such requests running at a time. However, if the table or
+ *             index specifications are complex, then DynamoDB might temporarily reduce the number
+ *             of concurrent operations.</p>
+ *          <p>When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.</p>
+ *          <p>There is a soft account quota of 2,500 tables.</p>
+ *
+ * @throws {@link ReplicaNotFoundException} (client fault)
+ *  <p>The specified replica is no longer part of the global table.</p>
+ *
+ * @throws {@link ResourceInUseException} (client fault)
+ *  <p>The operation conflicts with the resource's availability. For example, you
+ *             attempted to recreate an existing table, or tried to delete a table currently in the
+ *                 <code>CREATING</code> state.</p>
+ *
+ *
  */
 export declare class UpdateGlobalTableSettingsCommand extends $Command<UpdateGlobalTableSettingsCommandInput, UpdateGlobalTableSettingsCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UpdateGlobalTableSettingsCommandInput;

package/dist-types/commands/UpdateItemCommand.d.ts

@@ -35,6 +35,38 @@ export interface UpdateItemCommandOutput extends UpdateItemOutput, __MetadataBea
  * @see {@link UpdateItemCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link ConditionalCheckFailedException} (client fault)
+ *  <p>A condition specified in the operation could not be evaluated.</p>
+ *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link ItemCollectionSizeLimitExceededException} (client fault)
+ *  <p>An item collection is too large. This exception is only returned for tables that
+ *             have one or more local secondary indexes.</p>
+ *
+ * @throws {@link ProvisionedThroughputExceededException} (client fault)
+ *  <p>Your request rate is too high. The Amazon Web Services SDKs for DynamoDB
+ *             automatically retry requests that receive this exception. Your request is eventually
+ *             successful, unless your retry queue is too large to finish. Reduce the frequency of
+ *             requests and use exponential backoff. For more information, go to <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html#Programming.Errors.RetryAndBackoff">Error Retries and Exponential Backoff</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
+ *
+ * @throws {@link RequestLimitExceeded} (client fault)
+ *  <p>Throughput exceeds the current throughput quota for your account. Please contact
+ *                 <a href="https://aws.amazon.com/support">Amazon Web Services Support</a> to request a
+ *             quota increase.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ * @throws {@link TransactionConflictException} (client fault)
+ *  <p>Operation was rejected because there is an ongoing transaction for the
+ *             item.</p>
+ *
+ *
  * @example To update an item in a table
  * ```javascript
  * // This example updates an item in the Music table. It adds a new attribute (Year) and modifies the AlbumTitle attribute.  All of the attributes in the item, as they appear after the update, are returned in the response.

package/dist-types/commands/UpdateTableCommand.d.ts

@@ -55,6 +55,34 @@ export interface UpdateTableCommandOutput extends UpdateTableOutput, __MetadataB
  * @see {@link UpdateTableCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link LimitExceededException} (client fault)
+ *  <p>There is no limit to the number of daily on-demand backups that can be taken. </p>
+ *          <p>For most purposes, up to 500 simultaneous table operations are allowed per account. These operations
+ *             include <code>CreateTable</code>, <code>UpdateTable</code>,
+ *                 <code>DeleteTable</code>,<code>UpdateTimeToLive</code>,
+ *                 <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p>
+ *          <p>When you are creating a table with one or more secondary
+ *             indexes, you can have up to 250 such requests running at a time. However, if the table or
+ *             index specifications are complex, then DynamoDB might temporarily reduce the number
+ *             of concurrent operations.</p>
+ *          <p>When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.</p>
+ *          <p>There is a soft account quota of 2,500 tables.</p>
+ *
+ * @throws {@link ResourceInUseException} (client fault)
+ *  <p>The operation conflicts with the resource's availability. For example, you
+ *             attempted to recreate an existing table, or tried to delete a table currently in the
+ *                 <code>CREATING</code> state.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ *
  * @example To modify a table's provisioned throughput
  * ```javascript
  * // This example increases the provisioned read and write capacity on the Music table.

package/dist-types/commands/UpdateTableReplicaAutoScalingCommand.d.ts

@@ -34,6 +34,32 @@ export interface UpdateTableReplicaAutoScalingCommandOutput extends UpdateTableR
  * @see {@link UpdateTableReplicaAutoScalingCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link LimitExceededException} (client fault)
+ *  <p>There is no limit to the number of daily on-demand backups that can be taken. </p>
+ *          <p>For most purposes, up to 500 simultaneous table operations are allowed per account. These operations
+ *             include <code>CreateTable</code>, <code>UpdateTable</code>,
+ *                 <code>DeleteTable</code>,<code>UpdateTimeToLive</code>,
+ *                 <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p>
+ *          <p>When you are creating a table with one or more secondary
+ *             indexes, you can have up to 250 such requests running at a time. However, if the table or
+ *             index specifications are complex, then DynamoDB might temporarily reduce the number
+ *             of concurrent operations.</p>
+ *          <p>When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.</p>
+ *          <p>There is a soft account quota of 2,500 tables.</p>
+ *
+ * @throws {@link ResourceInUseException} (client fault)
+ *  <p>The operation conflicts with the resource's availability. For example, you
+ *             attempted to recreate an existing table, or tried to delete a table currently in the
+ *                 <code>CREATING</code> state.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ *
  */
 export declare class UpdateTableReplicaAutoScalingCommand extends $Command<UpdateTableReplicaAutoScalingCommandInput, UpdateTableReplicaAutoScalingCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UpdateTableReplicaAutoScalingCommandInput;

package/dist-types/commands/UpdateTimeToLiveCommand.d.ts

@@ -53,6 +53,34 @@ export interface UpdateTimeToLiveCommandOutput extends UpdateTimeToLiveOutput, _
  * @see {@link UpdateTimeToLiveCommandOutput} for command's `response` shape.
  * @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
  *
+ * @throws {@link InternalServerError} (server fault)
+ *  <p>An error occurred on the server side.</p>
+ *
+ * @throws {@link InvalidEndpointException} (client fault)
+ *
+ * @throws {@link LimitExceededException} (client fault)
+ *  <p>There is no limit to the number of daily on-demand backups that can be taken. </p>
+ *          <p>For most purposes, up to 500 simultaneous table operations are allowed per account. These operations
+ *             include <code>CreateTable</code>, <code>UpdateTable</code>,
+ *                 <code>DeleteTable</code>,<code>UpdateTimeToLive</code>,
+ *                 <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p>
+ *          <p>When you are creating a table with one or more secondary
+ *             indexes, you can have up to 250 such requests running at a time. However, if the table or
+ *             index specifications are complex, then DynamoDB might temporarily reduce the number
+ *             of concurrent operations.</p>
+ *          <p>When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.</p>
+ *          <p>There is a soft account quota of 2,500 tables.</p>
+ *
+ * @throws {@link ResourceInUseException} (client fault)
+ *  <p>The operation conflicts with the resource's availability. For example, you
+ *             attempted to recreate an existing table, or tried to delete a table currently in the
+ *                 <code>CREATING</code> state.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The operation tried to access a nonexistent table or index. The resource might not
+ *             be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
+ *
+ *
  */
 export declare class UpdateTimeToLiveCommand extends $Command<UpdateTimeToLiveCommandInput, UpdateTimeToLiveCommandOutput, DynamoDBClientResolvedConfig> {
     readonly input: UpdateTimeToLiveCommandInput;