Resource plans are subscription-based resources that offer lower prices based on their specifications and subscription duration. You can plan and purchase resource plans in advance based on your estimated resource consumption to reduce costs.
Notes
Tablestore resource plans cannot be used to offset internet outbound traffic.
You can purchase a storage plan of a specific type only once within the same period. However, you can purchase multiple pay-as-you-go write CU plans, pay-as-you-go read CU plans, and reserved CU plans.
Resource plan types
Tablestore provides four types of resource plans: pay-as-you-go write CU plans, pay-as-you-go read CU plans, storage plans, and reserved CU plans. The types of resource plans that are supported vary based on the billing method. The following table provides details.
Type | Applicable billing method | Description |
Pay-as-you-go write CU plan | CU mode (formerly pay-as-you-go mode) | The total number of write CUs that can be used each month within the validity period. This is used to offset pay-as-you-go write throughput. For example, if you purchase a one-year pay-as-you-go write CU plan of 1 billion CUs, 1 billion pay-as-you-go write CUs are offset by the resource plan each month for one year. |
Pay-as-you-go read CU plan | CU mode (formerly pay-as-you-go mode) | The total number of read CUs that can be used each month within the validity period. This is used to offset pay-as-you-go read throughput and reserved read throughput. |
Storage plan |
| The amount of storage that can be offset each hour within the validity period. |
Reserved CU plan | CU mode (formerly pay-as-you-go mode) | The amount of reserved read and write CUs that can be offset each hour within the validity period. This includes the reserved read throughput generated by search indexes. Note The reserved read throughput of search indexes can be offset by reserved CU plans. |
Resource plan prices
For information about resource plan pricing, see the Pricing page or the Purchase Resource Plan page.
Purchase guide
Before you purchase a resource plan, determine which plan to purchase based on the instance type, your resource usage, and other factors.
Region
Global resource plans can be used to offset usage in all regions.
Instance type
Tablestore provides two types of instances: high-performance instances and storage-optimized instances. The instance type that you select for the resource plan must match the instance type of the resources that you want to offset.
Instance type | Description |
High-performance instance (including search indexes) | A high-performance storage resource plan can only offset the resource usage of high-performance instances and search indexes under your account. If you purchase a storage-optimized storage resource plan, the resources used by the high-performance instance are billed on a pay-as-you-go basis. |
Storage-optimized instance | A storage-optimized storage resource plan can only offset the resource usage of storage-optimized instances under your account. If you purchase a high-performance storage resource plan, the resources used by the storage-optimized instance are billed on a pay-as-you-go basis. Important If you use a search index in a storage-optimized instance, high-performance storage usage and read/write fees are generated. In this case, you must purchase a high-performance storage resource plan and a reserved CU plan to offset the costs. For more information, see Metering and billing of search indexes. |
Plan specifications
You can export historical metering data from Expenses and Costs and perform a statistical analysis. Then, you can estimate your future resource consumption to determine the required plan specifications.
Metering data | Description of the evaluation scale |
Data storage | Export the usage of the last hour or the average hourly usage over a recent period. Estimate the usage for high-performance and storage-optimized instances separately. |
Reserved read throughput | Export the usage of the last hour or the average hourly usage over a recent period for estimation. |
Reserved write throughput | |
Pay-as-you-go read throughput | Export the total pay-as-you-go read CU usage of all instances from the last month for estimation. |
Pay-as-you-go write throughput | Export the total pay-as-you-go write CU usage of all instances from the last month for estimation. |
Subscription duration
The longer the subscription duration of a resource plan, the higher the discount.
Offset rules
Resource plan offset method: If your resource usage is within the specifications of your resource plan, Tablestore does not charge extra fees. If your resource usage exceeds the specifications, the excess usage is billed on a pay-as-you-go basis.
If multiple resource plans of the same type can be used to offset the usage of the same resource, Tablestore prioritizes the plan that expires first.
Resource plan offset order: The quota of the resource plan is used first. Any usage that exceeds the quota is billed on a pay-as-you-go basis.