Amazon Web Services → Microsoft Azure
Azure equivalent of Amazon Glacier (original vault service)
S3 storage classes map to Blob access tiers.
About Amazon Glacier (original vault service)
| Provider | Amazon Web Services |
|---|---|
| Status | maintenance Maintenance The standalone vault-based Glacier service (2012 REST API) no longer accepts new customers. Existing data stays accessible. AWS recommends the S3 Glacier storage classes instead. |
| What it is | Archive storage in vaults with its own API, separate from S3 and the S3 Glacier storage classes. |
| Documentation | docs.aws.amazon.com |
| Pricing | Official pricing page |
Azure mappings (1)
| Capability | Azure equivalent | Match |
|---|---|---|
| Object storage cost tiers (infrequent access and archive) | Blob Storage access tiers (hot, cool, cold, archive) | 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.