Check Cloud Storage transitions before counting savings
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Verify the transition, retention dates, and minimum-duration exposure before approval. For lifecycle SetStorageClass transitions, count time in the original class toward the destination minimum, or objects may remain unchanged, deletion may be blocked, or an early-deletion charge may apply for the remaining duration.
What you need first
- Tool
- Use the read-only worksheet below, a review sheet rather than a command-line tool. Start with the linked Object Lifecycle Management guide and a bucket configuration and object metadata report from the storage owner.
- Access
- Ask an authorized Google Cloud storage colleague to provide read-only results for the bucket's lifecycle rules, Autoclass status, retention settings, affected objects' metadata, and class history.
- If you do not use that tool
- Send the storage owner the bucket name, proposed rule, affected object set, and planned deletion or replacement dates. Ask them to return the completed worksheet and mark missing history or unverified compatibility as unknown.
Why this is worth a look
Skipping this review can leave objects unchanged, block deletion or replacement, or create an early-deletion charge when objects leave a class before its applicable minimum duration. Cloud Storage does not validate transition correctness, retention can delay deletion, and Class A operation charges can outweigh lower storage costs for small objects.
Run this check
CHECKLISTComplete this worksheet without changing resources. Use the linked Google Cloud guides and read-only results supplied by an authorized storage colleague. Record compatibility, retention, and fee findings separately.
READ-ONLY REVIEW
Execution surface: a text document beside the linked Google Cloud guides and the storage owner's configuration and metadata report.
Access: request read-only results from an authorized storage colleague for the named bucket and affected objects. This worksheet grants no permissions.
Scope: one bucket, the proposed lifecycle rule, and its matched objects. Account for current and future objects covered by the rule.
Units: storage-class durations in days; retention dates as full timestamps with time zones. Bucket retention periods are measured in seconds; one day is 86,400 seconds. Record any early-deletion charge as duration-based exposure for the remaining minimum, without assigning a billing meter or proration.
Time window: original class entry through planned transition and deletion or replacement. Record dates rather than assuming immediate execution.
PLAN
Bucket: ____
Proposed lifecycle actions and conditions: ____
Affected object set: ____
Planned transition date: ____
Planned deletion or replacement date, or unknown: ____
TRANSITION
[ ] Record Autoclass enabled / disabled / unknown: ____
[ ] If enabled, review Autoclass treatment before using a manual lifecycle cost calculation. Record compatibility questions for the storage owner: ____
[ ] Record actual object storage classes, not just the bucket default: ____
[ ] Compare each proposed source-to-destination transition with the supported transitions in the Object Lifecycle Management guide.
Result: supported / unsupported / unknown: ____
RETENTION
[ ] Record each affected object's bucket retention expiration time, if applicable: ____
[ ] Record each affected object's retain-until time, if applicable: ____
[ ] Compare the planned deletion or replacement date with both timestamps. Both applicable retentions must be satisfied.
Blocked / retentions satisfied / unknown: ____
DURATION AND COST EXPOSURE
[ ] Record class-entry dates and whether changes used lifecycle SetStorageClass or a rewrite: ____
[ ] Record the applicable minimum storage duration from the linked guides, in days: ____
[ ] For a lifecycle SetStorageClass transition between classes with minimum storage durations, include time already spent in the original class when checking the destination minimum. Compare credited duration at planned deletion with that minimum.
Duration shortfall in days / none / unknown: ____
[ ] Review rewrites separately for retrieval and early-deletion charges. Do not reuse the lifecycle calculation.
[ ] Flag small-object transitions for Class A operation cost review.
[ ] For Autoclass, review its separate billing rules: management and enablement charges apply; retrieval and early-deletion fees are not charged except as part of enablement charges.
HANDOFF
Unsupported transition or unresolved compatibility: ____
Retention blocker and applicable timestamp: ____
Possible early-deletion charge or missing history: ____
Costs still needing review before approving savings: ____How to confirm it
- 01
Define the plan before requesting results
Name one bucket, the proposed rule, and planned deletion or replacement dates. Include current and future objects matched by the rule. Send that scope to the storage owner with the worksheet.
- 02
Confirm the transition can happen
Compare the proposed class change with the lifecycle guide's supported transitions. Do not treat an accepted configuration as proof. Ask the owner to resolve compatibility with Autoclass if it is enabled.
- 03
Keep retention separate from fees
Compare planned deletion or replacement with each object's applicable retention timestamps. Wait until both bucket and object retention are satisfied before treating the date as eligible under those controls. A minimum storage duration is a fee consideration, not a retention lock.
- 04
Review duration and remaining costs
Use the class history to assess a duration shortfall at planned deletion. For a lifecycle SetStorageClass transition between classes with minimum storage durations, count time in the original class toward the destination minimum. Keep rewrites and Autoclass in separate cost reviews, and request a Class A operation review for small-object transitions.
Before making changes
Leave savings unapproved if class history, the change method, or transition compatibility is unknown. This review assumes the affected objects and planned dates are known; it checks transition support, retention, and duration, not total cost or deletion authorization. A bucket default does not establish existing objects' classes. Autoclass uses separate storage and operation billing categories, with management and enablement charges, so manual-transition pricing does not apply unchanged.