Quotas for Amazon Keyspaces (for Apache Cassandra)
This section describes current quotas and default values for Amazon Keyspaces (for Apache Cassandra).
Topics
Amazon Keyspaces service quotas
The following table contains Amazon Keyspaces (for Apache Cassandra) quotas and the default values. For more information about quotas, contact Amazon Web Services Support.
| Quota | Description | Amazon Keyspaces default |
|---|---|---|
|
Max keyspaces per Amazon Web Services Region |
The maximum number of keyspaces for this subscriber per Region. You can adjust
this default value in the
Service Quotas |
256 |
|
Max tables per Amazon Web Services Region |
The maximum number of tables across all keyspaces for this subscriber
per Region. You can adjust
this default value in the
Service Quotas |
256 |
|
Max table schema size |
The maximum size of a table schema. |
350 KB |
|
Max concurrent DDL operations |
The maximum number of concurrent DDL operations allowed for this subscriber per Region. |
50 |
|
Max queries per connection |
The maximum number of CQL queries that can be processed by a single client TCP connection per second. |
3000 |
|
Max row size |
The maximum size of a row, excluding static column data. For details, see Estimate row size in Amazon Keyspaces. |
1 MB |
Max number of columns in |
The maximum number of columns allowed in CQL |
225/166 |
|
Max static data per logical partition |
The maximum aggregate size of static data in a logical partition. For details, see Calculate the static column size per logical partition in Amazon Keyspaces. |
1 MB |
|
Max subqueries per |
The maximum number of subqueries you can use for the |
100 |
|
Max number of nested frozen collections per Amazon Web Services Region |
The maximum number of nested collections supported when you're using
the |
5 |
|
Max read throughput per second |
The maximum read throughput per second—read request units
(RRUs) or read capacity units (RCUs)—that can be allocated to
a table per Region. You can adjust
this default value in the
Service Quotas |
40,000 |
|
Max write throughput per second |
The maximum write throughput per second—write request units
(WRUs) or write capacity units (WCUs)—that can be allocated
to a table per Region. You can adjust
this default value in the
Service Quotas |
40,000 |
|
Account-level read throughput (provisioned) |
The maximum number of aggregate read capacity units (RCUs) allocated
for the account per Region. This is applicable only for tables in
provisioned read/write capacity mode. You can adjust
this default value in the
Service Quotas |
80,000 |
|
Account-level write throughput (provisioned) |
The maximum number of aggregate write capacity units (WCU)
allocated for the account per Region. This is applicable only for
tables in provisioned read/write capacity mode. You can adjust
this default value in the
Service Quotas |
80,000 |
|
Max number of scalable targets per Region per account |
The maximum number of scalable targets for the account per Region. An
Amazon Keyspaces table counts as one scalable target if auto scaling is enabled
for read capacity, and as another scalable target if auto scaling is
enabled for write capacity. You can adjust this default value in the Service Quotas |
1,500 |
|
Max partition key size |
The maximum size of the compound partition key. Up to 3 bytes of additional storage are added to the raw size of each column included in the partition key for metadata. |
2048 bytes |
|
Max clustering key size |
The maximum combined size of all clustering columns. Up to 4 bytes of additional storage are added to the raw size of each clustering column for metadata. |
850 bytes |
|
Max concurrent table restores using Point-in-time Recovery (PITR) |
The maximum number of concurrent table restores using PITR per
subscriber is 4. You can adjust
this default value in the
Service Quotas |
4 |
|
Max amount of data restored using point-in-time recovery (PITR) |
The maximum size of data that can be restored using PITR within 24
hours. You can adjust
this default value in the
Service Quotas |
5 TB |
Increasing or decreasing throughput (for provisioned tables)
Increasing provisioned throughput
You can increase ReadCapacityUnits or WriteCapacityUnits
as often as necessary by using the console or the ALTER TABLE
statement. The new settings don't take effect until the ALTER TABLE
operation is complete.
You can't exceed your per-account quotas when you add provisioned capacity. And you can increase the provisioned capacity for your tables as much as you need. For more information about per-account quotas, see the preceding section, Amazon Keyspaces service quotas.
Decreasing provisioned throughput
For every table in an ALTER TABLE statement, you can decrease
ReadCapacityUnits or WriteCapacityUnits (or both). The
new settings don't take effect until the ALTER TABLE operation is
complete.
A decrease is allowed up to four times, anytime per day. A day is defined according to Universal Coordinated Time (UTC). Additionally, if there was no decrease in the past hour, an additional decrease is allowed. This effectively brings the maximum number of decreases in a day to 27 (4 decreases in the first hour, and 1 decrease for each of the subsequent 1-hour windows in a day).
Amazon Keyspaces encryption at rest
You can change encryption options between an Amazon owned Amazon KMS key and a customer managed Amazon KMS key up to four times within a 24-hour window, on a per table basis, starting from when the table was created. If there was no change in the past six hours, an additional change is allowed. This effectively brings the maximum number of changes in a day to eight (four changes in the first six hours, and one change for each of the subsequent six-hour windows in a day).
You can change the encryption option to use an Amazon owned Amazon KMS key as often as necessary, even if the earlier quota has been exhausted.
These are the quotas unless you request a higher amount. To request a service quota
increase, see Amazon Web Services Support