AmazonDynamoDBNioClient
Simplified method form for invoking the BatchGetItem operation.
Simplified method form for invoking the BatchGetItem operation.
#batchGetItem(BatchGetItemRequest)
Simplified method form for invoking the BatchGetItem operation.
Simplified method form for invoking the BatchGetItem operation.
#batchGetItem(BatchGetItemRequest)
The BatchGetItem operation returns the attributes of one or more items from one or more tables.
The BatchGetItem operation returns the attributes of one or more items from one or more tables. You identify requested items by primary key.
A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. BatchGetItem will return a partial result if the response size limit is exceeded, the table's provisioned throughput is exceeded, or an internal processing failure occurs. If a partial result is returned, the operation returns a value for UnprocessedKeys. You can use this value to retry the operation starting with the next item to get.
<important>
If you request more than 100 items BatchGetItem will return a ValidationException with the message "Too many items requested for the BatchGetItem call".
</important>
For example, if you ask to retrieve 100 items, but each individual item is 300 KB in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also returns an appropriate UnprocessedKeys value so you can get the next page of results. If desired, your application can include its own logic to assemble the pages of results into one data set.
If none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then BatchGetItem will return a ProvisionedThroughputExceededException. If at least one of the items is successfully processed, then BatchGetItem completes successfully, while returning the keys of the unread items in UnprocessedKeys.
<important>
If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, we strongly recommend that you use an exponential backoff algorithm. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.
For more information, see Batch Operations and Error Handling in the Amazon DynamoDB Developer Guide.
</important>
By default, BatchGetItem performs eventually consistent reads on
every table in the request. If you want strongly consistent reads
instead, you can set ConsistentRead to true for any
or all tables.
In order to minimize response latency, BatchGetItem retrieves items in parallel.
When designing your application, keep in mind that DynamoDB does not return attributes in any particular order. To help parse the response by item, include the primary key values for the items in your request in the AttributesToGet parameter.
If a requested item does not exist, it is not returned in the result. Requests for nonexistent items consume the minimum read capacity units according to the type of read. For more information, see Capacity Units Calculations in the Amazon DynamoDB Developer Guide.
Represents the input of a BatchGetItem operation.
Result of the BatchGetItem operation returned by the service.
An error occurred on the server side.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the BatchWriteItem operation.
Simplified method form for invoking the BatchWriteItem operation.
#batchWriteItem(BatchWriteItemRequest)
The BatchWriteItem operation puts or deletes multiple items in one or more tables.
The BatchWriteItem operation puts or deletes multiple items in one or more tables. A single call to BatchWriteItem can write up to 16 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 400 KB.
<note>
BatchWriteItem cannot update items. To update items, use the UpdateItem API.
</note>
The individual PutItem and DeleteItem operations specified in BatchWriteItem are atomic; however BatchWriteItem as a whole is not. If any requested operations fail because the table's provisioned throughput is exceeded or an internal processing failure occurs, the failed operations are returned in the UnprocessedItems response parameter. You can investigate and optionally resend the requests. Typically, you would call BatchWriteItem in a loop. Each iteration would check for unprocessed items and submit a new BatchWriteItem request with those unprocessed items until all items have been processed.
Note that if none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then BatchWriteItem will return a ProvisionedThroughputExceededException.
<important>
If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, we strongly recommend that you use an exponential backoff algorithm. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.
For more information, see Batch Operations and Error Handling in the Amazon DynamoDB Developer Guide.
</important>
With BatchWriteItem, you can efficiently write or delete large amounts of data, such as from Amazon Elastic MapReduce (EMR), or copy data from another database into DynamoDB. In order to improve performance with these large-scale operations, BatchWriteItem does not behave in the same way as individual PutItem and DeleteItem calls would. For example, you cannot specify conditions on individual put and delete requests, and BatchWriteItem does not return deleted items in the response.
If you use a programming language that supports concurrency, you can use threads to write items in parallel. Your application must include the necessary logic to manage the threads. With languages that don't support threading, you must update or delete the specified items one at a time. In both situations, BatchWriteItem provides an alternative where the API performs the specified put and delete operations in parallel, giving you the power of the thread pool approach without having to introduce complexity into your application.
Parallel processing reduces latency, but each specified put and delete request consumes the same number of write capacity units whether it is processed in parallel or not. Delete operations on nonexistent items consume one write capacity unit.
If one or more of the following is true, DynamoDB rejects the entire batch write operation:
-
One or more tables specified in the BatchWriteItem request does not exist.
-
Primary key attributes specified on an item in the request do not match those in the corresponding table's primary key schema.
-
You try to perform multiple operations on the same item in the same BatchWriteItem request. For example, you cannot put and delete the same item in the same BatchWriteItem request.
-
There are more than 25 requests in the batch.
-
Any individual item in a batch exceeds 400 KB.
-
The total request size exceeds 16 MB.
Represents the input of a BatchWriteItem operation.
Result of the BatchWriteItem operation returned by the service.
An error occurred on the server side.
ItemCollectionSizeLimitExceededExceptionAn item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the CreateTable operation.
Simplified method form for invoking the CreateTable operation.
#createTable(CreateTableRequest)
The CreateTable operation adds a new table to your account.
The CreateTable operation adds a new table to your account. In an AWS account, table names must be unique within each region. That is, you can have two tables with same name if you create the tables in different regions.
CreateTable is an asynchronous operation. Upon receiving a
CreateTable request, DynamoDB immediately returns a response with
a TableStatus of CREATING. After the table is
created, DynamoDB sets the TableStatus to ACTIVE. You
can perform read and write operations only on an ACTIVE
table.
You can optionally define secondary indexes on the new table, as part of
the CreateTable operation. If you want to create multiple tables
with secondary indexes on them, you must create the tables sequentially.
Only one table with secondary indexes can be in the CREATING
state at any given time.
You can use the DescribeTable API to check the table status.
Represents the input of a CreateTable operation.
Result of the CreateTable operation returned by the service.
An error occurred on the server side.
LimitExceededException
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.
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.
Simplified method form for invoking the DeleteItem operation.
Simplified method form for invoking the DeleteItem operation.
#deleteItem(DeleteItemRequest)
Simplified method form for invoking the DeleteItem operation.
Simplified method form for invoking the DeleteItem operation.
#deleteItem(DeleteItemRequest)
Deletes a single item in a table by primary key.
Deletes a single item in a table by primary key. You can perform a conditional delete operation that deletes the item if it exists, or if it has an expected attribute value.
In addition to deleting an item, you can also return the item's attribute values in the same operation, using the ReturnValues parameter.
Unless you specify conditions, the DeleteItem is an idempotent operation; running it multiple times on the same item or attribute does not result in an error response.
Conditional deletes are useful for deleting items only if specific conditions are met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item is not deleted.
Represents the input of a DeleteItem operation.
Result of the DeleteItem operation returned by the service.
A condition specified in the operation could not be evaluated.
InternalServerErrorExceptionAn error occurred on the server side.
ItemCollectionSizeLimitExceededExceptionAn item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the DeleteTable operation.
Simplified method form for invoking the DeleteTable operation.
#deleteTable(DeleteTableRequest)
The DeleteTable operation deletes a table and all of its items.
The DeleteTable operation deletes a table and all of its items.
After a DeleteTable request, the specified table is in the
DELETING state until DynamoDB completes the deletion. If the
table is in the ACTIVE state, you can delete it. If a table
is in CREATING or UPDATING states, then
DynamoDB returns a ResourceInUseException. If the specified table
does not exist, DynamoDB returns a ResourceNotFoundException. If
table is already in the DELETING state, no error is
returned.
<note>
DynamoDB might continue to accept data read and write operations, such as
GetItem and PutItem, on a table in the
DELETING state until the table deletion is complete.
</note>
When you delete a table, any indexes on that table are also deleted.
If you have DynamoDB Streams enabled on the table, then the corresponding
stream on that table goes into the DISABLED state, and the
stream is automatically deleted after 24 hours.
Use the DescribeTable API to check the status of the table.
Represents the input of a DeleteTable operation.
Result of the DeleteTable operation returned by the service.
An error occurred on the server side.
LimitExceededException
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.
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 might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the DescribeTable operation.
Simplified method form for invoking the DescribeTable operation.
#describeTable(DescribeTableRequest)
Returns information about the table, including the current status of the table, when it was created, the primary key schema, and any indexes on the table.
Returns information about the table, including the current status of the table, when it was created, the primary key schema, and any indexes on the table.
<note>
If you issue a DescribeTable request immediately after a CreateTable request, DynamoDB might return a ResourceNotFoundException. This is because DescribeTable uses an eventually consistent query, and the metadata for your table might not be available at that moment. Wait for a few seconds, and then try the DescribeTable request again.
</note>
Represents the input of a DescribeTable operation.
Result of the DescribeTable operation returned by the service.
An error occurred on the server side.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the GetItem operation.
Simplified method form for invoking the GetItem operation.
#getItem(GetItemRequest)
Simplified method form for invoking the GetItem operation.
Simplified method form for invoking the GetItem operation.
#getItem(GetItemRequest)
The GetItem operation returns a set of attributes for the item with the given primary key.
The GetItem operation returns a set of attributes for the item with the given primary key. If there is no matching item, GetItem does not return any data.
GetItem provides an eventually consistent read by default. If your
application requires a strongly consistent read, set
ConsistentRead to true. Although a strongly
consistent read might take more time than an eventually consistent read,
it always returns the last updated value.
Represents the input of a GetItem operation.
Result of the GetItem operation returned by the service.
An error occurred on the server side.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the ListTables operation.
Simplified method form for invoking the ListTables operation.
#listTables(ListTablesRequest)
Simplified method form for invoking the ListTables operation.
Simplified method form for invoking the ListTables operation.
#listTables(ListTablesRequest)
Simplified method form for invoking the ListTables operation.
Simplified method form for invoking the ListTables operation.
#listTables(ListTablesRequest)
Simplified method form for invoking the ListTables operation.
Simplified method form for invoking the ListTables operation.
#listTables(ListTablesRequest)
Returns an array of table names associated with the current account and endpoint.
Returns an array of table names associated with the current account and endpoint. The output from ListTables is paginated, with each page returning a maximum of 100 table names.
Represents the input of a ListTables operation.
Result of the ListTables operation returned by the service.
An error occurred on the server side.
Simplified method form for invoking the PutItem operation.
Simplified method form for invoking the PutItem operation.
#putItem(PutItemRequest)
Simplified method form for invoking the PutItem operation.
Simplified method form for invoking the PutItem operation.
#putItem(PutItemRequest)
Creates a new item, or replaces an old item with a new item.
Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. You can perform a conditional put operation (add a new item if one with the specified primary key doesn't exist), or replace an existing item if it has certain attribute values.
In addition to putting an item, you can also return the item's attribute values in the same operation, using the ReturnValues parameter.
When you add an item, the primary key attribute(s) are the only required attributes. Attribute values cannot be null. String and Binary type attributes must have lengths greater than zero. Set type attributes cannot be empty. Requests with empty values will be rejected with a ValidationException exception.
You can request that PutItem return either a copy of the original item (before the update) or a copy of the updated item (after the update). For more information, see the ReturnValues description below.
<note>
To prevent a new item from replacing an existing item, use a conditional
put operation with ComparisonOperator set to NULL for
the primary key attribute, or attributes.
</note>
For more information about using this API, see Working with Items in the Amazon DynamoDB Developer Guide.
Represents the input of a PutItem operation.
Result of the PutItem operation returned by the service.
A condition specified in the operation could not be evaluated.
InternalServerErrorExceptionAn error occurred on the server side.
ItemCollectionSizeLimitExceededExceptionAn item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
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 Query operation uses the primary key of a table or a secondary index to directly access items from that table or index.
A Query operation uses the primary key of a table or a secondary index to directly access items from that table or index.
Use the KeyConditionExpression parameter to provide a specific hash key value. The Query operation will return all of the items from the table or index with that hash key value. You can optionally narrow the scope of the Query operation by specifying a range key value and a comparison operator in KeyConditionExpression. You can use the ScanIndexForward parameter to get results in forward or reverse order, by range key or by index key.
Queries that do not return results consume the minimum number of read capacity units for that type of read operation.
If the total number of items meeting the query criteria exceeds the result set size limit of 1 MB, the query stops and results are returned to the user with the LastEvaluatedKey element to continue the query in a subsequent operation. Unlike a Scan operation, a Query operation never returns both an empty result set and a LastEvaluatedKey value. LastEvaluatedKey is only provided if the results exceed 1 MB, or if you have used the Limit parameter.
You can query a table, a local secondary index, or a global secondary
index. For a query on a table or on a local secondary index, you can set
the ConsistentRead parameter to true and obtain a
strongly consistent result. Global secondary indexes support eventually
consistent reads only, so do not specify ConsistentRead when
querying a global secondary index.
Represents the input of a Query operation.
Result of the Query operation returned by the service.
An error occurred on the server side.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the Scan operation.
Simplified method form for invoking the Scan operation.
#scan(ScanRequest)
Simplified method form for invoking the Scan operation.
Simplified method form for invoking the Scan operation.
#scan(ScanRequest)
Simplified method form for invoking the Scan operation.
Simplified method form for invoking the Scan operation.
#scan(ScanRequest)
The Scan operation returns one or more items and item attributes by accessing every item in a table or a secondary index.
The Scan operation returns one or more items and item attributes by accessing every item in a table or a secondary index. To have DynamoDB return fewer items, you can provide a ScanFilter operation.
If the total number of scanned items exceeds the maximum data set size limit of 1 MB, the scan stops and results are returned to the user as a LastEvaluatedKey value to continue the scan in a subsequent operation. The results also include the number of items exceeding the limit. A scan can result in no table data meeting the filter criteria.
By default, Scan operations proceed sequentially; however, for faster performance on a large table or secondary index, applications can request a parallel Scan operation by providing the Segment and TotalSegments parameters. For more information, see Parallel Scan in the Amazon DynamoDB Developer Guide.
By default, Scan uses eventually consistent reads when acessing the data in the table or local secondary index. However, you can use strongly consistent reads instead by setting the ConsistentRead parameter to true.
Represents the input of a Scan operation.
Result of the Scan operation returned by the service.
An error occurred on the server side.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Overrides the default endpoint for this client ("https://dynamodb.us-east-1.amazonaws.com").
Overrides the default endpoint for this client ("https://dynamodb.us-east-1.amazonaws.com"). Callers can use this method to control which AWS region they want to work with.
Callers can pass in just the endpoint (ex:
"dynamodb.us-east-1.amazonaws.com") or a full URL, including the protocol
(ex: "https://dynamodb.us-east-1.amazonaws.com"). If the protocol is not
specified here, the default protocol from this client's
ClientConfiguration will be used, which by default is HTTPS.
For more information on using AWS regions with the AWS SDK for Java, and a complete list of all available endpoints for all AWS services, see: <a href= "http://developer.amazonwebservices.com/connect/entry.jspa?externalID=3912" > http://developer.amazonwebservices.com/connect/entry.jspa?externalID= 3912 This method is not threadsafe. An endpoint should be configured when the client is created and before any service requests are made. Changing it afterwards creates inevitable race conditions for any service requests in transit or retrying.
The endpoint (ex: "dynamodb.us-east-1.amazonaws.com") or a full URL, including the protocol (ex: "https://dynamodb.us-east-1.amazonaws.com") of the region specific AWS endpoint this client will communicate with.
An alternative to AmazonDynamoDB#setEndpoint(String), sets the
regional endpoint for this client's service calls.
An alternative to AmazonDynamoDB#setEndpoint(String), sets the
regional endpoint for this client's service calls. Callers can use this
method to control which AWS region they want to work with.
By default, all service endpoints in all regions use the https protocol.
To use http instead, specify it in the ClientConfiguration
supplied at construction.
This method is not threadsafe. A region should be configured when the client is created and before any service requests are made. Changing it afterwards creates inevitable race conditions for any service requests in transit or retrying.
The region this client will communicate with. See { @link Region#getRegion(com.amazonaws.regions.Regions)} for accessing a given region. Must not be null and must be a region where the service is available.
Region#isServiceSupported(String)
Region#createClient(Class, com.amazonaws.auth.AWSCredentialsProvider, ClientConfiguration)
Region#getRegion(com.amazonaws.regions.Regions)
Shuts down this client object, releasing any resources that might be held open.
Shuts down this client object, releasing any resources that might be held open. This is an optional method, and callers are not expected to call it, but can if they want to explicitly release any open resources. Once a client has been shutdown, it should not be used to make any more requests.
Simplified method form for invoking the UpdateItem operation.
Simplified method form for invoking the UpdateItem operation.
#updateItem(UpdateItemRequest)
Simplified method form for invoking the UpdateItem operation.
Simplified method form for invoking the UpdateItem operation.
#updateItem(UpdateItemRequest)
Edits an existing item's attributes, or adds a new item to the table if it does not already exist.
Edits an existing item's attributes, or adds a new item to the table if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update on an existing item (insert a new attribute name-value pair if it doesn't exist, or replace an existing name-value pair if it has certain expected attribute values). If conditions are specified and the item does not exist, then the operation fails and a new item is not created.
You can also return the item's attribute values in the same UpdateItem operation using the ReturnValues parameter.
Represents the input of an UpdateItem operation.
Result of the UpdateItem operation returned by the service.
A condition specified in the operation could not be evaluated.
InternalServerErrorExceptionAn error occurred on the server side.
ItemCollectionSizeLimitExceededExceptionAn item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.
ProvisionedThroughputExceededExceptionYour request rate is too high. The AWS 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 and Exponential Backoff in the Amazon DynamoDB Developer Guide.
ResourceNotFoundException
The operation tried to access a nonexistent table or index. The
resource might not be specified correctly, or its status might
not be ACTIVE.
Simplified method form for invoking the UpdateTable operation.
Simplified method form for invoking the UpdateTable operation.
#updateTable(UpdateTableRequest)
Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.
Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.
You can only perform one of the following operations at once:
-
Modify the provisioned throughput settings of the table.
-
Enable or disable Streams on the table.
-
Remove a global secondary index from the table.
-
Create a new global secondary index on the table. Once the index begins backfilling, you can use UpdateTable to perform other operations.
UpdateTable is an asynchronous operation; while it is executing,
the table status changes from ACTIVE to
UPDATING. While it is UPDATING, you cannot
issue another UpdateTable request. When the table returns to the
ACTIVE state, the UpdateTable operation is complete.
Represents the input of an UpdateTable operation.
Result of the UpdateTable operation returned by the service.
An error occurred on the server side.
LimitExceededException
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.
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 might not be specified correctly, or its status might
not be ACTIVE.