Resource plan-Object Storage Service(OSS)-阿里云帮助中心

Resource plan types

Resource plan	Description
Storage plan	Covers storage costs for OSS files or ECS snapshots.
Standard zone-redundant storage plan	Covers storage costs for OSS files of the Standard zone-redundant storage class.
Standard LRS plan	Covers storage costs for OSS files of the Standard LRS storage class or ECS snapshots. Important Once you purchase reserved capacity for a region, you can no longer purchase a Standard LRS storage plan for general use in the China mainland or one specific to that region.
IA zone-redundant storage plan	Covers storage costs for OSS files of the IA zone-redundant storage class.
IA LRS plan	Covers storage costs for OSS files of the IA LRS storage class.
Archive zone-redundant storage plan	Covers storage costs for OSS files of the archive zone-redundant storage class.
Archive LRS plan	Covers storage costs for OSS files of the archive LRS storage class.
Cold archive LRS plan	Covers storage costs for OSS files of the cold archive LRS storage class.
Data transfer plan	Covers traffic costs from using OSS.
Outbound data transfer plan	Covers traffic costs for transferring data from OSS to a client over the internet.
Back-to-origin data transfer plan	Covers back-to-origin traffic costs when data is transferred from OSS to CDN POPs.
Transfer acceleration plan	Covers traffic costs when users access OSS through an acceleration endpoint.
Request plan	Covers costs for PUT and GET requests.
Request plan - Standard storage class	Covers costs for PUT and GET requests for the Standard storage class.
Request plan - Non-standard storage class	Covers costs for PUT and GET requests for the IA, archive, and cold archive storage classes.
Anti-DDoS Basic plan	Covers costs for reserving Anti-DDoS instance resources.
OSS Accelerator plan	Covers configured capacity costs for OSS Accelerator instances.

Purchase recommendations

Recommendation 1: Select plan type by use case

A common combination of OSS resource plans is a storage plan and an outbound data transfer plan. The storage plan covers storage costs for OSS and ECS snapshots. The outbound data transfer plan covers data transfer costs for accessing OSS files over the Internet.

Scenario	Resource plan
Storing objects such as text, images, audio, and video in OSS using the Standard LRS storage class.	Standard LRS plan
Creating and retaining ECS snapshots.	Standard LRS plan
Browsing or downloading files from OSS over the Internet.	outbound data transfer plan

To learn more about the use cases for each resource plan, see Resource plan types.

Recommendation 2: Select plan type by billable items

If you have an existing OSS bill, select a resource plan based on the billable items in your detailed bill.

For example, if a billable item is Standard LRS capacity, you can purchase a Standard LRS plan to cover this cost.

On the Bill Details page, set Statistic Item to Billable Item and Statistic Period to Detailed. Then, filter by Product and select Object Storage Service to view the unit price of each billable item.

Recommendation 3: Select plan size by usage

If you have an existing OSS bill, select a resource plan size based on the usage shown in your detailed bill.

For example, if your hourly usage for Standard LRS capacity is 40 GB, purchase a 40 GB Standard LRS plan to cover this cost.

Recommendation 4: Troubleshoot unexpected charges

On the detailed bill page, check the billable item's type, usage, and billing time.
On the resource plan list page, check the type, total quota, and effective period of your active resource plan.

Compare the billable item with your resource plan.

Example problem	Solution
Your bill includes a NetworkOut billable item, but you do not have an active outbound data transfer plan.	Purchase an outbound data transfer plan.
Your bill includes a Standard LRS capacity billable item, but you do not have an active Standard LRS plan.	Purchase a Standard LRS plan.
Your bill shows 100 GB of hourly usage for Standard LRS capacity, but your Standard LRS plan has a total quota of 40 GB.	Upgrade your Standard LRS plan to 100 GB.
The charge occurred before you purchased the resource plan.	None

Limitations

An OSS resource plan covers costs only for the purchasing Alibaba Cloud account and cannot be shared.
An OSS resource plan applies only to the OSS service and does not cover other products.
An OSS resource plan covers only costs incurred after its purchase and cannot be applied retroactively.
An OSS resource plan covers costs only for its corresponding billable item. For more information, see Resource plan types.
An OSS resource plan for a specific region can offset fees only for its covered billable items in that region, while a general-purpose resource plan for the Chinese mainland can offset fees for its covered billable items across multiple regions in the Chinese mainland. For more information, see Applicable Regions.

Deduction methods

