Cloud Storage Lifecycle Coldline Size Transition

What Object Lifecycle Management with Size Filtering Is

Object Lifecycle Management (OLM) in Google Cloud Storage automates object transition and deletion policies. The SetStorageClass lifecycle action alters the storage tier of an object asynchronously without rewriting data bytes or triggering data movement pipelines.

How It Meets the Requirements

• Regulatory Archival at 365 Days: Setting the age condition to 365 and matchesStorageClass to STANDARD ensures that only active objects that have resided in Standard storage for a full year transition to the COLDLINE tier.
• Preventing Inefficient Class A Operation Fees: Applying sizeAboveBytes: 5242880 (5 MiB) filters out small index files and thumbnails. Because executing SetStorageClass is billed as a Class A operation against the destination class, small objects can incur transition API charges that dwarf ongoing capacity savings.
• Avoiding Retrieval and Inter-Region Fees: Unlike manual copy or rewrite routines, Cloud Storage lifecycle transitions using SetStorageClass do not rewrite the underlying object data. Consequently, they incur zero retrieval fees and zero inter-region network charges.

Key Advantages

• Automated Policy Enforcement: Evaluates object metadata asynchronously without client-side compute overhead.
• Granular Filter Combinations: Combines age, matchesStorageClass, and sizeAboveBytes within a single rule condition block.
• Cumulative Duration Credit: Time spent in the original storage class counts toward the minimum retention duration of subsequent storage tiers.

Why This Is Optimal

This declarative lifecycle approach eliminates manual batch scripts, avoids unneeded operation expenses on small files, and safeguards against unexpected egress and retrieval billing.