Storage usage refers to the used storage capacity. You are charged by the objects' size and how long you stored them. For different storage classes, the unit price, minimum object size, and minimum storage duration are different as described below. The actual costs depend on the use case and storage class of the object.
Note:For more information on storage classes, see Storage Class Overview.
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
STANDARD storage usage refers to the size of your data stored in the STANDARD storage class. You will be charged by the actual STANDARD storage usage and how long you store the data. | All regions | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
MAZ_STANDARD storage usage refers to the size of your data stored in the MAZ_STANDARD storage class. You will be charged by the actual MAZ_STANDARD storage usage and how long you store the data. | Beijing, Shanghai, Guangzhou | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
STANDARD_IA storage usage refers to the size of your data stored in the STANDARD_IA storage class. You will be charged depending on the actual use case:
|
All regions | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
MAZ_STANDARD_IA storage usage refers to the size of your data stored in the MAZ_STANDARD_IA storage class. You will be charged depending on the actual use case:
|
Beijing, Shanghai, Guangzhou | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
INTELLIGENT TIERING storage usage refers to the size of your data stored in the INTELLIGENT TIERING storage class. You will be charged depending on the actual use case:
|
Beijing, Nanjing, Shanghai, Guangzhou, Chengdu, Chongqing, Tokyo, and Singapore | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
MAZ_INTELLIGENT TIERING storage usage refers to the size of your data stored in the MAZ_INTELLIGENT TIERING storage class. You will be charged depending on the actual use case:
|
Beijing, Shanghai, Guangzhou | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
ARCHIVE storage usage refers to the size of your data stored in the ARCHIVE storage class. You will be charged depending on the actual use case:
|
All public cloud regions (except Jakarta), Shenzhen Finance | Pay-as-you-go |
Billable Item Description | Applicable Region | Applicable Billing Mode |
---|---|---|
DEEP ARCHIVE storage usage refers to the size of your data stored in the DEEP ARCHIVE storage class. You will be charged depending on the actual use case:
|
Beijing, Nanjing, Shanghai, Guangzhou, Chengdu, Chongqing, Tokyo, and Singapore | Pay-as-you-go |
Description | Involved Storage Class |
---|---|
Early deletion refers to the deletion of an object in the STANDARD_IA, MAZ_STANDARD_IA, ARCHIVE, or DEEP ARCHIVE storage class performed before it meets the minimum storage duration requirement after being uploaded. Note: Early deletion fees will be incurred in storage classes with the minimum storage duration requirement, i.e., STANDARD_IA, MAZ_STANDARD_IA, ARCHIVE, and DEEP ARCHIVE. Billing rule: The following operations may cause early deletion: 1. You delete an object in advance before it meets the minimum storage duration requirement. 2. You modify the attributes of an object before it meets the minimum storage duration requirement, such as custom header or storage class. In this case, COS will delete the original object after successful modification, and storage fees incurred by early object deletion will be charged. 3. You upload an object with the same name as an existing object to a bucket with versioning not enabled before the existing object meets the minimum storage duration requirement. In this case, COS will delete the existing object, and storage fees incurred by early object deletion will be charged. |
STANDARD_IA MAZ_STANDARD_IA ARCHIVE DEEP ARCHIVE |
Billing Mode | Calculation Formula |
---|---|
Pay-as-you-go |
|
Note:
For the unit prices of storage usage, see Pricing | Cloud Object Storage.
Note:
- Prices in the examples below are for reference only. For the actual prices, see Pricing | Cloud Object Storage.
- The storage capacity is calculated in binary, for example, 1 TB = 1024 GB.
Assume that on November 1, 2020, user A uploaded 10 GB of data to a bucket residing in Guangzhou region in the STANDARD storage class, generating 100 requests. Apart from this, user A did not perform any other operations in November. As fees for Mona day were settled the next day:
Fees analysis:
In summary, the total bill for user A in November is calculated as follows: 0.24 + 0.00002 = 0.24002 USD.
Assume that on November 1, 2020, user B uploaded 10 GB of data (including 10,000 pieces of 30 KB objects) to a bucket residing in Guangzhou region in the STANDARD_IA storage class, generating 100 requests. Apart from this, user B did not perform any other operations in November. As fees for a day were settled the next day:
Fees analysis:
In summary, the total bill for user B in November is calculated as follows: 0.19 + 0.0001 = 0.1901 USD.
Apakah halaman ini membantu?