Amazon S3 Glacier

Amazon S3 Glacier is a managed archival storage service for long-term, infrequently accessed data using vaults and archives. It provides API-based storage with configurable retrieval tiers to trade retrieval latency against cost. It typically sits as a cold- or archive-tier in an AWS storage architecture, receiving data via lifecycle transitions, backups, or direct archive APIs.

🗂 Resource Category

Storage

🧠 Exam Memory Hook

Think: "Long-term retention + infrequent access + lifecycle transition = Amazon S3 Glacier"

📖 Ownership

Classification: AWS Managed Service

AWS responsibilities: AWS operates and maintains the underlying storage infrastructure, network, service control plane, APIs, and the managed service platform that implements vaults and archives. AWS is responsible for physical security and patching of the physical infrastructure and managed service runtime that delivers the Glacier APIs. AWS manages durability mechanisms and service-side replication according to the service implementation.

Customer responsibilities: The customer configures access control (IAM policies and resource-based policies), lifecycle rules that transition data into Glacier, archive and retrieval requests, retention policies, monitoring and logging, encryption key choice and management when using customer-managed KMS keys, and the content and lifecycle of stored archives. The customer is also responsible for ensuring compliance controls, data classification, and any application-level encryption or data-format compatibility.

Patching responsibilities: AWS patches and maintains the physical infrastructure and the managed service platform that provides the Glacier APIs. There is no guest operating system or customer-managed runtime inside the Glacier service to patch; the customer patches their own applications, SDKs, and any servers or client systems that call Glacier, and manages libraries, dependencies, and application code.

🏗 Typical Architecture

💡 Top 5 Features

Long-term archival storage model using vaults and archives for infrequently accessed data.
Multiple retrieval tiers to allow trade-offs between retrieval latency and cost.
Integration points for lifecycle transitions from Amazon S3 and for backups from AWS Backup.
Vault Lock support for write-once-read-many (WORM) style retention controls to help meet compliance requirements.
Server-side encryption support and integration with AWS Key Management Service for customer-managed keys.

✅ Top 5 Use Cases

Regulatory retention of records where data must be preserved for many years and is infrequently accessed, with controlled retrieval processes.
Long-term retention of backup snapshots created by backup workflows to reduce primary storage costs while retaining recoverability.
Archiving large media assets (raw video, film scans) after production to free primary storage while preserving original assets.
Storing scientific or research datasets that must be retained for audits or reanalysis but are seldom accessed.
Keeping historical logs and transaction archives for investigations or compliance queries with lifecycle-managed transitions from S3.

🏗 Architecture Placement

Amazon S3 Glacier acts as a cold or archive tier within a regional AWS storage architecture; data is typically sent to Glacier via S3 lifecycle transitions, backup services, or direct Glacier API calls. Applications, backup systems, or lifecycle policies initiate archive or retrieval operations, and IAM and KMS are used to control access and encryption. Glacier is a regional service and stores data within the configured AWS region.

🎯 Commonly Used With

- Amazon S3
- AWS Identity and Access Management
- AWS Key Management Service
- Amazon CloudWatch
- AWS Backup

🌍 5 Real-World Examples

A bank moves aged transaction records to Glacier via S3 lifecycle policies to retain them for regulatory audits while reducing primary storage footprint.
A media company transitions completed raw footage to Glacier for long-term retention after post-production to keep source assets available for future use.
A healthcare provider archives medical imaging studies to Glacier to meet retention requirements while keeping frequently accessed recent studies in faster storage.
A research institution stores large experimental datasets in Glacier after initial analysis to preserve them for reproducibility and future verification.
A government records office places historical documents into Glacier using lifecycle and Vault Lock controls to satisfy retention and tamper-evidence requirements.

🎓 AWS Exam Clues

Use Glacier when requirements specify long-term retention and infrequent access with acceptance of retrieval latency.
Look for lifecycle transition rules from Amazon S3 as an architectural indicator to use Glacier for archival storage.
Vault Lock and retention policies are clues when an exam scenario requires immutable or WORM-style archives for compliance.
If the requirement emphasizes rapid frequent access or low-latency reads, Glacier is usually not the correct storage tier.
Integration with backup workflows (AWS Backup or custom backup tools) and mention of retention windows often points to Glacier for archival retention.

📝 Quick Revision

Amazon S3 Glacier provides managed archival storage for long-term, infrequently accessed data with configurable retrieval tiers and compliance controls. Use it when retention and low-cost cold storage are required, and consider retrieval latency, lifecycle automation, and key management when designing production solutions.

🏷 Keywords

Glacier • Archive • Vault • Archive retrieval • Retrieval tiers • Vault Lock • Lifecycle transition • Data retention • KMS encryption • AWS Backup integration • WORM retention • Cold storage