||A condition specified in the operation could not be evaluated.
||Default service exception class
||The request signature does not conform to AWS standards.
||The server encountered an internal error trying to fulfill the request.
||An error occurred on the server side.
||An item collection is too large. This exception is only returned for tables that
have one or more local secondary indexes.
||The number of concurrent table requests (cumulative number of tables in the
CREATING, DELETING or UPDATING state) exceeds the maximum allowed of 10. Also,
for tables with secondary indexes, only one of those tables can be in the
CREATING state at any point in time. Do not attempt to create more than one such
table simultaneously. The total limit of tables in the ACTIVE state is 250.
||Request must contain a valid (registered) AWS Access Key ID.
||The request rate is too high, or the request is too large, for the available
throughput to accommodate. The AWS SDKs automatically retry requests that
receive this exception; therefore, your request will eventually succeed, unless
the request is too large or your retry queue is too large to finish. Reduce the
frequency of requests by using the strategies listed in Error Retries and
Exponential Backoff in the Amazon DynamoDB Developer Guide.
||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 CREATING state.
||The operation tried to access a nonexistent table or index. The resource may not
be specified correctly, or its status may not be ACTIVE.
||The service is currently unavailable or busy.
||Rate of requests exceeds the allowed throughput.
||This exception may contain unprocessed write request items
||Unrecognized client exception
||One or more required parameter values were missing.