How Tablestore is billed - Tablestore - Alibaba Cloud Documentation Center

Pricing

Visit the Tablestore product page for pricing details.

Billing method

Tablestore uses pay-as-you-go billing. Billing starts after you create a table, and you are charged on an hourly basis.

Important

Pay-as-you-go does not cap overall resource usage. Manage consumption at the application layer to avoid unexpected costs from traffic spikes.

Billable items

A Tablestore instance incurs fees for the following billable items:

Billable item		Billing rule
Data storage		Billed by the hourly average of total data volume in an instance per billing cycle.
Read throughput	Reserved read throughput	Sum of reserved read throughput across all tables, billed by the hourly average per billing cycle. Note Only high-performance instances support reserved read throughput. Instance.
Read throughput	Pay-as-you-go read throughput	Actual read throughput consumed per second, summed across all tables in an instance per billing cycle.
Write throughput	Reserved write throughput	Sum of reserved write throughput across all tables, billed by the hourly average per billing cycle. Note Only high-performance instances support reserved write throughput. Instances.
Write throughput	Pay-as-you-go write throughput	Actual write throughput consumed per second, summed across all tables in an instance per billing cycle.
Cross-region replication traffic	Pay-as-you-go	Global tables generate cross-region data transfer traffic during asynchronous replication to each replica. This traffic is billed by actual synchronized data volume in GB. Important Replication traffic fees are calculated per replica and billed to the source instance.
Outbound Internet traffic		Outbound Internet traffic is generated when applications access Tablestore over the Internet, primarily from HTTP responses. Formula: Fees for outbound Internet traffic = Outbound Internet traffic (GB) × Unit price per GB. Note Only outbound Internet traffic is billed. Inbound and internal network traffic are free. Failed requests also generate outbound traffic. Cross-region access counts as Internet access.

Billing rules for core features

The following core features incur additional charges:

Important

Internet access incurs outbound traffic charges.
SQL statements incur no extra fees, but SQL query operations such as table scans and index queries are billed.

Core feature	Billing rule
Search index	Search indexes are billed for high-performance storage, reserved read throughput, and metered read throughput, regardless of instance type. Billable items of search indexes.
SQL query	SQL computation itself does not consume throughput. However, underlying operations such as table scans and index queries consume read and write throughput, which is billed accordingly. Billable items of SQL query.
Secondary index	Secondary indexes are billed for data storage and read throughput. Billable items of secondary indexes.
Time series model	The TimeSeries model is billed for storage and metered read/write throughput. Billable items of the TimeSeries model.
Multiple data versions	All data versions and their version numbers consume storage space and are billed accordingly. Data storage.
Lifecycle management	Data cleanup is free. However, lifecycle management adds timestamps as version numbers to each attribute column, which consumes additional storage. Data storage.
Tunnel Service	Tunnel Service is free. Read throughput is billed based on actual data pulled.
Global tables	Data read/write and storage fees vary by table type. Cross-region replication traffic is also billed. Global Table Metering and Billing.
Data synchronization and migration (using tools or other products)	Migration tools and products such as Data Transmission Service (DTS) incur read and write throughput charges based on actual requests.
Access from compute engines (MaxCompute, Spark, Flink, and others)	Compute engine access incurs read and write throughput charges based on actual requests.