A read request that returns up to 4kB of data is considered one RRU.

If a request returns more than 4kB of data, additional RRUs are required.

If a read request involves server-side filtering or aggregation of data, then the data is measured before the filtering or aggregation takes place. For example, this applies to queries that use the ALLOW FILTERING clause, COUNT function, or GROUP BY clause, and queries that don’t request all columns from a row.

A write request with up to 1kB of data is considered one WRU.

If a request has more than 1kB of data, additional WRUs are required.

A DELETE request is considered one WRU, regardless of size. There are no additional charges for the TTL delete operation, DROP statements, or TRUNCATE statements.

A write index is considered a write request. The write index size and the required WRUs are based on the size of each indexed column instead of the size of the index, regardless of the column type.

Writes in multi-region configurations are billed for each region written to.

Insert, update, and upsert options are treated as write operations and calculated as WRUs.

WRUs required for batched writes depend on the size and type. Logged batch writes require additional WRUs by default.

Data Transfer - Same Region: The transfer occurs within the same region of a cloud provider network.

Data Transfer - Cross Region within Cloud Provider Network: The transfer crosses regions within one cloud provider network.

Data Transfer - Internet: The transfer leaves the cloud provider network over the internet.

Private endpoints and custom DNS

Multi-region databases

Vector dimensions:

Index Storage Size, based on estimated storage size per month, methods of procedure (MOP) per month, and either one or three Availability Zones (AZ)