Lifecycle management rules in GCP - Commands & Configuration

Introduction

Lifecycle management rules help you automatically manage files in cloud storage. They let you set simple rules to delete or move files after a certain time, saving space and costs without manual work.

When you want to automatically delete old backup files after 30 days to save storage costs.

When you want to move files to cheaper storage after they haven't been accessed for 60 days.

When you want to keep only the latest versions of files and delete older ones automatically.

When you want to archive logs that are older than 90 days to a cold storage class.

When you want to clean up temporary files that are no longer needed after a few days.

Config File - lifecycle.json

lifecycle.json

{
  "rule": [
    {
      "action": {"type": "Delete"},
      "condition": {"age": 30}
    },
    {
      "action": {"type": "SetStorageClass", "storageClass": "NEARLINE"},
      "condition": {"age": 60}
    }
  ]
}

This JSON file defines lifecycle rules for a Google Cloud Storage bucket.

rule: A list of rules to apply.

action: What to do with the files. Here, delete files older than 30 days, and move files older than 60 days to NEARLINE storage.

condition: When to apply the action, based on file age in days.

Commands

This command applies the lifecycle rules defined in lifecycle.json to the bucket named example-bucket. It tells Google Cloud Storage to start managing files automatically based on these rules.

Terminal

gsutil lifecycle set lifecycle.json gs://example-bucket

Expected Output

Setting lifecycle configuration on gs://example-bucket/...

This command retrieves and shows the current lifecycle rules set on the example-bucket. It helps verify that the rules were applied correctly.

Terminal

gsutil lifecycle get gs://example-bucket

Expected Output

{

  "rule": [

    {

      "action": {"type": "Delete"},

      "condition": {"age": 30}

    },

    {

      "action": {"type": "SetStorageClass", "storageClass": "NEARLINE"},

      "condition": {"age": 60}

    }

  ]

}

Key Concept

If you remember nothing else from this pattern, remember: lifecycle rules automate file cleanup and storage class changes based on file age to save costs and effort.

Common Mistakes

Not applying the lifecycle rules to the correct bucket name.

The rules won't affect the intended storage bucket, so files won't be managed automatically.

Double-check the bucket name in the gsutil lifecycle set command matches your target bucket.

Using incorrect JSON syntax in the lifecycle configuration file.

The gsutil command will fail to apply the rules because the file is invalid.

Validate the JSON file syntax before applying, ensuring proper brackets, commas, and quotes.

Expecting immediate deletion or storage class change after applying rules.

Lifecycle actions run asynchronously and may take some time to process files.

Wait some time after applying rules and check file status later to see changes.

Summary

Create a JSON file defining lifecycle rules with actions and conditions.

Use gsutil lifecycle set to apply these rules to your storage bucket.

Verify the rules with gsutil lifecycle get to ensure they are set correctly.

Practice

1. What is the main purpose of lifecycle management rules in Google Cloud Storage?

easy

A. To encrypt files before uploading

B. To manually upload files to the cloud storage

C. To create backups of files every hour

D. To automatically delete or move files based on conditions like age or storage class

Solution

1. Step 1: Understand lifecycle rules function

   Lifecycle rules automate file management by applying actions like deletion or moving files based on set conditions.

2. Step 2: Compare options with lifecycle purpose

   Only To automatically delete or move files based on conditions like age or storage class describes automatic file management based on age or storage class, which matches lifecycle rules.

3. Final Answer:

   To automatically delete or move files based on conditions like age or storage class -> Option D

4. Quick Check:

   Lifecycle rules automate file management = A [OK]

Hint: Lifecycle rules automate file cleanup and movement [OK]

Common Mistakes:

• Confusing lifecycle rules with manual file upload
• Thinking lifecycle rules create backups
• Assuming lifecycle rules handle encryption

2. Which of the following is the correct syntax snippet to define a lifecycle rule that deletes objects older than 30 days in a GCP bucket JSON configuration?

easy

A. {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]}

