Object Storage Service:How am I charged if I use lifecycle rules to convert the storage class of objects or delete objects?

API operation calling fees

Successful API operations that are asynchronously called to perform actions triggered by lifecycle rules are recorded in access logs. You are charged for only successful API operations. Failed operations are not recorded or charged. The following items describe the fees generated when API operations are called to convert the storage class of objects or delete objects and parts based on lifecycle rules:

• PUT request fees generated for converting the storage class of objects

  You are charged PUT request fees based on the storage class of objects before the storage class is converted. For example, when a Standard object is converted to an Infrequent Access (IA) object based on a lifecycle rule, you are charged for PUT requests based on the Standard storage class. The CommitTransition operation is called to convert the storage class of an object based on lifecycle rules. In this case, you are charged for PUT requests based on the number of storage class conversion tasks of objects.

  Important

  When an IA, Archive, or Cold Archive object is converted to a Deep Cold Archive object based on lifecycle rules, you are charged higher PUT request fees compared with the PUT request fees when a Standard object is converted to an IA, Archive, Cold Archive, or Deep Cold Archive object.

• PUT request fees generated for deleting objects

  You are charged PUT request fees based on the storage class of objects when the objects are deleted. The ExpireObject operation is called to delete an object based on lifecycle rules. In this case, you are charged for PUT requests based on the number of deleted objects.

  Important

  • In regions in the Chinese mainland, when an IA, Archive, or Cold Archive object is deleted based on lifecycle rules, you are charged higher PUT request fees compared with the PUT request fees when a Standard object is deleted. You are not charged PUT request fees when you use lifecycle rules to delete Deep Cold Archive objects.

  • In the China (Hong Kong) region and regions outside the Chinese mainland, you are not charged PUT request fees when you use lifecycle rules to delete objects of any storage class.

  For more information, see Regions and OSS endpoints in the public cloud.

• PUT request fees generated for deleting parts

  You are charged PUT request fees based on the storage class of parts when the parts are deleted. The AbortMultipartUpload operation is called to delete a part based on lifecycle rules. In this case, you are charged for PUT requests based on the number of deleted parts.

Important

• In regions in the Chinese mainland, when an IA, Archive, or Cold Archive part is deleted based on lifecycle rules, you are charged higher PUT request fees compared with the PUT request fees when a Standard part is deleted. You are not charged PUT request fees when you use lifecycle rules to delete Deep Cold Archive parts.

• In the China (Hong Kong) region and regions outside the Chinese mainland, you are not charged PUT request fees when you use lifecycle rules to delete parts of any storage class.

For more information, see API operation calling fees.

Storage costs

You are charged for the objects stored in Object Storage Service (OSS) based on the storage class, size, and storage duration.

IA, Archive, Cold Archive, and Deep Cold Archive objects have a minimum billable size. Objects that are smaller than 64 KB are charged for 64 KB. Objects that are greater than or equal to 64 KB are charged based on their actual sizes.

If you use lifecycle rules to delete an IA, Archive, Cold Archive, or Deep Cold Archive object within the minimum storage duration, you are charged for the storage usage of the object that is stored for less than the minimum storage duration.

For more information, see Storage fees.