Bird
Raised Fist0
AWScloud~5 mins

S3 lifecycle rules in AWS - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
S3 lifecycle rules help you automatically manage your files in cloud storage. They save money by moving or deleting files you don't need often.
When you want to delete old backup files automatically after 30 days.
When you want to move photos to cheaper storage after 60 days.
When you want to keep only recent logs in fast storage and archive older ones.
When you want to save money by cleaning up unused files regularly.
When you want to automate file management without manual work.
Config File - lifecycle.json
lifecycle.json
{
  "Rules": [
    {
      "ID": "MoveToGlacierAfter30Days",
      "Status": "Enabled",
      "Filter": {},
      "Transitions": [
        {
          "Days": 30,
          "StorageClass": "GLACIER"
        }
      ],
      "NoncurrentVersionTransitions": [],
      "Expiration": {},
      "NoncurrentVersionExpiration": {}
    },
    {
      "ID": "DeleteAfter365Days",
      "Status": "Enabled",
      "Filter": {},
      "Expiration": {
        "Days": 365
      },
      "Transitions": [],
      "NoncurrentVersionTransitions": [],
      "NoncurrentVersionExpiration": {}
    }
  ]
}

This JSON file defines two lifecycle rules for an S3 bucket.

The first rule moves files to Glacier storage after 30 days to save cost.

The second rule deletes files after 365 days to clean up old data.

Both rules are enabled and apply to all files in the bucket.

Commands
This command applies the lifecycle rules from the JSON file to the S3 bucket named 'example-bucket'. It sets up automatic file management.
Terminal
aws s3api put-bucket-lifecycle-configuration --bucket example-bucket --lifecycle-configuration file://lifecycle.json
Expected OutputExpected
No output (command runs silently)
→
--bucket - Specifies the name of the S3 bucket to apply the rules to
→
--lifecycle-configuration - Points to the JSON file with lifecycle rules
This command retrieves and shows the current lifecycle rules set on the 'example-bucket' to verify the configuration.
Terminal
aws s3api get-bucket-lifecycle-configuration --bucket example-bucket
Expected OutputExpected
{ "Rules": [ { "ID": "MoveToGlacierAfter30Days", "Status": "Enabled", "Filter": {}, "Transitions": [ { "Days": 30, "StorageClass": "GLACIER" } ], "NoncurrentVersionTransitions": [], "Expiration": {}, "NoncurrentVersionExpiration": {} }, { "ID": "DeleteAfter365Days", "Status": "Enabled", "Filter": {}, "Expiration": { "Days": 365 }, "Transitions": [], "NoncurrentVersionTransitions": [], "NoncurrentVersionExpiration": {} } ] }
→
--bucket - Specifies the bucket to check lifecycle rules
Key Concept

If you remember nothing else from this pattern, remember: lifecycle rules automate moving or deleting files to save cost and keep storage tidy.

Common Mistakes
Not enabling the lifecycle rule by setting Status to 'Enabled'.
The rule will not work if it is disabled, so files won't move or delete automatically.
Always set "Status": "Enabled" in each lifecycle rule.
Using incorrect JSON syntax or missing required fields in the lifecycle configuration file.
AWS will reject the configuration and not apply the rules.
Validate JSON syntax and include all required keys like ID, Status, and either Transitions or Expiration.
Applying lifecycle rules to the wrong bucket name.
Rules won't affect the intended bucket, causing confusion and no cost savings.
Double-check the bucket name in the command matches the target bucket.
Summary
Create a JSON file defining lifecycle rules to move or delete files automatically.
Use 'aws s3api put-bucket-lifecycle-configuration' to apply the rules to your bucket.
Verify the rules with 'aws s3api get-bucket-lifecycle-configuration' to ensure they are set correctly.

Practice

(1/5)
1. What is the main purpose of an S3 lifecycle rule?
easy
A. To automatically move or delete files based on time to save costs
B. To manually upload files to S3 buckets
C. To create backups of files in S3
D. To encrypt files stored in S3

