Billing in Special Scenarios

Billing for Lifecycle Management

If you configure lifecycle rules to perform actions automatically, you may be billed. The following tables list billable items and their descriptions.

For billing details, see OBS Billing Items.

**Table 1** Billing for lifecycle management actions (during action execution)
Action	Billing Item	Description	Billing Mode
Delete after expiration	Requests	You are billed for the number of successfully deleted objects.	Pay-per-use
Delete after expiration	Storage space	If objects are deleted before they have been stored for the required minimum storage duration (180, 90 and 30 days for Deep Archive, Archive and Infrequent Access, respectively), you still need to pay for the remaining days.	Pay-per-use Resource packages
Transition from Standard to Infrequent Access	Infrequent Access PUT requests	You are billed for the number of successfully transitioned objects. If N objects are successfully transitioned, you are billed for N requests.	Pay-per-use
Transition from Standard to Archive	Archive PUT requests	You are billed for the number of successfully transitioned objects. If N objects are successfully transitioned, you are billed for N requests.	Pay-per-use
Transition from Infrequent Access to Archive	Archive PUT requests		Pay-per-use
Transition from Standard to Deep Archive	Deep Archive PUT requests	You are billed for the number of successfully transitioned objects. If N objects are successfully transitioned, you are billed for N requests.	Pay-per-use
Transition from Infrequent Access to Deep Archive	Deep Archive PUT requests
Transition from Archive to Deep Archive	Deep Archive PUT requests

**Table 2** Billing for lifecycle management actions (after action execution)
Action	Billing Item	Description	Billing Mode
Delete after expiration	N/A	After the deletion is complete, the objects no longer exist, so no further billing will apply.	N/A
Transition from Standard to Infrequent Access	Infrequent Access storage	After the transition, you will be billed for the Infrequent Access storage.	Pay-per-use
Transition from Standard to Archive	Archive storage	After the transition, you will be billed for the Archive storage.	Pay-per-use Resource packages (Archive storage)
Transition from Infrequent Access to Archive	Archive storage	After the transition, you will be billed for the Archive storage. Infrequent Access storage has a minimum storage duration of 30 days. If objects are transitioned to Archive before this period ends, you still need to pay for the remaining days of Infrequent Access storage.	Pay-per-use Resource packages (Archive storage)
Transition from Standard to Deep Archive	Deep Archive storage	After the transition, you will be billed for the Deep Archive storage.	Pay-per-use
Transition from Infrequent Access to Deep Archive	Deep Archive storage	After the transition, you will be billed for the Deep Archive storage. Infrequent Access storage has a minimum storage duration of 30 days. If objects are transitioned to Deep Archive before this period ends, you still need to pay for the remaining days of Infrequent Access storage.
Transition from Archive to Deep Archive	Deep Archive storage	After the transition, you will be billed for the Deep Archive storage. Archive storage has a minimum storage duration of 90 days. If objects are transitioned to Deep Archive before this period ends, you still need to pay for the remaining days of Archive storage.

The prices in the following example are for reference only. For the actual prices, see Pricing Details.

Example: Billing for transition from Infrequent Access to Archive and deletion

Assume that you had 1,000 objects, 100 GB in total, in the CN-Hong Kong region. From April 1 to April 30, 2025, they were stored in the Infrequent Access (single-AZ) storage class. On May 1, 2025, they were transitioned to Archive (single-AZ) storage. On May 30, 2025, they were expired and then deleted. In this case, you were billed for 30 days of Infrequent Access single-AZ storage, 90 days of Archive storage (including 30 days of actual storage and the remaining 60 days of Archive storage), and 1,000 Archive PUT requests. Specific billing analysis is given as follows:

Pay-per-use billing:

Infrequent Access single-AZ storage cost = ($0.0140 USD per GB-month)/30 × 100 GB × 30 days = $1.40 USD

Archive storage cost = ($0.0045 USD per GB-month)/30 × 100 GB × 90 days = $1.35 USD

Archive PUT request cost = $0.0050 USD per 1,000 requests × (1,000 requests/1,000 requests) = $0.005 USD

The total cost is as follows:

