Quotas for Amazon Keyspaces (for Apache Cassandra) - Amazon Keyspaces (for Apache Cassandra)

Quotas for Amazon Keyspaces (for Apache Cassandra)

This sections describes current quotas and default values for Amazon Keyspaces (for Apache Cassandra).

To increase default quotas for your account, contact AWS Support.

Quotas

The following table contains the Amazon Keyspaces (for Apache Cassandra) quotas and the default values. You can view your service quotas in the AWS Service Quotas console.

Quota Description Amazon Keyspaces default

Max keyspaces per AWS Region

The maximum number of keyspaces for this subscriber per Region.

256

Max tables per AWS Region

The maximum number of tables across all keyspaces for this subscriber per Region.

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 processed by a single client TCP connection per second.

3000

Max row size

The maximum size of a row. For details see Calculating Row Size in Amazon Keyspaces.

1 MB

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.

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.

40,000

Account-level read throughput (provisioned)

The maximum number of aggregate read capacity units (RCUs) allocated for the account per Region; applicable only for tables in provisioned read/write capacity mode.

80,000

Account-level write throughput (provisioned)

The maximum number of aggregate write capacity units (WCU) allocated for the account per Region; applicable only for tables in provisioned read/write capacity mode.

80,000

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.

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.

5 TB

Increasing or Decreasing Throughput (for Provisioned Tables)

Increasing Provisioned Throughput

You can increase ReadCapacityUnits or WriteCapacityUnits as often as necessary, using the AWS Management Console or the ALTER TABLE statement. The new settings do not 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, 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).