This document will guide you to create a storage policy, which can periodically convert the storage type of files or delete files to reduce storage costs.
Applicable Scenario
If you need to periodically convert files to STANDARD_IA, ARCHIVE, or DEEP_ARCHIVE storage classes, or directly delete files based on the file's modification time or prefix, you can create an appropriate storage policy to automatically execute the corresponding operations, thereby reducing storage costs.
Prerequisites
Create a Storage Policy
1. Log in to the VOD console, click Application Management on the left sidebar to enter the application list page. 2. Find the Pro edition application that needs to configure a storage policy, click the application name to enter the application storage page. Click Storage Policy to enter the storage policy page.
3. Click Create Storage Policy to enter the new policy creation page.
4. On the Create Storage Policy Configuration page, you can configure an appropriate policy based on your business needs:
Storage Policy Name: The length of the storage policy name shall not exceed 20 characters, and only Chinese characters, English letters, digits, spaces, _, -, and . are supported in seven formats.
Effective Scope: By default, it applies to all buckets. You can specify a bucket to take effect through the dropdown. If you choose to apply to all buckets, the storage policy will also take effect on newly added buckets.
Trigger Condition: Provides two trigger conditions of modification time and file prefix, where the modification time can be selected for up to 3650 days at most, and up to 20 file prefixes can be added.
Execute Action: The default is to switch to infrequent access storage. You can select to switch to archive storage, switch to deep archive storage, or delete a file through the dropdown.
5. After the policy details are configured, click Confirm to complete the creation of the storage policy. The storage policy will officially take effect at 0 o'clock the next morning.
Note:
The effective time is at 0 o'clock in the morning of the next day after the policy is enabled (i.e., the policy status is "enabled").