Object Lifecycle

As your data storage needs evolve, you may want to optimize costs by moving less frequently accessed objects to more cost-effective storage tiers. Tigris provides an object lifecycle rule to automatically move objects between storage tiers. For example, you might want to move older log files or archived data to a lower-cost storage tier while keeping frequently accessed data in the standard tier. This helps to maintain optimal performance for active data while reducing storage costs for infrequently accessed objects.

Configuring an Object Lifecycle rule

With Object Lifecycle rules, you can configure when and how your objects transition between storage tiers. This is done at the bucket level and applies to all objects within that bucket.

The transition timing can be set in two ways:

• Days: The objects will be transitioned after the specified number of days.
• Date: The objects will be transitioned on the specified date.

Tigris currently supports transitioning an object from STANDARD to one of these three storage tiers:

1. STANDARD_IA: Infrequent Access storage is designed for data that is accessed less frequently, but requires rapid access when needed. This tier offers lower storage costs compared to standard storage while maintaining high durability and availability. Ideal for backup data, older logs, or infrequently accessed files.

2. GLACIER: Glacier storage is designed for long-term archival data that is rarely accessed. This tier provides the lowest storage costs but has higher retrieval times. Perfect for data that you need to retain for compliance or archival purposes but rarely need to access, such as old backups, historical records, or completed projects.

3. GLACIER_IA: Glacier Infrequent Access storage is designed for data that requires immediate access but is accessed very infrequently. This tier offers a balance between cost and retrieval time - it's more expensive than GLACIER but provides faster access times. Ideal for data that needs to be available quickly when requested, such as monthly reports, quarterly analytics, or seasonal data that might be needed on short notice.

Specifying an Object Lifecycle rule via the Tigris Dashboard

You can specify lifecycle transition rules for your bucket using the Tigris Dashboard.

Here's a short video that demonstrates how to specify Object Lifecycle rule for a bucket:

Specifying an Object Lifecycle rule via the AWS CLI

You can configure an Object Lifecycle rule for objects in the bucket using AWS the CLI. Below are some examples of how you can configure the lifecycle transition rules.

Transition objects after 30 days

Here's an example of an Object Lifecycle configuration that transitions objects after 30 days.

Create a JSON file named lifecycle.json with the following content:

{
  "Rules": [
    {
      "Status": "Enabled",
      "Transitions": [
        {
          "Days": 30,
          "StorageClass": "STANDARD_IA"
        }
      ]
    }
  ]
}

Then, run the following command to apply the lifecycle configuration to the bucket:

aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-configuration file://lifecycle.json

Transition objects at the end of the year 2024

Here's an example of an Object lifecycle configuration that transitions objects at the end of the year 2024.

Create a JSON file named lifecycle.json with the following content:

{
  "Rules": [
    {
      "Status": "Enabled",
      "Transitions": [
        {
          "Date": "2024-12-31T00:00:00Z",
          "StorageClass": "GLACIER"
        }
      ]
    }
  ]
}

Then, run the following command to apply the lifecycle configuration to the bucket:

aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-configuration file://lifecycle.json

Things to note

• Tigris always rounds the transition time to UTC midnight for the scheduled date.
• Only one Object Lifecycle rule can be applied to a bucket at a time.
• When using the AWS CLI to apply an Object Lifecycle configuration, the JSON can only contain the fields shown in the examples above.