LLMpediaThe first transparent, open encyclopedia generated by LLMs

Amazon Glacier

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Expansion Funnel Raw 53 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted53
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Amazon Glacier
NameAmazon Glacier
ProductCold storage service
DeveloperAmazon Web Services
Released2012
GenreCloud storage

Amazon Glacier is a cloud-based cold storage service designed for long-term archival and digital preservation of data. It provides durable, low-cost object storage tailored for infrequently accessed datasets and regulatory retention, integrating with a broader suite of Amazon Web Services offerings. Organizations in sectors such as banking, NASA, European Space Agency, and media production use Glacier-style archival workflows alongside compute and networking services.

Overview

Amazon Glacier delivers archival storage with an emphasis on durability and cost per gigabyte, positioned against services like Google Cloud Storage Nearline and Microsoft Azure Blob Storage cold tiers. The service exposes APIs compatible with Amazon S3 paradigms while offering distinct retrieval models and latency characteristics. Customers often pair Glacier with lifecycle policies from Amazon S3 to transition objects from active storage to archival tiers as part of data governance and retention strategies. Glacier’s model addresses compliance frameworks such as Sarbanes–Oxley Act and Health Insurance Portability and Accountability Act where long-term immutable retention and auditability are required.

History and development

Glacier was introduced in 2012 by Amazon Web Services as part of a continuing trend toward specialized cloud tiers that began with Amazon S3 in 2006. The offering evolved in response to market demand for lower-cost archival alternatives to primary object stores and tape libraries used by enterprises like The New York Times and research institutions such as CERN. Over subsequent years, AWS added features influenced by technologies from partners and standards bodies including the Internet Engineering Task Force and integrations with backup vendors such as Veeam and Commvault. Product iterations reflected enterprise workflows established in archival systems created by organizations like National Archives and Records Administration and broadcasters like BBC.

Service architecture and features

Glacier is built on AWS data center infrastructure spanning US East (N. Virginia), US West (Oregon), EU (Ireland), and other AWS regions, leveraging underlying storage and replication mechanics similar to those used by Amazon S3. Key features include data lifecycle policies, vaults and archives, multipart upload support, and vault lock for write-once-read-many (WORM) retention compatible with legal holds. Integration points exist with services such as AWS Lambda for event-driven workflows, AWS Identity and Access Management for access control, Amazon CloudWatch for monitoring, and AWS Key Management Service for server-side encryption. Glacier provides RESTful APIs and SDK support in languages used at companies like Netflix and Airbnb for programmatic management.

Pricing and data retrieval tiers

The pricing model separates storage costs, request costs, and retrieval costs, a structure resembling pricing strategies used by Google Cloud Platform and Microsoft Azure. Glacier introduced multiple retrieval tiers—expedited, standard, and bulk—each balancing latency and price similar to how FedEx offers express versus economy shipping. Customers charged for storage per gigabyte-month, and retrievals incur per-GB and per-request fees; data transfer between regions may involve additional charges comparable to inter-region networking billed by AWS. Cost optimization often involves lifecycle transitions from Amazon S3 to Glacier or use of inventory reports to minimize unpredictable retrieval expenses, a practice adopted by enterprises such as Adobe and Slack.

Security and compliance

Glacier supports encryption at rest using AWS Key Management Service and client-side encryption patterns employed by security teams at Goldman Sachs and JP Morgan Chase. Access control integrates with AWS Identity and Access Management policies and cross-account roles used by multi-tenant deployments at Salesforce. Immutable retention via vault lock enables compliance with regulations like SEC Rule 17a-4 and data sovereignty requirements observed by Deutsche Bank. Auditability and logging are supported through AWS CloudTrail and integration with third-party security information and event management systems adopted by firms such as Splunk.

Use cases and adoption

Common use cases include long-term backups for enterprises like SAP customers, media asset preservation used by studios such as Warner Bros., scientific data archiving at institutions including University of California, Berkeley, and compliance retention for financial services regulated by Financial Industry Regulatory Authority. Organizations implement Glacier in data protection strategies, digital preservation for libraries like the Library of Congress, and large-scale archive migration projects displaced from legacy tape systems from vendors like IBM and Dell EMC.

Limitations and criticisms

Criticisms focus on retrieval latency and cost predictability compared with hot storage, an issue noted in comparisons with Amazon S3 Glacier Deep Archive and alternatives from Backblaze and Wasabi Technologies. Users have highlighted complexity in lifecycle policy configuration, potential vendor lock-in when integrating with proprietary APIs, and challenges in e-discovery workflows under legal frameworks such as Federal Rules of Civil Procedure. Operational concerns include monitoring cold data and ensuring timely restores in disaster recovery plans used by enterprises like Capital One and Target. Additionally, data transfer costs and cross-region replication considerations raise architectural trade-offs for multinational organizations such as Siemens and Toyota.

Category:Amazon Web Services