Amazon S3 Glacier

Name: Amazon S3 Glacier
Brand: Amazon Web Services (AWS)
Rating: 4.5 (197 reviews)

Leader

Official Global LinkedIn page for Amazon Web Services (AWS).

Est 2006|Valuation $2560B|2 Ref Customers

LinkedIn 10.9M|Website|Web traffic 1.1M|FTEs 148,001|HQ Seattle, Washington, US

MarketsCloud Infrastructure Providers (IaaS/PaaS)Backup and Data Protection

01Competitive Landscape

Narrative analysis

**Where S3 Glacier tends to be used effectively** - Integration with S3 features and AWS tooling (lifecycle policies, IAM, analytics, replication patterns). - Low advertised per-GB storage rates for Deep Archive on AWS product pages (region-dependent). **Where competitors can be preferable** - Predictability / simplicity: some non-hyperscaler providers emphasize fewer line-item fees and simpler forecasting, though they may not provide the same retrieval characteristics (vendor pricing pages). - Egress economics: providers such as Backblaze may offer different egress pricing models that are preferable depending on workload (vendor pricing pages). - Multi-cloud neutrality: teams avoiding single-vendor lock-in may prefer providers with consistent pricing across clouds or S3-compatible APIs. **Adoption trends / market presence** - Amazon S3 is a widely used object storage service; S3 Glacier classes are commonly used as part of S3 lifecycle management. - Presence on review sites indicates broad mindshare, though ratings can be biased toward users who had successful implementations.

	Amazon S3 Glacier (S3 storage classes)	Azure Blob Storage (Archive)	Google Cloud Storage (Archive)
Starting Price (indicative)	Published low per-GB rates for Deep Archive; region-dependent (see vendor pricing pages)	Varies by region and redundancy option; published pricing available from the vendor	Published low per-GB rates announced at launch; actual rates vary by region/model
Suitable for	S3-native archival with lifecycle policies, integration with AWS tooling	Azure-centric shops using Blob tiers and Azure governance	GCP-centric shops; simple class model with GCS tooling
Key Strength	Integration with S3 features and multiple retrieval options; low advertised deep archive storage price	Integration with Azure services and tiering model; governance controls	Competitive archival pricing; GCS class simplicity
Key Weakness	Retrieval/restore and egress economics can be a cost driver; naming confusion (legacy Glacier vs S3 classes)	Rehydration/transaction costs can increase overall cost; tiering complexity	Egress and retrieval charges still apply; fewer enterprise patterns vs AWS in some organizations

01Competitive Landscape

Narrative analysis

Where S3 Glacier tends to be used effectively

Integration with S3 features and AWS tooling (lifecycle policies, IAM, analytics, replication patterns).
Low advertised per-GB storage rates for Deep Archive on AWS product pages (region-dependent).

Where competitors can be preferable

Predictability / simplicity: some non-hyperscaler providers emphasize fewer line-item fees and simpler forecasting, though they may not provide the same retrieval characteristics (vendor pricing pages).
Egress economics: providers such as Backblaze may offer different egress pricing models that are preferable depending on workload (vendor pricing pages).
Multi-cloud neutrality: teams avoiding single-vendor lock-in may prefer providers with consistent pricing across clouds or S3-compatible APIs.

Adoption trends / market presence

Amazon S3 is a widely used object storage service; S3 Glacier classes are commonly used as part of S3 lifecycle management.
Presence on review sites indicates broad mindshare, though ratings can be biased toward users who had successful implementations.

	Amazon S3 Glacier (S3 storage classes)	Azure Blob Storage (Archive)	Google Cloud Storage (Archive)
Starting Price (indicative)	Published low per-GB rates for Deep Archive; region-dependent (see vendor pricing pages)	Varies by region and redundancy option; published pricing available from the vendor	Published low per-GB rates announced at launch; actual rates vary by region/model
Suitable for	S3-native archival with lifecycle policies, integration with AWS tooling	Azure-centric shops using Blob tiers and Azure governance	GCP-centric shops; simple class model with GCS tooling
Key Strength	Integration with S3 features and multiple retrieval options; low advertised deep archive storage price	Integration with Azure services and tiering model; governance controls	Competitive archival pricing; GCS class simplicity
Key Weakness	Retrieval/restore and egress economics can be a cost driver; naming confusion (legacy Glacier vs S3 classes)	Rehydration/transaction costs can increase overall cost; tiering complexity	Egress and retrieval charges still apply; fewer enterprise patterns vs AWS in some organizations