Quotas
This section describes the current quotas, also referred to as limits, in Amazon Timestream.
Default quotas
The following table contains the Timestream quotas and the default values. To edit data retention for a table from the console, see Edit a table .
displayName | Description | defaultValue |
---|---|---|
Databases per account |
The maximum number of databases you can create per AWS account. |
500 |
Tables per account |
The maximum number of tables you can create per AWS account. |
50000 |
Future ingestion period in minutes |
The maximum lead time (in minutes) for your time series data compared to the current system time. For example, if the future ingestion period is 15 minutes, then Timestream will accept data that is up to 15 minutes ahead of the current system time. |
15 |
Minimum retention period for memory store in hours |
The minimum duration (in hours) for which data must be retained in the memory store per table. |
1 |
Maximum retention period for memory store in hours |
The maximum duration (in hours) for which data can be retained in the memory store per table. |
8766 |
Minimum retention period for magnetic store in days |
The minimum duration (in days) for which data must be retained in the magnetic store per table. |
1 |
Maximum retention period for magnetic store in days |
The maximum duration (in days) for which data can be retained in the magnetic store. This value is equivalent to 200 years. |
73000 |
Default retention period for magnetic store in days |
The default value (in days) for which data is retained in the magnetic store per table. This value is equivalent to 200 years. |
73000 |
Default retention period for memory store in hours |
The default duration (in hours) for which data is retained in the memory store. |
6 |
Dimensions per table |
The maximum number of dimensions per table. |
128 |
Measure names per table |
The maximum number of unique measure names per table. |
8192 |
Dimension name dimension value pair size per series |
The maximum size of dimension name and dimension value pair per series. |
2 Kilobytes |
Maximum record size |
The maximum size of a record. |
2 Kilobytes |
Records per WriteRecords API request |
The maximum number of records in a WriteRecords API request. |
100 |
Throttle rate for CRUD APIs |
The maximum number of Create/Update/List/Describe/Delete database/table/scheduled query API requests allowed per second per account, in the current region. |
1 |
Dimension name length |
The maximum number of bytes for a Dimension name. |
60 Bytes |
Measure name length |
The maximum number of bytes for a Measure name. |
256 Bytes |
Database name length |
The maximum number of bytes for a Database name. |
256 Bytes |
Table name length |
The maximum number of bytes for a Table name. |
256 Bytes |
QueryString length in KiB |
The maximum length (in KiB) of a query string in UTF-8 encoded chars for a query. |
256 |
Execution duration for queries in hours |
The maximum execution duration (in hours) for a query. Queries that take longer will timeout. |
1 |
Metadata size for query result |
The maximum metadata size for a query result. |
100 Kilobytes |
Data size for query result |
The maximum data size for a query result. |
5 Gigabytes |
Scheduled queries per account |
The maximum number of schedule queries you can create per Amazon account. |
10000 |
Measures per multi-measure record |
The maximum number of measures per multi-measure record. |
256 |
Measure value size per multi-measure record |
The maximum size of measure values per multi-measure record. |
2048 |
Unique measures across multi-measure records per table |
The unique measures in all the multi-measure records defined in a single table. |
1024 |
Maximum count of active magnetic store partitions |
The maximum number of active magnetic store partitions per database. A partition may remain active for up to 6 hours after receiving ingestion. |
250 |
Supported data types
The following table describes the supported data types for measure and dimension values.
Description | Timestream value |
---|---|
Supported data types for measure values. |
Big int, double, string, boolean, MULTI, Timestamp |
Supported data types for dimension values. |
String |
Naming constraints
The following table describes naming constraints.
Description | Timestream value |
---|---|
The maximum length of a dimension name. |
60 bytes |
The maximum length of a measure name. |
256 bytes |
The maximum length of a table name or database name. |
256 bytes |
Table and Database Name |
Table and database names are compared using UTF-8 binary representation. This means that comparison for ASCII characters is case sensitive. |
Measure Name |
Table and database names are compared using UTF-8 binary representation. This means that comparison for ASCII characters is case sensitive. |
Dimension Name |
Dimension and measure names are compared using UTF-8 binary representation. This means that comparison for ASCII characters is case sensitive. |
All Column Names |
Column names can not be duplicated. Since multi-measure records represent dimensions and measures as columns, the name for a dimension can not be the same as the name for a measure. |
Reserved keywords
All of the following are reserved keywords:
-
ALTER
-
AND
-
AS
-
BETWEEN
-
BY
-
CASE
-
CAST
-
CONSTRAINT
-
CREATE
-
CROSS
-
CUBE
-
CURRENT_DATE
-
CURRENT_TIME
-
CURRENT_TIMESTAMP
-
CURRENT_USER
-
DEALLOCATE
-
DELETE
-
DESCRIBE
-
DISTINCT
-
DROP
-
ELSE
-
END
-
ESCAPE
-
EXCEPT
-
EXECUTE
-
EXISTS
-
EXTRACT
-
FALSE
-
FOR
-
FROM
-
FULL
-
GROUP
-
GROUPING
-
HAVING
-
IN
-
INNER
-
INSERT
-
INTERSECT
-
INTO
-
IS
-
JOIN
-
LEFT
-
LIKE
-
LOCALTIME
-
LOCALTIMESTAMP
-
NATURAL
-
NORMALIZE
-
NOT
-
NULL
-
ON
-
OR
-
ORDER
-
OUTER
-
PREPARE
-
RECURSIVE
-
RIGHT
-
ROLLUP
-
SELECT
-
TABLE
-
THEN
-
TRUE
-
UESCAPE
-
UNION
-
UNNEST
-
USING
-
VALUES
-
WHEN
-
WHERE
-
WITH
System identifiers
We reserve column names "measure_value", "ts_non_existent_col" and "time" to be Timestream system identifiers. Additionally, column names may not start with "ts_" or "measure_name". System identifiers are case sensitive. Identifiers compared using UTF-8 binary representation. This means that comparison for identifiers is case sensitive.
System identifiers may not be used for dimension or measure names. We recommend you do not use system identifiers for database or table names.