Findings reference catalog for Storage Intelligence advisor

Indicates frequent operations on data in Coldline storage and Archive storage. For example, you might see this finding if an analytics job accesses monthly reports in Archive storage daily. This daily access results in a high operation rate for data better suited for Standard storage. To resolve this finding, move the data to a storage class suited for frequent access, or configure the analytics job to use cached data.

For more information, see Optimize usage for Coldline and Archive storage data.

Indicates that Cloud Storage is rate-limiting requests, which causes latency and timeouts. For example, you might see this finding if a batch processing job rapidly reads or writes many objects in the same bucket. This burst of requests exceeds per-bucket limits and triggers 429 Too Many Requests errors. To resolve this issue, implement exponential backoff in your application or scale up request throughput gradually.

For more information, see Improve performance by mitigating rate limited request errors.

Indicates an increase in data transfer between Cloud Storage buckets in one region and Compute Engine instances or other Google Cloud services in another region. This cross-region traffic can lead to unexpected egress costs. For example, you might see this finding if a Compute Engine instance in us-central1 frequently accesses a bucket in us-east1. To resolve this finding, colocate your compute and storage resources in the same region by using bucket relocation.

For more information, see Manage cross-region egress.

Indicates that storage consumption has increased beyond historical trends over the last 30 days. For example, you might see this finding if your bucket retains noncurrent object versions indefinitely after you upload new versions. Indefinite retention can lead to unnecessary storage costs. To resolve this finding, use Object Lifecycle Management to delete noncurrent versions or move them to colder storage, or enable Autoclass to automatically manage storage classes based on access patterns.

For more information, see Identify above trend storage consumption.

Indicates that a bucket with a default customer-managed encryption key (CMEK) contains objects that aren't encrypted with CMEK. For example, you might see this finding if you uploaded objects before setting the bucket's default Cloud Key Management Service (Cloud KMS) key. To resolve this finding, identify the non-compliant objects by using Storage Insights datasets and re-encrypt them with the bucket's default Cloud KMS key.

For more information, see Re-encrypt objects that violate default CMEK bucket policies.

Indicates that a bucket contains objects that use an encryption method restricted by the bucket's encryption enforcement configuration. For example, you might see this finding if you uploaded objects encrypted with standard encryption (Google default encryption, or GMEK) or customer-supplied encryption keys (CSEK) before restricting those methods on the bucket. To resolve this finding, identify the non-compliant objects by using Storage Insights datasets and re-encrypt them with an allowed encryption method.

For more information, see Re-encrypt objects that violate enforced encryption rules.