INTELLIGENT TIERING is a COS storage class designed to reduce storage costs by automatically moving objects between two storage tiers (frequent access and infrequent access) when access patterns change.
INTELLIGENT TIERING is ideal for data with unknown or changing access patterns. It offers the same low latency and high throughput as STANDARD while featuring lower costs. Users can change the storage class of objects with uncertain access patterns from STANDARD to INTELLIGENT TIERING as needed to reduce in-cloud storage costs.
- Currently, INTELLIGENT TIERING is only available for the Beijing, Shanghai, Guangzhou, Chongqing, Tokyo, and Singapore regions.
- INTELLIGENT TIERING is a standalone storage class that will incur storage usage fees. For detailed pricing, see Product Pricing.
The access patterns of data stored in INTELLIGENT TIERING will be monitored. COS moves objects that have not been accessed for a continuous period to the lower-cost infrequent access tier. If an object in the infrequent access tier is accessed later, it is automatically moved back to the frequent access tier to ensure the data retrieval performance. INTELLIGENT TIERING manages to strike a balance between storage costs and read/write performance and features the following strengths:
To store your object in the COS INTELLIGENT TIERING storage class, enable INTELLIGENT TIERING for the bucket, and then specify the storage class of your object as INTELLIGENT TIERING.
You can perform the following steps to store your object in the INTELLIGENT TIERING storage class:
Once INTELLIGENT TIERING is enabled for a bucket, it cannot be disabled.
You can perform the following steps to move in-cloud objects to the INTELLIGENT TIERING storage class:
You can use the following APIs to configure INTELLIGENT TIERING:
Currently, all SDKs that COS releases support INTELLIGENT TIERING. To support INTELLIGENT TIERING, you can set
INTELLIGENT_TIERING when uploading a file. For more information, see SDK Overview.
INTELLIGENT TIERING has the following limits:
INTELLIGENT TIERING fees include INTELLIGENT TIERING storage usage fees and INTELLIGENT TIERING object monitoring fees.
Assume that an organization has 1 TB objects, 100,000 objects in total (10 MB per object), and the data is stored in the INTELLIGENT TIERING storage class in the Beijing region. If 20% of the objects (i.e., 20,000 objects) transition to the infrequent access tier every month, the object monitoring fees and storage usage fees for each month will be as follows:
|Month||Object Monitoring Fees (USD)||INTELLIGENT TIERING Storage Usage Fees (USD)||STANDARD Storage Usage Fees (USD)|
|1||0.25||1024 x 0.024 = 24.58||1024 x 0.024 = 24.58|
|2||0.25||819.2 x 0.024 + 204.8 x 0.018 = 23.35||1024 x 0.024 = 24.58|
|3||0.25||655.36 x 0.024 + 368.64 x 0.018 = 22.36||1024 x 0.024 = 24.58|
|4||0.25||524.288 x 0.024 + 499.712 x 0.018 = 21.58||1024 x 0.024 = 24.58|
|5||0.25||419.4304 x 0.024 + 604.5696 x 0.018 = 20.95||1024 x 0.024 = 24.58|
|6||0.25||335.54432 x 0.024 + 688.45568 x 0.018 = 20.45||1024 x 0.024 = 24.58|
As you can see, using INTELLIGENT TIERING reduces storage costs over time. Only a small amount of monitoring cost is required each month.
INTELLIGENT TIERING is suitable for large objects (such as audio and video, logs, etc.) whose access patterns change. Larger average object sizes mean you pay less for monitoring per GB objects. If your business has relatively fixed data access patterns, you can set lifecycle configuration to specify the time to transition objects to STANDARD_IA without the need to use INTELLIGENT TIERING.
You can store objects in INTELLIGENT TIERING as follows:
COPYAPI. You can also use the lifecycle feature to transition STANDARD or STANDARD_IA objects to INTELLIGENT TIERING.
INTELLIGENT TIERING has a minimum storage object size of 64 KB. Therefore, objects smaller than 64 KB will always be stored in STANDARD. For objects smaller than 64 KB, we recommend you upload them to the STANDARD, STANDARD_IA, ARCHIVE, or DEEP ARCHIVE storage class as needed to reduce costs.
INTELLIGENT TIERING configuration can't be disabled once enabled. If you don't need to store your objects in INTELLIGENT TIERING, you just need to specify the storage class as a non-INTELLIGENT TIERING class such as STANDARD, STANDARD_IA, ARCHIVE, or DEEP ARCHIVE when uploading the objects.