---
cuppy_hub: gcp
cuppy_path: changelog/2026-10-21-storage-family.md
cuppy_section: docs
cuppy_doc: 1EGP-F975
cuppy_doc_uuid: be3fa4de-7d39-4ddd-a916-337f5d9b5264
cuppy_permalink: https://cuppy.io/gcp/d/1EGP-F975
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/gcp/docs/changelog/2026-10-21-storage-family
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 19132f18306a24273d0e0fc75cebde98efebaa0949f7150657ced3869f318ea2
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---


# Storage family — first release

## Added

| Document | What it carries |
|---|---|
| `reference/storage/cloud-storage.md` | the five classes, their minimum durations, the four location types, and the bucket-default rule |
| `reference/storage/cloud-storage-access-control.md` | the five mechanisms, the uniform-access recommendation, and the 90-day one-way door |
| `reference/storage/persistent-disk-and-hyperdisk.md` | the three block families and the performance model that separates them |
| `reference/storage/filestore.md` | the current and legacy tiers, protocols, and the capacity floors |
| `reference/storage/errors.md` | the JSON API reason strings with cause, check and fix |
| `guides/storage/create-a-bucket-that-is-not-public.md` | six steps, ending in a verification that attempts what was forbidden |
| `guides/parity/storage.md` | S3 and Blob side by side, with the 365-against-180 archive row |

## The headline fact

**`ARCHIVE` commits 365 days of storage charges**, against 180 days for both AWS S3 Glacier Deep Archive and
the Azure archive tier. Every lifecycle rule carried in from either cloud needs re-tuning, and nothing warns
you — the charge simply appears.

## Absences recorded rather than filled in

1. The Compute Engine disks overview **does not address attaching a disk to multiple instances**.
2. The Filestore service-tiers page **says nothing about changing tier after creation**.
3. The Cloud Storage classes page **does not describe a rehydration step** for `ARCHIVE`, where both AWS and
   Azure document one for their deepest tiers. The parity guide records this as a difference *and* as an
   absence, because "no step is documented" is not the same claim as "no step exists".

## Known missing

- Object Lifecycle Management rule syntax in detail.
- Bucket retention policies, object holds and Object Versioning.
- Customer-managed encryption keys on buckets and disks (CMEK), beyond the KMS model in the identity family.
- Snapshots and machine images.
- Storage Transfer Service, which lives in the migration family instead.


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 91 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/gcp/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->