Missing Autoclass on GCS Bucket

Enabling Autoclass allows GCS to automatically move objects to lower-cost tiers based on observed access behavior, optimizing storage costs without manual lifecycle policy management. Activating Autoclass reduces operational overhead while maintaining seamless access to objects across storage classes.

GCS charges for data stored based on the selected storage class. Standard, Nearline, and Coldline classes offer different pricing tiers optimized for access frequency. Without Autoclass, objects may remain in higher-cost tiers even when usage patterns change, leading to unnecessary storage expenses. Autoclass dynamically transitions objects between storage classes based on access frequency. It adds a per-object management fee and a one-time enablement charge (retrieval and early deletion fees are waived), objects smaller than 128 KiB always stay in Standard storage, and the default terminal class is Nearline unless the terminal class is set to Archive.

• Identify GCS buckets where Autoclass is not enabled
• Review object access patterns to confirm a mix of frequently and infrequently accessed data
• Assess current storage class distribution to identify potential inefficiencies
• Evaluate whether manual lifecycle management policies exist or are absent
• Validate that enabling Autoclass aligns with data retention and compliance requirements

Enable Autoclass on eligible GCS buckets to automate storage class transitions based on real-time access patterns. Remove any lifecycle rules that use the SetStorageClass action or the matchesStorageClass condition, which cannot be combined with Autoclass. Note that enabling Autoclass on an existing bucket moves all objects to Standard storage and incurs a one-time enablement charge; Autoclass can later be disabled, and objects then stay in their current storage class. Monitor storage cost trends after activation to verify expected savings and operational improvements.

• Autoclassdocs.cloud.google.com
• Storage pricingcloud.google.com