Notes and Constraints

A store name must be 16 to 52 characters long. It is case-insensitive and cannot contain periods (.). A store name must be globally unique.
Each account can create up to 25 stores.
Point-In-Time Recovery (PITR) cannot be enabled for both a store and its tables.
A store belongs to a region.
Stores cannot be deleted.

A table name can be 3 to 52 characters long. It is case-sensitive and must be unique within the store where it is.
Up to 100 tables can be created in a store.
You can only define one shard key and one sort key for a single table.
A table must belong to a store.
Tables cannot be deleted.

The KV data type can be a string, Boolean value, null value, floating-point number, array, mapping, date, or ObjectId. The total size of keys and values in a KV item cannot exceed 512 KB, including the primary key and local secondary indexes.
A field name can be 1 byte to 63 bytes long. It is case sensitive and cannot contain periods (.) or dollar signs ($). A field name prefixed with X is a reserved name. The existing reserved field names are Xattr and Xblob. You are advised not to use them as field names.
A primary key must be unique and cannot exceed 1,200 bytes.
KV items accessed through APIs must be in the same store.
A KV item must belong to a table.
A KV item is uniquely identified by its store, table, and primary key combined.

A local secondary index must be prefixed with the shard key of its base table.
A newly written KV item takes about one second to be synchronized to the global secondary index.
An index item cannot be longer than 1,200 bytes.
Indexes can only be created during table creation.
Duplicate composite primary keys (shard key and sort key) are not allowed for multiple global secondary indexes of a table.
Duplicate keys are not allowed in a single global secondary index.
A global secondary index cannot have the same shard key as its base table.
Duplicate sort keys are not allowed for multiple local secondary indexes of a table.
Duplicate keys are not allowed in a single local secondary index.
A local secondary index cannot have the same shard key as its base table.
A local secondary index cannot have the same sort key as its base table.