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 expense 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, you’ll see how to set a variety of lifecycle rules for Google Cloud Storage buckets, both from the console and the command line, as well as see how to place an object on hold so it stays in place regardless of the rules.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Create and Populate the Storage Bucket
In Cloud Storage, create a bucket and add several files.
- Create Lifecycle Storage Rules via the Console
Using the console, create lifecycle rules.
- Update Lifecycle Rules via the CLI
From the GCP CLI, update the existing lifecycle rules using a JSON file.
- Place an Item on Hold
Place an event-based hold on one item in bucket.
