Review Cloud Storage transitions and retention blockers

Why this is worth a look

Cloud Storage objects added to a bucket inherit its default storage class unless another class is explicitly set. Object Lifecycle Management rules apply to current and future objects, and SetStorageClass changes an object's class when its conditions are met. Autoclass prohibits SetStorageClass and matchesStorageClass rules. Minimum storage durations are a deletion-fee consideration, while Bucket Lock and Object Retention Lock govern deletion or replacement. When both retention controls apply, both must be satisfied.

A read-only, documentation-led checklist for one bucket and a defined object set. It separates lifecycle-rule compatibility from deletion or replacement eligibility and fee exposure.

READ-ONLY REVIEW
Execution surface: Google Cloud documentation plus your approved read-only bucket and object metadata viewer.
Scope: one Cloud Storage bucket, its lifecycle configuration, and the defined objects in scope.
Required access: permission to read the bucket lifecycle and Autoclass configuration, retention settings, and the applicable object metadata. Confirm the exact permission names in your organization's approved access model.
Units and time window: storage durations and retention periods as documented by Google Cloud; use the object's applicable retention expiration or retain-until timestamp and the documented time spent in its storage class. Review the full period relevant to the proposed deletion or replacement.

1. Read the Storage classes and Object Lifecycle Management guides. Record the classes, minimum storage durations, proposed transition, SetStorageClass actions, and any matchesStorageClass conditions.
2. Check whether Autoclass is enabled. If it is enabled, reject SetStorageClass and matchesStorageClass lifecycle rules for this bucket. Also verify that the proposed transition is listed as supported by the lifecycle guide.
3. For the defined objects, use the approved read-only metadata viewer to record the storage-class history or other evidence available in your environment. Do not infer an existing object's class from the bucket default. Record retention expiration time for bucket retention, retain-until time for object retention, and whether both controls apply.
4. Review deletion or replacement separately from the class transition. Check whether retention has been satisfied. Then assess potential early-deletion fees using the documented minimum duration and the object's time spent in the relevant original storage class. Do not treat a possible fee as proof that the transition itself is blocked.

How to confirm it

1. 01

   Define the review scope

   Name one bucket, the proposed lifecycle change, and the affected object set. Use the full period relevant to any planned deletion or replacement, and keep transition compatibility separate from later cost or retention review.

2. 02

   Check lifecycle compatibility

   Read the lifecycle configuration and list SetStorageClass actions and matchesStorageClass conditions. Check Autoclass first. An Autoclass-enabled bucket cannot use either of those lifecycle elements, and the lifecycle guide says to verify that the proposed transition is listed.

3. 03

   Confirm storage-class evidence

   Use your approved read-only bucket and object metadata viewer to record the storage-class evidence available for each affected object. Do not infer an existing object's class from the bucket default. The supplied procedure intentionally does not prescribe an API field, command, or permission name.

4. 04

   Review retention controls

   Check the bucket retention policy and each object's retention configuration. Bucket Lock applies retention uniformly across the bucket, while Object Retention Lock applies per object. If both apply, deletion or replacement requires both retentions to be satisfied.

5. 05

   Assess deletion fee exposure

   For a planned deletion, compare the documented minimum storage duration with the object's documented time spent in the relevant original storage class. Early-deletion fees may apply when the duration has not ended. This is a fee assessment, not a claim that SetStorageClass is blocked.

Primary sources