AWS Amazon DynamoDB Error Codes

There is another ongoing conflicting backup control plane operation on the table. The backup is either being created, deleted or restored to a table.

Backup not found for the given BackupARN.

A condition specified in the operation failed to be evaluated.

Backups have not yet been enabled for this table.

There was an attempt to insert an item with the same primary key as an item that already exists in the DynamoDB table.

There was a conflict when writing to the specified S3 bucket.

The specified export was not found.

The specified global table already exists.

The specified global table does not exist.

DynamoDB rejected the request because you retried a request with a different payload but with an idempotent token that was already used.

There was a conflict when importing from the specified S3 source. This can occur when the current import conflicts with a previous import request that had the same client token.

The specified import was not found.

The operation tried to access a nonexistent index.

An error occurred on the server side.

The specified ExportTime is outside of the point in time recovery window.

An invalid restore time was specified. RestoreDateTime must be between EarliestRestorableDateTime and LatestRestorableDateTime.

An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.

There is no limit to the number of daily on-demand backups that can be taken. For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive, RestoreTableFromBackup, and RestoreTableToPointInTime. 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

Point in time recovery has not yet been enabled for this source table.

The operation tried to access a nonexistent resource-based policy. If you specified an ExpectedRevisionId, it's possible that a policy is present for the resource but its revision ID didn't match the expected value.

The request was denied due to request throttling. For detailed information about why the request was throttled and the ARN of the impacted resource, find the ThrottlingReason field in the returned exception. 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 Error Retries a

The specified replica is already part of the global table.

The specified replica is no longer part of the global table.

The request was rejected because one or more items in the request are being modified by a request in another Region.

Throughput exceeds the current throughput quota for your account. For detailed information about why the request was throttled and the ARN of the impacted resource, find the ThrottlingReason field in the returned exception. Contact Amazon Web Services Support to request a quota increase.

The operation conflicts with the resource's availability. For example: You attempted to recreate an existing table. You tried to delete a table currently in the CREATING state. You tried to update a resource that was already being updated. When appropriate, wait for the ongoing update to complete and attempt the request again.

The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE.

A target table with the specified name already exists.

A target table with the specified name is either being created or deleted.

A source table with the name TableName does not currently exist within the subscriber's account or the subscriber is operating in the wrong Amazon Web Services Region.

The request was denied due to request throttling. For detailed information about why the request was throttled and the ARN of the impacted resource, find the ThrottlingReason field in the returned exception.

The entire transaction request was canceled. DynamoDB cancels a TransactWriteItems request under the following circumstances: A condition in one of the condition expressions is not met. A table in the TransactWriteItems request is in a different account or region. More than one action in the TransactWriteItems operation targets the same item. There is insufficient provisioned capacity for the transaction to be completed. An item size becomes too large (larger than 400 KB), or a local s

Operation was rejected because there is an ongoing transaction for the item.

The transaction with the given request token is already in progress. Recommended Settings This is a general recommendation for handling the TransactionInProgressException. These settings help ensure that the client retries will trigger completion of the ongoing TransactWriteItems request. Set clientExecutionTimeout to a value that allows at least one retry to be processed after 5 seconds have elapsed since the first attempt for the TransactWriteItems operation. Set socketTimeout to