Store objects in three S3 storage classes and add a lifecycle configuration

Steps

1. Choose the bucket name. A bucket name must be unique across all of AWS, so it ends in your account ID. Replace 111122223333 with your own:

aws sts get-caller-identity --query Account --output text
BUCKET=clf-lab18-storage-111122223333
echo $BUCKET

2. Create the bucket in your CloudShell Region, then confirm that Block Public Access is on:

aws s3 mb s3://$BUCKET
aws s3api get-public-access-block --bucket $BUCKET

All four settings, BlockPublicAcls, IgnorePublicAcls, BlockPublicPolicy and RestrictPublicBuckets, read true. Leave them so. 3. Write three short text files of invented content, and upload each in a different storage class:

echo "INFO sample application log line for a lab" > app-1.txt
echo "Quarterly summary: invented sample text for a lab" > summary.txt
echo "Draft notes with no predictable access pattern" > notes.txt
aws s3 cp app-1.txt s3://$BUCKET/logs/app-1.txt
aws s3 cp summary.txt s3://$BUCKET/reports/summary.txt --storage-class STANDARD_IA
aws s3 cp notes.txt s3://$BUCKET/notes/notes.txt --storage-class INTELLIGENT_TIERING

The log file uses the default class, S3 Standard, for data read often. The summary goes to Standard-IA, for data read rarely but needed at once. The notes go to Intelligent-Tiering, for data whose access pattern nobody knows. 4. List the objects with their storage classes:

aws s3api list-objects-v2 --bucket $BUCKET --query 'Contents[].[Key,StorageClass]' --output table

Each key shows its class: STANDARD, STANDARD_IA and INTELLIGENT_TIERING. The logs/, reports/ and notes/ parts of the keys are prefixes, not real folders, and a lifecycle rule can target one. 5. Write a lifecycle configuration. The first rule applies only to the logs/ prefix: after 30 days it moves objects to Standard-IA, after 180 days to S3 Glacier Deep Archive, and after 365 days it deletes them. The second rule applies to the whole bucket and removes multipart uploads left unfinished for 7 days:

cat > lifecycle.json <<'EOF'
{
  "Rules": [
    {
      "ID": "clf-lab18-logs-rule",
      "Filter": {"Prefix": "logs/"},
      "Status": "Enabled",
      "Transitions": [
        {"Days": 30, "StorageClass": "STANDARD_IA"},
        {"Days": 180, "StorageClass": "DEEP_ARCHIVE"}
      ],
      "Expiration": {"Days": 365}
    },
    {
      "ID": "clf-lab18-abort-uploads",
      "Filter": {"Prefix": ""},
      "Status": "Enabled",
      "AbortIncompleteMultipartUpload": {"DaysAfterInitiation": 7}
    }
  ]
}
EOF
aws s3api put-bucket-lifecycle-configuration --bucket $BUCKET --lifecycle-configuration file://lifecycle.json

6. Read the rules back, and see them in the console:

aws s3api get-bucket-lifecycle-configuration --bucket $BUCKET --query 'Rules[].[ID,Status]' --output table

Then open the S3 console, choose your bucket, and open the Management tab. Lifecycle rules lists clf-lab18-logs-rule and clf-lab18-abort-uploads, and choosing the first draws its transitions as a timeline. Nothing moves today: the rules act on objects by age, and these objects are minutes old.