Total cost = Infrequent Access single-AZ storage cost + Archive storage cost + Archive PUT request cost = 1.40 + 1.35 + 0.005 = $2.755 USD

Billing for Object Restore

You must restore objects in the Infrequent Access or Archive or Deep Archive storage class before you can download them, access them with URLs, or configure the ACL and metadata for them. The table below lists the items you might be billed for during object restore.

**Table 3** Billing for object restore
Action	Billing Item	Description	Billing Mode
Restore objects	Requests	You are billed for the number of successfully restored objects. Specifically, if N objects are successfully restored, you are billed for N requests. When you access Infrequent Access objects, OBS automatically restores them. The restore requests incur costs, which are the same as those for restoring Archive and Deep Archive objects.	Pay-per-use
	Restore traffic	You are billed based on the amount of data restored and the restore speed (either expedited or standard). During the validity period, no more restore traffic costs are generated.	Pay-per-use
	Outbound Internet traffic (when objects are accessed over the Internet)	If you access the restored objects over the Internet, you will be billed for the outbound Internet traffic based on the object size.	Pay-per-use
	Temporary storage	After an object is restored, an object copy in the Standard storage class will be generated. This way, there is both the original Archive or Deep Archive object and its Standard object copy in the bucket. When you restore an object, you will be billed a one-time storage cost for its Standard copy. After the validity period expires, the Standard copy is automatically deleted. Retrieving Infrequent Access objects or retrieving Archive objects from a bucket with direct reading enabled does not create object copies, so there will not be additional costs on Standard storage.	Pay-per-use

Billing for Direct Reading

In certain scenarios, you may need to access Archive objects without restoring them first. To do this, you can enable direct reading for the bucket, which allows you to access Archive objects directly. The table below outlines the billing items associated with direct reading.

**Table 4** Billing for direct reading
Action	Billing Item	Description	Billing Mode
Direct reading	Requests	You are billed for the number of successfully read objects. If N objects are successfully read, you are billed for N requests.	Pay-per-use
	Direct reading traffic	Traffic for downloading and replicating Archive objects from a bucket with direct reading enabled. For more information, see Direct Reading. The amount of data retrieved is determined by the range specified in the request header when the HTTP connection is established. Even if the transmission is interrupted early, the system calculates usage based on the full range defined in the original request. For example, if the request specifies a range from 50 MB to 100 MB, the system still bills you for the range of 50 MB to 100 MB, even if only one byte is actually transmitted.	Pay-per-use
	Outbound Internet traffic (when objects are accessed over the Internet)	If you download or replicate objects over the Internet, the outbound Internet traffic costs will be incurred based on the object size.	Pay-per-use

The prices in the following example are for reference only. For the actual prices, see Pricing Details.

Example: Billing for downloading objects from a bucket with or without direct reading enabled

Assume that you need to download 100 Archive objects (100 GB in total) over the Internet. The following table compares the billing for downloading these objects from a bucket with direct reading enabled or disabled.

**Table 5** Billing for downloading objects from a bucket with or without direct reading enabled
Billing Item	A Bucket Without Direct Reading Enabled	A Bucket With Direct Reading Enabled
Restore requests	100 PUT requests	N/A
Download requests	100 GET requests	100 GET requests
Temporary storage	Storage for 100 GB of Standard copies, which is charged once	N/A
Restore traffic	Assume that you use expedited restore, there will be traffic for restoring 100 GB of data at an expedited speed.	N/A
Direct reading traffic	N/A	Direct reading traffic for 100 GB of data
Outbound Internet traffic	Outbound Internet traffic for 100 GB of data	Outbound Internet traffic for 100 GB of data

Billing for Data Replication in the Same Region

If you replicate objects from one bucket to another in the same region using OBS Browser+, obsutil, SDKs, or APIs, you may be billed for the items listed in the table below.

**Table 6** Billing for data replication in the same region
Action	Billing Item	Description	Billing Mode
Replicate data in the same region	Requests	You are billed for the number of successfully replicated objects. Successfully replicating one object creates a copy request. For details, see Copying Objects. To learn about the request billing, see Requests.	Pay-per-use
	Data transfer	Free, because data in the same region is replicated over an intranet.	N/A
	Storage space	Storage space occupied by objects stored in the destination bucket. If you have specified another storage class for object copies in the destination bucket, these copies are billed based on the new storage class.	Pay-per-use Resource packages