Solution

  1. Step 1: Understand lifecycle rule purpose

    S3 lifecycle rules automate management of files by moving or deleting them after a set time.

  2. Step 2: Compare options with lifecycle rule function

    Only To automatically move or delete files based on time to save costs describes automatic moving or deleting files to save costs, which matches lifecycle rules.

  3. Final Answer:

    To automatically move or delete files based on time to save costs -> Option A

  4. Quick Check:

    Lifecycle rules automate file management = C [OK]
Hint: Lifecycle rules automate file moves or deletes by time [OK]
Common Mistakes:
  • Confusing lifecycle rules with manual upload
  • Thinking lifecycle rules create backups
  • Assuming lifecycle rules encrypt files
2. Which of the following is the correct JSON snippet to define a lifecycle rule that deletes objects after 30 days?
easy
A. {"Rules": [{"Status": "Disabled", "Expiration": {"Days": 30}}]}
B. {"Rules": [{"Status": "Enabled", "Transition": {"Days": 30}}]}
C. {"Rules": [{"Status": "Enabled", "Expiration": {"Days": 30}}]}
D. {"Rules": [{"Status": "Enabled", "Expiration": {"Date": 30}}]}

Solution

  1. Step 1: Identify correct lifecycle rule syntax for expiration

    The expiration action uses "Expiration" with "Days" key and rule must be "Enabled".

  2. Step 2: Check each option for correct keys and values

    {"Rules": [{"Status": "Enabled", "Expiration": {"Days": 30}}]} uses "Expiration" with "Days":30 and "Status":"Enabled" which is correct. {"Rules": [{"Status": "Enabled", "Transition": {"Days": 30}}]} uses "Transition" which is for storage class change, not deletion. {"Rules": [{"Status": "Disabled", "Expiration": {"Days": 30}}]} disables the rule. {"Rules": [{"Status": "Enabled", "Expiration": {"Date": 30}}]} uses "Date" instead of "Days" which is invalid.

  3. Final Answer:

    {"Rules": [{"Status": "Enabled", "Expiration": {"Days": 30}}]} -> Option C

  4. Quick Check:

    Expiration with Days and Enabled status = A [OK]
Hint: Expiration uses "Days" and rule must be enabled [OK]
Common Mistakes:
  • Using Transition instead of Expiration for deletion
  • Setting rule status to Disabled
  • Using Date instead of Days for expiration
3. Given this lifecycle rule snippet, what happens to objects after 60 days?
{
  "Rules": [{
    "Status": "Enabled",
    "Prefix": "logs/",
    "Transition": {"Days": 60, "StorageClass": "GLACIER"}
  }]
}
medium
A. Objects in the 'logs/' folder are moved to Glacier storage after 60 days
B. Objects in the 'logs/' folder are deleted after 60 days
C. All objects in the bucket are moved to Glacier after 60 days
D. Objects in the 'logs/' folder are archived immediately

Solution

  1. Step 1: Understand the Transition action with Prefix

    The rule targets objects with prefix "logs/" and transitions them to Glacier after 60 days.

  2. Step 2: Analyze options against rule behavior

    Objects in the 'logs/' folder are moved to Glacier storage after 60 days correctly states objects in 'logs/' move to Glacier after 60 days. Objects in the 'logs/' folder are deleted after 60 days incorrectly says deletion. All objects in the bucket are moved to Glacier after 60 days incorrectly applies to all objects, not just prefix. Objects in the 'logs/' folder are archived immediately says immediate archive which is wrong.

  3. Final Answer:

    Objects in the 'logs/' folder are moved to Glacier storage after 60 days -> Option A

  4. Quick Check:

    Transition with prefix moves files after days = A [OK]
Hint: Transition moves files after days, prefix limits target [OK]
Common Mistakes:
  • Confusing Transition with Expiration (deletion)
  • Ignoring the prefix filter
  • Assuming all bucket objects are affected
