Overview
Resource packages (prepaid) are discounted packages offered by COS for different billable items. You can purchase different resource packages for deduction of the usage of billable items such as storage, requests, and traffic. Compared with pay-as-you-go billing, resource packages are cheaper and available only in public cloud regions (not in finance cloud regions), and you can choose to purchase them on your own.
This document describes resource packages (prepaid). A resource package consists of one or multiple billable items. Compared with pay-as-you-go billing, resource packages are cheaper. Currently, available types of resource packages cover most billable items of COS, and you can purchase them based on your business needs.
Pricing
Purchase Entrance
Purchase Notes
Resource packages are available only in public cloud regions, not in finance cloud regions. For more information on regions, see Regions and Access Endpoints.
Resource packs can only be used to deduct resource costs generated by storage buckets in the same general region (such as a public cloud region in the Chinese mainland, not a finance cloud region). Therefore, be sure to select a resource pack in the same region as your bucket.
Resource packs are prepaid and can be configured to take effect immediately or at a specified time based on your actual use case. If a resource pack is configured to take effect immediately, it will take effect immediately on the day of purchase without any operation required. If a resource pack is configured to take effect at a specified time, it will take effect at the specified time, and your usage will be billed on a pay-as-you-go model before the resource pack takes effect.
For resource packages purchased or renewed before December 1, 2021, the period of one month is calculated as 30 days. For resource packages purchased or renewed on or after December 1, 2021, the period of one month is calculated from the effective date and will expire on the same day of the following month. Special cases are described as follows:
If a resource package takes effect on the last day of the current month, it will expire on the last day of the target month.
If the effective date of the resource pack exceeds the total number of days in the target month, it will expire on the last day of the target month.. For example, if a resource package with 1-month period takes effect on January 30, it will expire on February 28 or 29.
Resource packs can be purchased for multiple cycles, and in such cases, the resource pack resetting date will be applicable. For more information, see Validity Period.
The unused portion of a resource package in a cycle does not carry over to the next cycle.
A self-service refund is supported for resource packs. If you purchase an inappropriate resource pack by mistake, you can request a self-service refund refund if the refund conditions are met.
Multiple resource packs can be used together. If you purchase multiple resource packs at a time, their specifications can be combined, but their validity periods will not. For more information on the validity period, see Validity Period.
After a resource package expires or is used up, you don't need to migrate the data in your bucket, and pay-as-you-go billing will be adopted.
While a resource package is effective, bills will be settled in the following sequence: free tier > resource package > pay-as-you-go. Usage beyond the free tier and the resource package's quota will be billed using the pay-as-you-go model.
If an account has overdue payments (the account's balance is below 0), COS service will be suspended after 24 hours, regardless of whether the resource package is still effective.
Currently, resource packages are available only for certain billable items (such as storage and requests). During the use of COS, other fees (such as data retrieval fees and management feature fees) may be incurred and will be charged based on your actual usage.
Note:
The billing unit of the storage capacity billing item and storage capacity packages is GB, and the capacity unit conversion ratio is 1:1,024.For example, 1 TB of standard storage capacity equals 1,024 GB. A standard storage capacity package of 1 TB can deduct fees of 1,024 GB of standard storage capacity.
The billing unit of the traffic billing item and traffic packages is GB, and the traffic unit conversion ratio is 1:1,024.For example, 1 TB of public network downstream traffic equals 1,024 GB. A public network downstream traffic package of 1 TB can deduct fees of 1,024 GB of public network downstream traffic.This conversion rule will take effect from April 1, 2025.
The billing unit for read and write requests, as well as request packages, is 10,000 requests, with each request representing 10,000 units. For example, 10,000 STANDARD storage write requests are equivalent to 10,000 requests. A package of 100,000 STANDARD storage requests would be converted to 100,000 STANDARD storage requests.
Applicable Regions
Resource packages are classified into resource packages for regions in the Chinese mainland and resource packages for regions outside the Chinese mainland by region.
Resource packages for regions in the Chinese mainland are available in public cloud regions in the Chinese mainland, not in finance cloud regions.
Resource packages for regions outside the Chinese mainland apply to regions outside the Chinese mainland.
Types and Deduction Rules
The resource packages are classified by type in the following table:
Note:
For more information on the billable items as described in the table, see Billable Items.
Currently, INTELLIGENT TIERING storage capacity packs are only supported in Beijing, Nanjing, Shanghai, Guangzhou, Chengdu, Chongqing, Tokyo, and Singapore regions, while DEEP_ARCHIVE storage capacity packs are only supported in Beijing, Nanjing, Shanghai, Guangzhou, Chengdu, Chongqing, Tokyo, and Singapore regions.
When a resource pack is used up or expires, the billing mode will be automatically switched to pay-as-you-go billing. To avoid incurring additional fees, we recommend that you promptly upgrade or renew the resource pack.
Resource Package Type | Resource Package Description | Resource Package Deduction Rules |
Storage Package | There are several types of storage packages: Standard Storage Package: Applies to the deduction of standard storage usage fees, but cannot be used to deduct Multi-AZ standard storage usage fees. Infrequent Access Storage Package: Applies to deduction of Infrequent Access storage usage fees, but cannot be used to deduct multi-AZ Infrequent Access storage usage fees. Intelligent Tiering Storage Package: Applies to the deduction of Intelligent Tiering storage usage fees, but cannot be used to deduct storage usage fees for multi-AZ Intelligent Tiering storage. Archive Storage Capacity Pack: Applies to deduction of archive storage usage fees, suitable for data settled to COS archive storage type through COS lifecycle and also applicable to data directly uploaded to the archive storage type. DEEP ARCHIVE Storage Package: Applies to the deduction of DEEP ARCHIVE storage usage fees. | The average storage usage of the day is deducted every day, and the quota is reset every day. Example: Xiao Yun purchases a 20 GB STANDARD storage package on the 1st of the month. His storage bucket has 10 GB of STANDARD storage on the 1st, increases to 20 GB on the 2nd, and 30 GB on the 3rd. The 20 GB package can deduct 10 GB on the 1st, 20 GB on the 2nd and 3rd, with an excess of 10 GB on the 3rd, which will be charged on a pay-as-you-go basis. |
Request Package | The following types of request packages are available: STANDARD request package: Applies to deduction of STANDARD read/write requests. STANDARD_IA request package: Applies to deduction of STANDARD_IA read/write requests. | The total number of requests of the day is deducted every day, and the quota is reset every month. For example, if you purchased a STANDARD request package of 1,000,000 requests on the 1st day of the month, and your bucket generated 100,000 requests every day from the 1st day to the 3rd day, then 100,000 requests would be deducted from the request package every day from the 1st day to the 3rd day, and there would still be 700,000 requests available on the 4th day. |
Public Network Downstream Traffic Package | Applies to deduction of public network downstream traffic | The total amount of traffic of the day is deducted every day, and the quota is reset every month. For example, if you purchased a public network downstream traffic package of 100 GB on the 1st day of the month, and your bucket generated 10 GB of public network downstream traffic every day from the 1st day to the 3rd day, then 10 GB of traffic would be deducted from the traffic package every day from the 1st day to the 3rd day, and there would still be 70 GB of traffic available on the 4th day. |
CDN Origin-Pull Traffic Package | Used for deducting CDN/EdgeOne origin-pull traffic fees. | The total amount of traffic of the day is deducted every day, and the quota is reset every month. Example: Xiao Yun purchased a 100 GB CDN origin-pull traffic package. His storage bucket generates 10 GB of CDN origin-pull traffic daily from the 1st to the 3rd. The 100 GB traffic package will deduct 10 GB of traffic each day from the 1st to the 3rd, leaving 70 GB of traffic available for use on the 4th. |
Cross-Region Replication Traffic Package | Used for deducting cross-region replication traffic fees. | The total amount of traffic of the day is deducted every day, and the quota is reset every month. Example: Xiao Yun purchased a 100 GB cross-region replication traffic pack for regions in the Chinese mainland. They configured a cross-region replication rule for their Guangzhou storage bucket to replicate new data to a storage bucket in Hong Kong (China). From the 1st to the 3rd of the month, 10 GB of cross-region replication traffic was generated daily. The 100 GB traffic pack will deduct 10 GB of traffic each day from the 1st to the 3rd, leaving 70 GB of traffic available for use on the 4th. |
Global Acceleration Traffic Package | Used to deduct global accelerated traffic costs, including public network global accelerated traffic and private global accelerated traffic. Global acceleration traffic packages are divided into the following categories according to the data transfer acceleration direction: For regions in the Chinese mainland: Applies to deduction of global acceleration traffic (upstream and downstream) generated by transfer between regions in the Chinese mainland, not finance cloud regions. For regions outside the Chinese mainland: Applies to global acceleration traffic (upstream and downstream) generated by transfer between regions in the Chinese mainland and outside the Chinese mainland or between regions outside the Chinese mainland. | The total amount of traffic of the day is deducted every day, and the quota is reset every month. For example, if you purchased a global acceleration traffic package of 100 GB, and your bucket generated 10 GB of global acceleration traffic every day from the 1st day to the 3rd day, then 10 GB of traffic would be deducted from the traffic package every day from the 1st day to the 3rd day, and there would still be 70 GB of traffic available for deduction on the 4th day. |
Specifications
Different types of resource packages have different specifications. For more information, see Resource Package Purchase Page.
Validity Period Options
Note:
Note:
Starting from December 1, 2021, the validity period policy for COS resource packs has been adjusted as follows:
For resource packs purchased or renewed before December 1, 2021, the validity period of one month is calculated as 30 days. To ensure you enjoy the best discount, historical resource packs support renewal, and the renewal duration is calculated according to the new validity period policy.
For resource packs purchased or renewed after December 1, 2021, the validity period is one month, starting from the effective date and expiring on the same day of the following month. The following are explanations for special cases:
If the resource pack becomes effective on the last day of the month, the expiration date will be the last day of the target month.
If the effective date of the resource pack is greater than the total number of days in the target month, the expiration date will be the last day of the target month. For example, if the resource pack becomes effective on January 30th, it will expire on February 28th or 29th. For more information, see the calculation logic for the validity period duration below.
Starting from March 7, 2022, the extension operation for COS resource packs has been renamed to renewal operation.
Definition
1. Validity period: A period of time from the effective date to the expiration time of a resource pack.
2. Resetting date: The date on which the specification of a resource pack is reset, after which you will get the same amount of usage as the specification.
Storage pack: The usage of a resource pack is reset every day during its validity period. The resetting date is subject to the validity period, not the purchase date.
Read/Write request pack and traffic pack: The usage of a resource pack is reset every cycle during its validity period. The resetting date is subject to the validity period, not the purchase date. If you purchase a resource pack with a validity period of three months, and one month is a cycle by default, then the resource pack has two resetting dates.
3. Cycle: The validity period of a resource pack is divided into several cycles, and one month is a cycle by default. If you purchase a resource pack with a validity period of three months, the resource pack has three cycles.
To view the resource pack cycle division, go to COS Console > Resource Packages Management > Self-purchased Resource Packages > Operation, and click on Usage Details to view the cycle division of the resource pack, as well as the usage details of the current and historical cycles.
To view the resource pack reset date, go to COS Console > Resource Packages Management > Self-purchased Resource Packages > Usage Description.
For example:
1. If you purchased a STANDARD storage pack of 10 GB with a validity period of one month on December 1, 2021, then:
Validity period: From 00:00:00 on December 1, 2021 to 23:59:59 on January 1, 2022.
Resetting date: The resource pack will be reset to 10 GB every day during its validity period, that is, 10 GB of STANDARD storage usage can be deducted every day.
Cycle: The resource pack has only one cycle, i.e., from December 1, 2021 to January 1, 2022.
2. If you purchased a public network downstream traffic pack of 10 GB with a validity period of three months on December 1, 2021, then:
Validity period: From 00:00:00 on December 1, 2021 to 23:59:59 on March 1, 2022.
Resetting date: The resource pack has two resetting dates: 24:00:00 on January 1, 2022 (i.e., 00:00:00 on January 2, 2022) and 24:00:00 on February 1, 2022 (i.e., 00:00:00 on February 2, 2022). You can get new 10 GB of public network downstream traffic on each resetting date for deduction of the public network downstream traffic generated in the current cycle.
Cycle: The resource pack has three cycles: From December 1, 2021 to January 1, 2022, from January 2, 2022 to February 1, 2022, and from February 2, 2022 to March 1, 2022.
Calculation logic
Validity period and reset date of a purchased resource package
Note: If you purchased a traffic pack or read/write request pack with a validity period of N month(s) on a day (B) in a month (A), then the resource pack would expire on the same day (B) in the month (A+N) and be reset at 24:00:00 on the same day (B) every month, and have (N-1) resetting dates and N cycles.
Logic:
1. If the resource pack becomes effective on the last day of the month, the expiration date will be the last day of the target month.
2. If the effective date of the resource pack is greater than the total number of days in the target month, the expiration date will be the last day of the target month. For example, if the resource pack becomes effective on January 30th, it will expire on February 28th or 29th. For more information, see the calculation logic for the validity period duration below.
For example:
Resource Package Type | Action | Duration | Purchase Date | Effective time | Expiration Time | Resetting Time |
Public Network Downstream Traffic Package | Purchase | One month | 2021.12.01 | 2021.12.01 00:00:00 | 2022.01.01 23:59:59 | —— |
Public Network Downstream Traffic Package | Purchase | 2 months | 2021.12.01 | 2021.12.01 00:00:00 | 2022.02.01 23:59:59 | 2022.01.01 24:00:00 |
Public Network Downstream Traffic Package | Purchase | Three months | 2021.12.01 | 2021.12.01 00:00:00 | 2022.03.01 23:59:59 | 2022.01.01 24:00:00、2022.02.01 24:00:00 |
Public Network Downstream Traffic Package | Purchase | One month | 2021.12.15 | 2021.12.15 00:00:00 | 2022.01.15 23:59:59 | —— |
Public Network Downstream Traffic Package | Purchase | 2 months | 2021.12.15 | 2021.12.15 00:00:00 | 2022.02.15 23:59:59 | 2022.01.15 24:00:00 |
Public Network Downstream Traffic Package | Purchase | Three months | 2021.12.15 | 2021.12.15 00:00:00 | 2022.03.15 23:59:59 | 2022.01.15 24:00:00、2022.02.15 24:00:00 |
Public Network Downstream Traffic Package | Purchase | One month | 2021.12.29 | 2021.12.29 00:00:00 | 2022.01.29 23:59:59 | —— |
Public Network Downstream Traffic Package | Purchase | 2 months | 2021.12.29 | 2021.12.29 00:00:00 | 2022.02.28 23:59:59 | 2022.01.29 24:00:00 |
Public Network Downstream Traffic Package | Purchase | Three months | 2021.12.29 | 2021.12.29 00:00:00 | 2022.03.29 23:59:59 | 2022.01.29 24:00:00、2022.02.28 24:00:00 |
Validity period of a renewed resource package: the same as a purchased resource package
Note: If you purchased a traffic pack or read/write request pack with a validity period of N month(s) on a day (B) in a month (A) and renewed it for M month(s), the resource pack would expire on the same day (B) in the month (A+N+M) and be reset at 24:00:00 on the same day (B) every month, and have (N+M-1) resetting dates and (N+M) cycles.
Logic:
1. If the resource pack becomes effective on the last day of the month, the expiration date will be the last day of the target month.
2. If the effective date of the resource pack is greater than the total number of days in the target month, the expiration date will be the last day of the target month. For example, if the resource pack becomes effective on January 30th, it will expire on February 28th or 29th. For more information, see the calculation logic for the validity period duration below.
For example:
Resource Package Type | Action | Duration | Purchase Date | Effective time | Expiration Time Before Renewal | Renewal Duration | Expiration Time After Renewal | Resetting Time |
Public Network Downstream Traffic Package | Purchase and renewal before expiration | One month | 2021.12.01 | 2021.12.01 00:00:00 | 2022.01.01 23:59:59 | One month | 2022.02.01 23:59:59 | 2022.01.01 24:00:00 |
Public Network Downstream Traffic Package | Purchase and renewal before expiration | One month | 2021.12.01 | 2021.12.01 00:00:00 | 2022.01.01 23:59:59 | 2 months | 2022.03.01 23:59:59 | 2022.01.01 24:00:00、2022.02.01 24:00:00 |
Public Network Downstream Traffic Package | Purchase and renewal before expiration | One month | 2021.12.15 | 2021.12.15 00:00:00 | 2022.01.15 23:59:59 | One month | 2022.02.15 23:59:59 | 2022.01.15 24:00:00 |
Public Network Downstream Traffic Package | Purchase and renewal before expiration | One month | 2021.12.15 | 2021.12.15 00:00:00 | 2022.01.15 23:59:59 | 2 months | 2022.03.15 23:59:59 | 2022.01.15 24:00:00、2022.02.15 24:00:00 |
Public Network Downstream Traffic Package | Purchase and renewal before expiration | One month | 2021.12.29 | 2021.12.29 00:00:00 | 2022.01.29 23:59:59 | One month | 2022.02.28 23:59:59 | 2022.01.29 24:00:00 |
Public Network Downstream Traffic Package | Purchase and renewal before expiration | One month | 2021.12.29 | 2021.12.29 00:00:00 | 2022.01.29 23:59:59 | 2 months | 2022.03.29 23:59:59 | 2022.01.29 24:00:00、2022.02.28 24:00:00 |
Examples
Deduction example
Assume that you purchased two STANDARD storage packs of 200 GB for regions in the Chinese mainland with a validity period of three months and two public network downstream traffic packs of 200 GB for regions in the Chinese mainland with a validity period of three months on January 15, 2019, then:
Resource Package Type | Deduction Description | Validity Period |
Two STANDARD storage packs | Within the validity period, they could be applied to deduction of 400 GB of STANDARD storage used by buckets in public cloud regions in the Chinese mainland (not finance cloud regions). | January 15, 2019 to April 14, 2019 |
Two public network downstream traffic packs | Every month (30 days), they could be applied to deduction of 400 GB of public network downstream traffic generated by buckets in public cloud regions in the Chinese mainland (not finance cloud regions). | January 15, 2019 to April 14, 2019 |
Deduction order example
Assume that you purchased a STANDARD storage pack of 500 GB for regions in the Chinese mainland, and the resource pack was within the validity period. The following describes the deduction order of resource packs in different use cases:
Different unit price usage scenarios
If 700 GB of STANDARD storage data was uploaded to a Guangzhou storage bucket and 300 GB of STANDARD storage data was uploaded to a Chengdu storage bucket on the same day, the higher unit price priority deduction rule will be applied. The 500 GB STANDARD storage pack will be prioritized to deduct the STANDARD storage usage of the Guangzhou storage bucket.
Same unit price usage scenario
If 700 GB of STANDARD storage data was uploaded to a Guangzhou storage bucket and 300 GB of STANDARD storage data was uploaded to a Beijing storage bucket on the same day, the 500 GB STANDARD storage pack will be deducted in the following order: Shanghai > Guangzhou > Beijing 1 > Singapore > Chengdu > Hong Kong, China > Toronto > Frankfurt > Beijing > Seoul > Mumbai > Virginia > Silicon Valley > Bangkok > Tokyo > Nanjing > Jakarta > São Paulo > Chongqing.
Examples of deduction items and regions
Assume that you purchased a STANDARD storage pack of 200 GB for regions in the Chinese mainland with a validity period of three months on January 15, 2019.
If, from January 15 to January 31, your bucket in Guangzhou region used 100 GB of STANDARD storage, 50 GB of STANDARD_IA storage, and 1 million read/write requests and downloaded 10 GB of data over the public network, and your bucket in Singapore region used 50 GB of STANDARD storage, then:
Billing Items Generated | Whether the Resource Package is Effective |
100 GB of STANDARD storage usage in Guangzhou region | Yes. The resource pack would be applied to deduction of 100 GB of STANDARD storage usage every day during the validity period. |
50 GB of STANDARD_IA storage usage in Guangzhou region | No. The resource pack could not be applied to deduction of STANDARD_IA storage usage, which would be billed on a pay-as-you-go basis. |
1 million read/write requests in Guangzhou region | No. The resource pack could not be applied to deduction of read/write requests, which would be billed on a pay-as-you-go basis. |
10 GB of public network downstream traffic in Guangzhou region | No. The resource pack could not be applied to deduction of public network downstream traffic, which would be billed on a pay-as-you-go basis. |
50 GB of STANDARD storage usage in Singapore region | No. The resource pack could not be applied to deduction of your usage in Singapore region, which would be billed on a pay-as-you-go basis. |
Note
To learn more about the detailed cost calculation of COS and billing details in different scenarios, see Billing Examples.
Purchase/Renewal/Upgrade/Refund
For detailed directions, see the following documents: