While saving an object in a Cloud Storage bucket is relatively inexpensive, there is, nonetheless, a cost. The cost varies depending on the storage class selected. Certain objects are required to be more available at first, requiring the storage class with the highest availability and cost. Such objects may eventually be relegated to less available and less expensive storage classes and, even, be deleted. Management of these objects over time can be handled automatically by establishing and implementing lifecycle rules. In this hands-on lab, we’ll set a variety of lifecycle rules for Google Cloud Storage buckets both from the console and the command line.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Create a Cloud Storage Bucket
- From the Google Cloud console, navigate to Cloud Storage > Browser.
- Click CREATE BUCKET.
- Under Name your bucket, enter a globally unique name.
- Click Create.
- Define the First Lifecycle Rule
- Under Bucket details, select LIFECYCLE.
- In Rules, click Add a rule.
- Under Select an action, select Set storage class to Nearline.
- Click Continue.
- Under Select object conditions, select Age and enter 180.
- Click Continue.
- Click Create.
- Define the Second Lifecycle Rule
- In Rules, click Add a rule.
- Under Select an action, select Set storage class to Coldline.
- Click Continue.
- Under Select object conditions, select Age and enter 365.
- Click Continue.
- Click Create.
- Get Lifecycle Rules from the Command Line
At the top menu, click the Cloud Shell icon (>_) to activate Cloud Shell.
In the Cloud Shell, enter the following code:
gsutil lifecycle get gs://<BUCKETNAME>Review output.
- Set the Lifecycle Rule with the JSON File
Clone a repo and change to the lab’s directory:
git clone https://github.com/linuxacademy/content-gc-essentials cd content-gc-essentials/cloud-storage-lifecycle-labReview the file in Cloud Editor.
In Cloud Shell, enter the following code:
gsutil lifecycle set delete-after-two-years.json gs://<BUCKET_NAME>Confirm the lifecycle rule has been added in the console.
