Storage class

How it works

Hot tiers retrieve now. Archive tiers need a restore that can take minutes or hours. A transfer into an archive tier is a bad place for a file a client will download today. Lifecycle can move it after the delivery window.

A 40 GB master lands in standard storage, is downloaded twice, and transitions to archive after 30 days. A job that wrote it straight to archive made the client wait four hours on a restore.

How it differs

Storage class is not an archive file format. ZIP and tar are formats. The class is billing and latency.

Restore charges surprise people who thought the file was online.

Match class to the access pattern.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For storage class, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive storage class files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.