Microsoft Azure → Amazon Web Services
AWS equivalent of Blob Storage access tiers (hot, cool, cold, archive)
The closest AWS equivalents of Blob Storage access tiers (hot, cool, cold, archive) are Amazon S3 storage classes and Amazon Glacier (original vault service).
About Blob Storage access tiers (hot, cool, cold, archive)
| Provider | Microsoft Azure |
|---|---|
| Status | Generally available |
| What it is | Online hot, cool (30-day minimum), and cold (90-day minimum) tiers, plus the offline archive tier (180-day minimum, rehydration up to 15 hours). Tiers apply to block blobs; archive needs an LRS, GRS, or RA-GRS account. |
| Documentation | learn.microsoft.com |
| Pricing | Official pricing page |
AWS mappings (1)
| Capability | AWS equivalent | Match |
|---|---|---|
| Object storage cost tiers (infrequent access and archive) | Amazon S3 storage classes, Amazon Glacier (original vault service) Maintenance | Direct match |
Object tiers, lifecycle & protection(1)
Object storage cost tiers (infrequent access and archive) Direct match
S3 storage classes map to Blob access tiers. Standard-IA maps to cool (30-day minimum), Glacier Instant Retrieval maps to cold (90 days), and Glacier Flexible Retrieval and Deep Archive both map to archive (180 days, offline).
- Granularity. In S3 the storage class is set per object. On Azure the tier is set per block blob, with a default tier (hot, cool, cold, or smart) set on the account.
- Archive. Azure has one archive tier. Rehydration takes up to 15 hours and must go to an online tier before you can read. S3 has two archive classes, Glacier Flexible Retrieval (minutes to hours) and Deep Archive (within 12 hours for standard retrieval, lowest cost), and restores create a temporary copy.
- Redundancy limits. Blob archive isn't supported in ZRS, GZRS, or RA-GZRS accounts. S3 Glacier classes keep their multi-AZ design.