B. {"rule": [{"action": {"type": "Remove"}, "condition": {"age": 30}}]}

C. {"rule": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]}

D. {"rule": [{"action": {"type": "Delete"}, "condition": {"days": 30}}]}

Solution

1. Step 1: Identify correct key names in lifecycle JSON

   The lifecycle configuration uses the key "rules" (plural) for the list of rules, not "rule".

2. Step 2: Check action type and condition keys

   Action type must be "Delete" and condition uses "age" in days. {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]} correctly uses "rules", "Delete", and "age".

3. Final Answer:

   {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]} -> Option A

4. Quick Check:

   Correct lifecycle JSON uses "rules" and "age" = C [OK]

Hint: Use "rules" key and "age" condition for lifecycle JSON [OK]

Common Mistakes:

• Using singular "rule" instead of "rules"
• Using "Remove" instead of "Delete" for action
• Using "days" instead of "age" in condition

3. Given this lifecycle rule JSON snippet for a GCP bucket:

{"rules": [{"action": {"type": "SetStorageClass", "storageClass": "NEARLINE"}, "condition": {"age": 60}}]}

What happens to objects older than 60 days?

medium

A. They remain in the current storage class

B. They are deleted immediately

C. They are moved to the NEARLINE storage class

D. They are archived to Coldline storage

Solution

1. Step 1: Understand action type in lifecycle rule

   The action type "SetStorageClass" changes the storage class of objects matching the condition.

2. Step 2: Analyze condition and effect

   The condition "age": 60 means objects older than 60 days will be moved to the "NEARLINE" storage class.

3. Final Answer:

   They are moved to the NEARLINE storage class -> Option C

4. Quick Check:

   SetStorageClass action moves objects = A [OK]

Hint: SetStorageClass moves files; Delete removes them [OK]

Common Mistakes:

• Confusing SetStorageClass with Delete action
• Assuming objects are deleted instead of moved
• Thinking NEARLINE means Coldline storage

4. You wrote this lifecycle rule JSON to delete objects older than 90 days:

{"rule": [{"action": {"type": "Delete"}, "condition": {"age": 90}}]}

Why does this rule not work as expected?

medium

A. The key should be "rules" not "rule"

B. The action type "Delete" is invalid

C. The condition "age" must be a string, not a number

D. The age value must be less than 30

Solution

1. Step 1: Check lifecycle JSON key names

   The lifecycle configuration requires the key "rules" (plural) for the list of rules, not "rule".

2. Step 2: Validate action and condition correctness

   "Delete" is a valid action type, and "age" is correctly a number. Age can be any positive number.

3. Final Answer:

   The key should be "rules" not "rule" -> Option A

4. Quick Check:

   Correct key is "rules" = B [OK]

Hint: Use "rules" key for lifecycle rules array [OK]

Common Mistakes:

• Using singular "rule" instead of "rules"
• Thinking "Delete" is invalid action
• Believing age must be string or less than 30

5. You want to create a lifecycle rule that moves objects to Coldline storage after 30 days and deletes them after 365 days. Which JSON configuration correctly implements this?

hard

A. {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 365}}, {"action": {"type": "Delete"}, "condition": {"age": 30}}]}

B. {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]}

C. {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "NEARLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]}

D. {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}, {"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 365}}]}

Solution

1. Step 1: Identify correct order of lifecycle actions

   Objects should first move to Coldline after 30 days, then be deleted after 365 days. The order matters for correct lifecycle behavior.

2. Step 2: Check storage class and age conditions

   {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]} correctly sets "SetStorageClass" to "COLDLINE" at age 30, then "Delete" at age 365.

3. Final Answer:

   {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]} -> Option B

4. Quick Check:

   Move to Coldline at 30 days, delete at 365 days = D [OK]

Hint: Order rules: move storage first, then delete later [OK]

Common Mistakes:

• Reversing delete and move actions order
• Using wrong storage class name
• Setting wrong age values for actions