Billing in Special Scenarios

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
Delete after expiration	Requests	You are billed for the number of successfully deleted objects.
Delete after expiration	Storage space	If objects are deleted before they have been stored for the required minimum duration (180, 90, and 30 days for Deep Archive, Archive, and Infrequent Access storage, respectively), you still need to pay for the remaining days.
Transition from Standard to Infrequent Access	Requests	You are billed for the number of successfully transitioned objects. Specifically, if N objects are successfully transitioned, you are billed for N requests.
Transition from Standard to Archive	Requests
Transition from Infrequent Access to Archive	Requests
Transition from Standard to Deep Archive	Requests	You are billed for the number of successfully transitioned objects. Specifically, if N objects are successfully transitioned, you are billed for N requests.
Transition from Infrequent Access to Deep Archive	Requests
Transition from Archive to Deep Archive	Requests

**Table 2** Billing for lifecycle management actions (after action execution)
Action	Billing Item	Description
Delete after expiration	N/A	N/A
Transition from Standard to Infrequent Access	Storage space	After the transition, you will be billed for the Infrequent Access storage.
Transition from Standard to Archive	Storage space	After the transition, you will be billed for the Archive storage.
Transition from Infrequent Access to Archive	Storage space	After the transition, you will be billed for the Archive storage. If Infrequent Access objects are transitioned to Archive before they have been stored for the required minimum duration (30 days), you still need to pay for Infrequent Access storage of the remaining days.
Transition from Standard to Deep Archive	Storage space	After the transition, you will be billed for the Deep Archive storage.
Transition from Infrequent Access to Deep Archive	Storage space	After the transition, you will be billed for the Deep Archive storage. If Infrequent Access objects are transitioned to Deep Archive before they have been stored for the required minimum duration (30 days), you still need to pay for Infrequent Access storage of the remaining days.
Transition from Archive to Deep Archive	Storage space	After the transition, you will be billed for the Deep Archive storage. If Archive objects are transitioned to Deep Archive before they have been stored for the required minimum duration (90 days), you still need to pay for Archive storage of the remaining days.

Restore of Archive or Deep Archive Objects

You must restore objects in the Archive or Deep Archive storage class before you can download them, access them with URL, 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 restoring Archive or Deep Archive objects
Action	Billing Item	Description
Restoring 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.
	Data transfer	You are billed for the data restore traffic.
	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. During the copy retention period, you will be billed for the storage space occupied by both the object and its copy. The Standard object copy will be automatically deleted after it expires.

Cross-Bucket Replication in the Same Region

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

**Table 4** Billing for cross-bucket replication
Action	Billing Item	Description
Replicate data across buckets 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.
	Data transfer	Free, because data in the same region is replicated over an intranet.
	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.

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

**Table 5** Billing for cross-region replication
Action	Billing Item	Description
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. To learn about the request billing, see Requests.
	Data transfer	You are billed for the amount of data transferred from one region to another.
	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.
Synchronize existing objects	Requests	You are billed for the number of existing objects that are successfully replicated to the destination bucket. With synchronization of existing objects enabled, OBS synchronously replicates the objects that already exist in the bucket before a cross-region replication rule is created to the destination bucket.
	Data transfer	You are billed for the traffic generated when OBS synchronizes objects across regions.
	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.

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

Table 6 describes the billing items in detail.

**Table 6** Billing for using CDN to access OBS
Billing Item	Billing Party	Description
Requests	OBS	When you access data the first time, a CDN edge node will pull data from the origin server (OBS). During this process, CDN sends requests to OBS. OBS bills you for the API calls. For details, see Requests.
CDN pull traffic	OBS	Pull traffic generated when the origin server returns data and caches it on the CDN node. 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.
CDN traffic	CDN	Outbound traffic generated when you access a CDN node. For details, see CDN Traffic Billing.

Back to Source by Mirroring

If the data you requested is not found in a bucket with a mirroring back-to-source 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 7** Billing for back to source by mirroring
Action	Billing Item	Description
Perform mirroring-based back to source	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.
Perform mirroring-based back to source	Storage space	Space occupied by data pulled from the origin server. The pulled data is stored in the Standard storage class in OBS.