When you use secondary indexes, you are charged for the storage usage of index data and the read throughput that is generated when you query index data. This topic describes the billing method and billable items of secondary indexes.
Billing rules
You are charged separately for secondary indexes. The storage usage and read throughput for index data are calculated in the same manner as the storage usage and read throughput for data in data tables. For more information, see Billing overview.
Billable items
The billable items of secondary indexes consist of the storage usage of index data and the read throughput for index data. The following table describes the billable items.
Billable item | Billing method | Description |
Storage usage of index data | Pay-as-you-go | The total storage usage of secondary indexes. Unit: GB. The storage usage of index data is calculated in the same manner as the storage usage of data in data tables. The total storage usage of secondary indexes is the sum of the storage usage of all rows in secondary indexes. The storage usage of one row is the sum of the storage usage of all primary key columns and attribute columns of the row. For more information, see Data storage. |
Read throughput for index data | Pay-as-you-go | The read throughput that is generated when read operations are called to read data from secondary indexes. Unit: CU. The read throughput for index data is calculated in the same manner as the read throughput for data in data tables. |
FAQ
Am I charged when I create a secondary index?
Read and write throughput is not calculated when you create a secondary index and when data is synchronized from the data table to the secondary index. You are not charged during the process of creating a secondary index.