This topic describes how you are billed when you use lifecycle rules to transform the storage class of objects or to delete objects and parts.
Request fees for transformations or deletions (Required)
Operation | API operation | Billable item | Billing rule | Description |
Transform the storage class of an object | CommitTransition | Put requests | Request fees are calculated based on the number of successful requests. | Put request fees are charged based on the source storage class of the object. |
Delete an object | ExpireObject | Put request fees are charged based on the storage class of the object at the time of deletion. Note Put request fees for deleting a delete marker are charged based on the Standard storage class. | ||
Delete a part | AbortMultipartUpload | Put request fees are charged based on the storage class of the part at the time of deletion. |
The Put request fees to transform objects from Infrequent Access, Archive, or Cold Archive to other storage classes are higher than the fees to transform objects from the Standard storage class to Infrequent Access, Archive, Cold Archive, or Deep Cold Archive.
In regions in the Chinese mainland, the Put request fees for using lifecycle rules to delete Infrequent Access, Archive, or Cold Archive objects or parts are higher than the fees for deleting Standard objects or parts. No Put request fees are charged when you use lifecycle rules to delete Deep Cold Archive objects or parts.
In the China (Hong Kong) region and regions outside China, no Put request fees are charged for using lifecycle rules to delete objects or parts of any storage class.
For more information, see Request fees.
Fees for early deletion storage capacity (Conditional)
If a lifecycle policy transforms or deletes Infrequent Access, Archive, Cold Archive, or Deep Cold Archive objects before their minimum storage duration expires, you are charged for early deletion storage capacity.
Storage duration calculation method | Operation | Billable items | |
Billed storage capacity | Insufficient Capacity for the Specified Duration | ||
The minimum storage duration for the Infrequent Access storage class is 30 days. The duration is calculated from the Last-Modified time of the object in OSS. | A Standard object is stored for 10 days, transformed to an Infrequent Access object, stored for 5 days, and then deleted. |
| Early deletion fees for 15 days of Infrequent Access storage capacity |
The minimum storage duration for the Archive storage class is 60 days. The duration is calculated from the Last-Modified time of the object in OSS. | A Standard object is stored for 10 days, transformed to an Infrequent Access object, stored for 5 days, transformed to an Archive object, stored for 5 days, and then deleted. |
| Early deletion fees for 40 days of Archive storage capacity |
The minimum storage duration for the Cold Archive or Deep Cold Archive storage class is 180 days. The duration is calculated from the time the object is transformed to the Cold Archive or Deep Cold Archive storage class. | A Standard object is stored for 10 days, transformed to a Cold Archive object, stored for 1 day, and then deleted. |
| Early deletion fees for 179 days of Cold Archive storage capacity |
A Cold Archive object is stored for 10 days, transformed to a Deep Cold Archive object, stored for 1 day, and then deleted. |
|
| |
For more information, see Storage fees.
Data restoration fees (Conditional)
When you use a lifecycle rule to transition data to a colder storage class, you must consider both the storage duration and the data retrieval fees. Different fees apply when you read or restore objects from different storage classes.
Data retrieval fees are incurred when you directly read Infrequent Access objects.
Fees for real-time access of Archive objects are incurred when you directly read Archive objects.
Fees for Put requests and data retrieval capacity are incurred when you restore Archive objects.
Fees for retrieval requests, retrieval capacity, and temporary restoration capacity are incurred when you restore Cold Archive or Deep Cold Archive objects.
For Cold Archive and Deep Cold Archive objects, retrieval fees vary based on the retrieval priority. A higher priority incurs higher fees.
References
To avoid early deletion storage fees, understand how the minimum storage duration is calculated for objects in different storage classes. Ensure that the minimum storage duration is met before you transform or delete the objects. For more information, see How do I avoid fees for early deletion of objects?