Billing for Cross-Region Replication

Figure 1 shows the items that will be billed when data is replicated from one region to another.

Figure 1 Items billed for cross-region replication
Click to enlarge

**Table 7** Billing for data replication across regions
Action	Billing Item	Description	Billing Mode
Replicate data across regions	Requests	You are billed for the number of successfully replicated objects. Successfully replicating one object creates a copy request. For details, see Copying Objects. For non-multipart objects, replicating an object creates a GET request to the source bucket and a PUT request to the destination bucket; deleting an object from the source bucket creates a DELETE request to the destination bucket. For multipart objects, replicating each part creates a GET request to the source bucket and a PUT request to the destination bucket. For details about how requests are billed, see Requests.	Pay-per-use
	Data transfer	Traffic generated when you replicate data from the source bucket to the destination bucket in another region. Billing only applies to the data transferred out of the source bucket. If objects are encrypted using server-side encryption, the cost of their cross-region replication traffic is calculated based on the length of the plaintext for SSE-KMS and SSE-OBS.	Pay-per-use
	Storage space	Space occupied by the replicated objects in the destination bucket If you have specified another storage class for object copies in the destination bucket, these copies are billed based on the new storage class. If objects are encrypted using server-side encryption, their storage cost is calculated based on the length of the ciphertext.	Pay-per-use Resource packages
Synchronize existing objects	Requests	You are billed for the number of existing objects that are successfully replicated to the destination bucket. Billing applies to the number of objects that are successfully replicated. You are also billed for listing the existing objects.	Pay-per-use
	Data transfer	Traffic generated when OBS replicates existing objects to the destination bucket in another region. Billing only applies to the data transferred out of the source bucket. If historical objects are encrypted using server-side encryption, the cost of their cross-region replication traffic is calculated based on the length of the plaintext for SSE-KMS and SSE-OBS.	Pay-per-use
	Storage space	Space occupied by the replicated objects in the destination bucket If you have specified another storage class for object copies in the destination bucket, these copies are billed based on the new storage class. If historical objects are encrypted using server-side encryption, their storage cost is calculated based on the length of the ciphertext.	Pay-per-use Resource packages

Billing for CDN-Accelerated Access to OBS

If you use Huawei Cloud CDN to accelerate access to the data stored in OBS, you will be billed for using both OBS and CDN.

Figure 2 shows how and what costs are generated.

Figure 2 Using CDN to access OBS
Click to enlarge

Table 8 describes the billing items in detail.

**Table 8** Billing for using CDN to access OBS
Billing Item	Billing Party	Description	Billing Mode
Requests	OBS	When you attempt to access data the first time, a CDN edge node will send a request to pull data from the origin server (OBS). OBS bills you for the API calls. For details, see Requests.	Pay-per-use
CDN pull traffic	OBS	Pull traffic generated when the origin server (OBS 3.0 bucket) returns data and caches it on the CDN edge PoP. If Direct Connect is used, the price will be different. For details, see Product Pricing Details. Such traffic is only for OBS 3.0 buckets. If data is pulled from OBS 2.0 buckets, the data is directly transferred out over the Internet.	Pay-per-use
CDN traffic	CDN	Outbound traffic generated when you access a CDN edge PoP. For details, see Billing by Traffic.	Pay-per-use Resource packages (prepaid CDN traffic packages)

Billing for Back to Source by Mirroring

If the data you requested is not found in a bucket with a back-to-source by mirroring rule configured and the data meets the specified back-to-source conditions, OBS will pull the data from the origin server and then return it to you.

**Table 9** Billing for back to source by mirroring
Action	Billing Item	Description	Billing Mode
Perform back to source by mirroring	Requests	If the data you requested the first time is not found in OBS, OBS will send a request to pull it from the origin server. OBS bills you for the API calls. For details, see Requests.	Pay-per-use
Perform back to source by mirroring	Storage space	Space occupied by data pulled from the origin server. The pulled data is stored in the Standard storage class in OBS.	Pay-per-use Standard storage resource packages (single-AZ or multi-AZ)