4. You wrote this lifecycle rule but it does not delete files after 90 days:
{
  "Rules": [{
    "Status": "Enabled",
    "Expiration": {"Days": 90}
  }]
}
What is the likely problem?
medium
A. Missing a required rule ID
B. Status should be set to Disabled to activate
C. Expiration action cannot be used without Transition
D. Rule is missing a filter or prefix to target objects

Solution

  1. Step 1: Recall S3 lifecycle rule required fields

    Every lifecycle rule requires a unique "ID" field only if using AWS CLI or SDKs; however, in JSON configuration for S3 console, "ID" is optional. Filter or prefix is required to target objects; otherwise, the rule applies to all objects.

  2. Step 2: Analyze given rule

    The rule lacks a filter or prefix, so it applies to all objects. If files are not deleting, likely the rule is not targeting the intended objects. Missing "ID" is not always mandatory (A wrong). Status "Enabled" is correct (B wrong). Expiration works standalone (C wrong). Filter or prefix is needed to target specific objects (D correct).

  3. Final Answer:

    Rule is missing a filter or prefix to target objects -> Option D

  4. Quick Check:

    Missing filter or prefix means rule may not target intended objects = D [OK]
Hint: Filter or prefix is needed to target objects for deletion [OK]
Common Mistakes:
  • Believing filter or prefix is optional (A)
  • Thinking Expiration requires Transition (C)
  • Status should be Disabled to activate (B)
5. You want to save costs by moving files older than 30 days to STANDARD_IA storage and delete files older than 365 days, but only for files in the archive/ folder. Which lifecycle rule setup achieves this?
hard
A. { "Rules": [{ "Status": "Enabled", "Prefix": "archive/", "Transition": {"Days": 365, "StorageClass": "STANDARD_IA"}, "Expiration": {"Days": 30} }] }
B. { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}], "Expiration": {"Days": 365} }] }
C. { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transition": {"Days": 365, "StorageClass": "STANDARD_IA"}, "Expiration": {"Days": 30} }] }
D. { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transitions": [{"Days": 365, "StorageClass": "STANDARD_IA"}], "Expiration": {"Days": 30} }] }

Solution

  1. Step 1: Identify correct keys for multiple transitions and expiration

    Multiple transitions require "Transitions" array. Expiration is separate. Filter with Prefix targets 'archive/'.

  2. Step 2: Check each option for correct days and storage class order

    { "Rules": [{ "Status": "Enabled", "Prefix": "archive/", "Transition": {"Days": 365, "StorageClass": "STANDARD_IA"}, "Expiration": {"Days": 30} }] } reverses days and expiration. { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}], "Expiration": {"Days": 365} }] } correctly uses "Transitions" array with 30 days to STANDARD_IA and expiration at 365 days, with filter prefix. { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transition": {"Days": 365, "StorageClass": "STANDARD_IA"}, "Expiration": {"Days": 30} }] } uses singular "Transition" but reverses days (365 to IA, expire 30). { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transitions": [{"Days": 365, "StorageClass": "STANDARD_IA"}], "Expiration": {"Days": 30} }] } reverses days and expiration.

  3. Step 3: Choose best practice with multiple transitions

    { "Rules": [{ "Status": "Enabled", "Filter": {"Prefix": "archive/"}, "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}], "Expiration": {"Days": 365} }] } uses "Transitions" array which is best practice for multiple transitions, even if only one here, and matches requirements.

  4. Final Answer:

    Rule with Filter prefix 'archive/', Transitions at 30 days to STANDARD_IA, Expiration at 365 days -> Option B

  5. Quick Check:

    Multiple transitions use "Transitions" array, filter prefix set = B [OK]
Hint: Use "Transitions" array for multiple moves, filter prefix to target folder [OK]
Common Mistakes:
  • Confusing Transition singular vs Transitions array
  • Mixing up days for transition and expiration
  • Not using filter or prefix to limit scope