Deduction method	Resource plan	Description
fixed hourly quota	storage plan Anti-DDoS Basic plan OSS transfer acceleration plan	This method provides a fixed quota each hour. Unused quota does not carry over to the next hour. storage plan Example: A 10 TB storage plan covers up to 10 TB of storage capacity each hour. If your storage usage in the first hour is 9 TB, the storage plan covers the full storage cost. If your storage usage in the second hour is 10 TB, the storage plan covers the full storage cost. If your storage usage in the third hour is 11 TB, the storage plan covers 10 TB, and the excess 1 TB is billed on a pay-as-you-go basis. Anti-DDoS Basic plan Example: If you purchase two single-instance Anti-DDoS Basic plans with a term of six months, the plans cover the Anti-DDoS resource reservation and early release fees for up to two Anti-DDoS instances each hour. If there is only one Anti-DDoS instance in the first hour, the Anti-DDoS Basic plans fully cover its cost. If there are two Anti-DDoS instances in the second hour, the Anti-DDoS Basic plans fully cover their costs. If there are three Anti-DDoS instances in the third hour, the Anti-DDoS Basic plans cover the costs for two instances, and the excess instance is billed on a pay-as-you-go basis. OSS transfer acceleration plan Example: If you purchase a 100 GB OSS transfer acceleration plan, it covers a total of 100 GB of configured capacity for your OSS transfer acceleration instances each hour. If you create an OSS transfer acceleration instance with 50 GB of configured capacity in the first hour, the plan covers the full capacity cost. If you change the configured capacity of the instance to 100 GB in the second hour, the plan covers the full capacity cost. If you change the configured capacity of the instance to 110 GB in the third hour, the plan covers 100 GB of the capacity cost, and the excess 10 GB is billed on a pay-as-you-go basis.
fixed monthly quota	outbound data transfer plan	This method provides a fixed quota each month. The quota is reset on the 1st of the following month, and any unused quota does not roll over. Example: If you purchase a 1-month, 100 GB outbound data transfer plan on the 18th of the month, the plan covers 100 GB of outbound internet traffic from the 18th through the end of the month. Any excess usage is billed on a pay-as-you-go basis. On the 1st of the next month, the quota resets. From the 1st through the 18th of the next month, the plan again covers 100 GB, and any excess usage is billed on a pay-as-you-go basis.
total declining balance	transfer acceleration plan back-to-origin traffic plan request plan - Standard storage request plan - non-standard storage	Usage is deducted from the plan's total quota until the quota is exhausted or the plan expires. transfer acceleration plan Example: If you purchase a 5 TB plan for three months, you have a total quota of 5 TB for transfer acceleration traffic over the three-month period. Any excess usage is billed on a pay-as-you-go basis. back-to-origin traffic plan Example: If you purchase a 5 TB plan for six months, you have a total quota of 5 TB for back-to-origin traffic over the six-month period. Any excess usage is billed on a pay-as-you-go basis. request plan - Standard storage Example: If you purchase a plan for 50 million requests for one year, you have a total quota of 50 million PUT and GET requests for the Standard storage class over the one-year period. Any excess usage is billed on a pay-as-you-go basis. request plan - non-standard storage Example: If you purchase a plan for 50 million requests for one year, you have a total quota of 50 million PUT and GET requests for the Infrequent Access, Archive, and Cold Archive storage classes over the one-year period. Any excess usage is billed on a pay-as-you-go basis.

Applicable regions

When you purchase an OSS resource plan, you must specify a region. This requirement does not apply to Anti-DDoS Basic resource plans. A region-specific resource plan deducts fees incurred only in the specified region.

Note

An Anti-DDoS Basic resource plan deducts fees for Anti-DDoS instances in all available regions. Within a single hour, a plan can cover the fees for only one instance in one region. If you incur Anti-DDoS charges in multiple regions during the same hour, you must purchase additional Anti-DDoS Basic resource plans to cover the fees.

Region type	Description
Region-specific^①	Deducts fees for resource usage in a specific region. These resource plans cannot be shared across regions.^②
All regions in the Chinese mainland^①	Deducts fees for resource usage in all regions in the Chinese mainland. These resource plans can be shared across regions.^③
Transfer acceleration region	Deducts transfer acceleration traffic fees for uploads and downloads when you use an acceleration endpoint to access OSS buckets across regions.
Transfer acceleration M2M	Deducts transfer acceleration traffic fees for uploads and downloads (AccM2MIn and AccM2MOut) when you use an acceleration endpoint to access OSS buckets between regions within the Chinese mainland.
Transfer acceleration M2O_O2M	Deducts transfer acceleration traffic fees for uploads and downloads (AccM2OIn, AccM2OOut, AccO2MIn, and AccO2MOut) when you use an acceleration endpoint to access OSS buckets between regions inside and outside the Chinese mainland.
Transfer acceleration O2O	Deducts transfer acceleration traffic fees for uploads and downloads (AccO2OIn and AccO2OOut) when you use an acceleration endpoint to access OSS buckets between regions outside the Chinese mainland.

^①You can purchase both a region-specific resource plan and a plan for all regions in the Chinese mainland. When fees are deducted, the region-specific plan is consumed first. If its quota is exhausted, the plan for all Chinese mainland regions is consumed next. If both plans are exhausted, any excess usage is charged on a pay-as-you-go basis.

^②For example, a resource plan for the China (Qingdao) region deducts resource usage fees incurred only in that region.

^③For a list of the Chinese mainland regions supported by these plans, see Regions supported by resource plans that are available in all regions in the Chinese mainland.

Supported regions in the Chinese mainland

Resource plan	Region
Standard LRS storage plan	China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Nanjing - Local Region - Decommissioning), China (Fuzhou - Local Region - Decommissioning), and China (Wuhan - Local Region)
IA LRS storage plan
Archive LRS storage plan
Cold Archive LRS storage plan
Standard ZRS storage plan
IA ZRS storage plan
Archive ZRS storage plan
Outbound data transfer plan
Back-to-origin traffic plan
Request plan - Standard storage
Request plan - Infrequent Access (IA) storage
OSS-ECI acceleration plan	China (Hangzhou), China (Shanghai), China (Beijing), China (Ulanqab), and China (Shenzhen)

Important

You cannot create buckets in the China (Zhangjiakou) region. However, you can still use resource plans to deduct fees for existing buckets in this region.

Supported operations