Best practices for using Deep Cold Archive

Use a lifecycle rule to transform an object's storage class to Deep Cold Archive

To avoid high fees for PUT requests, first upload objects to the Standard storage class. Then, use a lifecycle rule to transform them to the Deep Cold Archive storage class. Do not directly upload objects to the Deep Cold Archive storage class. When an object is transformed using a lifecycle rule, the PUT request is billed based on the source storage class. This means you are billed at the rate for the Standard storage class.

The following table shows the unit price per 10,000 PUT requests for different storage classes in the China (Hangzhou) region.

For more information about how to use lifecycle rules to transform an object's storage class, see Lifecycle.

Use a lifecycle rule to delete Deep Cold Archive objects

Manually deleting a Deep Cold Archive object calls the DeleteObject API. Each successful call to this API incurs a fee for one PUT-like request. To avoid these fees, you can configure a lifecycle rule to delete the objects automatically. Automatic deletion using a lifecycle rule calls the ExpireObject API, which does not incur fees for PUT-like requests.

For more information, see PUT-like API requests.

Meet the minimum storage duration requirement for objects

To avoid early deletion fees, ensure that when you transform an object to Deep Cold Archive, it meets the minimum storage duration requirements for both its source and new storage classes.

The following table lists the minimum storage duration for different storage classes.

For more information about fees for storage retained for less than the specified duration, see Storage fees.