Bucket Lifecycle
Overview
Lifecycle on vStorage is a feature that helps you manage the lifecycle of objects in your bucket, thereby optimizing storage costs. With Lifecycle, you can configure rules in 2 types:
Transition rule: Rules support moving objects between storage classes. You can set up one or more lifecycle rules to move objects if the object has not changed for N days.
Expiration rule: Rules support deleting objects based on constraints. You can set up one or more lifecycle rules to delete objects after a certain period of time since the object exists on the vStorage system.
Refer to the table below to understand how each storage class works:
Designed for
For frequently accessed data that requires low latency and high throughput with retrieval in milliseconds (10m object/ 1H).
For long-term storing data with retrieval in miliseconds (5m object/ 1H).
For long-term data archiving that is accessed once or twice in a year with retrieval within hour (5m object/ 12H and 10m object/ 24H).
Durability
99.999999999%
99.999999999%
99.999999999%
Availability
99.99%
99.99%
99.99%
Min storage quota
No
No
5 TB
Min storage duration
No
No
90 days
Min billable object size
0
0
128 KB
Free traffic
Quota x 10
Quota x 2
Quota x1
Free request
Free request on Gold Class performance
Free request on Instant Archive Class performance
Free request on Archive Class performance
With Transition rule
Follow the instructions below to set up a transition rule:
1. Log in to https://vstorage.console.vngcloud.vn, then select Region HCM04
2. Select the project containing the bucket you want to set up the lifecycle for. For example, I have a bucket demo-project that has been initialized to create Storage Class Gold as shown below.
3. Select the Action icon and select Configure Lifecycle.
4. The Lifecycle screen is displayed. Select Create a lifecycle rule.
5. Enter a Rule name . The Rule names we allow you to enter include letters (az, AZ, 0-9, '_', '-', space). The length of your Rule name must be between 5 and 50.
6. Select Rule type: Transition
7. Enter Filter. This filter is applied to a specific lifecycle rule. If you want to apply the lifecycle rule you are creating to all objects in this bucket, leave this field blank. Or you can filter the objects you want to apply the lifecycle rule to through the prefix.
8. Select the action that happens to the object in the bucket you choose, including:
Transition current version of objects:
When enabled, this rule automatically moves the current version of an object from the current storage class to an selected lower storage class a certain period of time.
You can enter a number of days in the "After ___ days from object creation" section to define the number of days from object creation that the current version will be moved.
Transition noncurrent version of objects:
This rule applies to noncurrent versions of objects if you have Versioning enabled.
You can configure to move old versions after a number of days since they become noncurrent version, by filling in "After ___ days become noncurrent version".
With Expiration rule
Expiration rule is a set of rules that automatically delete objects when they expire. Follow the instructions below to set up a expiration rule:
1. Log in to https://vstorage.console.vngcloud.vn.
2. Select the project containing the bucket you want to set up the lifecycle for.
3. Select the Action icon and select Configure Lifecycle.
4. The Lifecycle screen is displayed. Select Create a lifecycle rule.
5. Enter a Rule name . The Rule names we allow you to enter include letters (az, AZ, 0-9, '_', '-', space). The length of your Rule name must be between 5 and 50.
6. Select Rule type: Expiration
7. Enter Filter. This filter is applied to a specific lifecycle rule. If you want to apply the lifecycle rule you are creating to all objects in this bucket, leave this field blank. Or you can filter the objects you want to apply the lifecycle rule to through the prefix.
8. Select the action that happens to the object in the bucket you choose, including:
Expire current version of objects :
When enabled, this rule will automatically delete the current version of the object after a certain period of time.
You can enter a number of days in the "After ___ days from object creation" section to define the number of days from object creation that the current version will expire and be deleted.
Permanently delete noncurrent versions :
This rule applies to noncurrent versions of objects if you have Versioning enabled.
You can configure to delete old versions after a number of days since they become noncurrent version, by filling in "After ___ days become noncurrent version".
Delete incomplete multipart uploads :
When you upload a large object using a multipart upload, but the upload does not complete, the uploaded parts are retained in S3.
This rule allows to automatically delete parts of multipart uploads that are not completed after a period of time since the upload was started.
You can enter a number of days in the "After ___ days from object creation" section to specify the period of time before incomplete parts of a multipart upload are deleted.
Delete expired object delete marker :
This rule only applies if you have Versioning enabled and have object delete markers in the bucket.
When enabled, it will remove expired delete markers , improving performance by cleaning up markers that are no longer needed. (This option can usually only be enabled when there are expired delete markers in the bucket.)
Last updated