English translation
AWS Glacier Cold Storage: Deep Archive for Long-Term Data Retention
AI Article Decision Snapshot
Turn the lesson into workflow, model, budget, and security checks before choosing tools.
Use this quick snapshot before leaving the article. It keeps the next search tied to practical AI software, model/API, cost, privacy, and implementation questions.
Workflow fit
Identify the real job behind the article: coding, research, document review, support, analytics, content, or internal automation.
Model or tool decision
Decide whether the next step is a software shortlist, an AI tool comparison, an API platform choice, or a model benchmark.
Budget and usage signal
Estimate seats, API calls, prompt volume, retries, review time, and fallback work before assuming the workflow is cheap.
Security and privacy review
Check whether source code, customer data, private documents, prompts, logs, or embeddings will enter the AI workflow.
In the previous section, we introduced Amazon EBS and instance storage—two storage services well-suited for applications requiring fast access and high performance. However, not all data needs frequent access; for such infrequently used data, cold storage solutions become essential. AWS provides Amazon Glacier, a service specifically designed for long-term archival storage.
What Is Amazon Glacier?
Amazon Glacier is a low-cost cloud storage service offered by Amazon Web Services (AWS), purpose-built for data archiving and long-term backup. Users can store infrequently accessed data in Glacier at significantly lower costs than standard Amazon S3 storage.
Advantages of Glacier
- Low Cost: Glacier dramatically reduces storage expenses—especially when storing large volumes of data over extended periods.
- Durability: Data stored in Glacier is redundantly distributed across multiple Availability Zones, delivering 99.999999999% (eleven nines) durability.
- Security: Glacier integrates with AWS Identity and Access Management (IAM) and supports server-side encryption to ensure data confidentiality and integrity.
Common Use Cases for Glacier
- Long-Term Data Retention: Meeting regulatory or compliance requirements that mandate multi-year data retention.
- Backup and Disaster Recovery: Maintaining secure, durable backups for business continuity and recovery.
- Digital Asset Archiving: Preserving digital content—including videos, images, documents, and other media—for historical or legal purposes.
Glacier Storage Tiers
Glacier offers three retrieval tiers, enabling users to balance cost and access speed according to their needs:
- Standard Retrieval: Designed for data that requires relatively quick access but isn’t frequently retrieved—typically available within 3–5 hours.
- Bulk Retrieval: The most cost-effective tier, with retrieval times ranging from 5 to 12 hours—ideal for large-scale, non-urgent restores.
- Expedited Retrieval: Optimized for urgent access needs, delivering archived data in as little as 1–5 minutes.
How to Use Amazon Glacier
Creating a Glacier Vault
The first step is to create a Glacier vault—a logical container for your archives. You can do this via the AWS Management Console, AWS CLI, or AWS SDKs. Below is an example using the AWS CLI:
aws glacier create-vault --account-id - --vault-name my-glacier-vault
Here, my-glacier-vault is the name you assign to your new vault. Upon successful execution, you’ll receive an Amazon Resource Name (ARN) uniquely identifying the vault.
Uploading Archive Data
After creating the vault, you can upload files—each uploaded object is called an archive. To upload using the CLI:
aws glacier upload-archive --account-id - --vault-name my-glacier-vault --archive-description "My first archive" --body path/to/myfile.txt
The --body parameter specifies the local file path. Upon success, AWS returns a unique ArchiveId, which you’ll use later to manage or retrieve that archive.
Retrieving Archived Data
Because Glacier is a cold storage service, uploaded archives are not immediately accessible. To retrieve them, you must first initiate a retrieval job. Follow these steps:
-
Initiate a Retrieval Job
Run the following command to start the retrieval process:aws glacier initiate-job --account-id - --vault-name my-glacier-vault --job-parameters '{"Type":"archive-retrieval","ArchiveId":"YOUR_ARCHIVE_ID","Tier":"Standard"}'Replace
YOUR_ARCHIVE_IDwith the actual archive ID, and set"Tier"to"Standard","Bulk", or"Expedited"based on your urgency and budget. -
Check Job Status
Monitor progress using:aws glacier describe-job --account-id - --vault-name my-glacier-vault --job-id JOB_IDThis returns metadata including job status (
InProgress,Succeeded, orFailed) and estimated completion time. -
Download Retrieved Data
Once the job completes successfully, download the output with:aws glacier get-job-output --account-id - --vault-name my-glacier-vault --job-id JOB_ID output.txtThis saves the retrieved archive to
output.txtlocally.
Pricing Structure
When using Amazon Glacier, consider the following cost components:
- Storage Costs: Charged monthly per gigabyte stored.
- Retrieval Costs: Vary by tier—Expedited is most expensive, Bulk least expensive.
- Data Transfer Costs: May apply when downloading data out of AWS (e.g., to the internet); inbound transfers and inter-AZ transfers are free.
Summary
This article introduced Amazon Glacier, AWS’s purpose-built cold storage service for archival workloads. We covered its core benefits, typical use cases, available retrieval tiers, and practical steps for vault creation, archive upload, and retrieval—all while highlighting how Glacier helps optimize long-term storage costs for infrequently accessed data.
In the next article, we’ll dive deeper into Amazon RDS, AWS’s managed relational database service, exploring how to deploy, configure, and operate databases efficiently in the cloud.
Apply This Lesson
Turn this article into AI software, model, API, and security decisions.
English Article FAQ
Use this article as evidence before choosing AI tools
How should I use this AI Tutorials article?
Use it as the implementation or learning layer, then connect the idea to AI software buyer guides, tool comparisons, benchmarks, API choices, and security checks before making a production decision.
Is this English article different from the Chinese original?
The English edition is localized for global AI readers while preserving the original diagrams, screenshots, prompts, code examples, and source context from the Chinese article.
What should I read after AWS Glacier Cold Storage: Deep Archive for Long-Term Data Retention?
Continue with AI Software Buyer Guides, AI Tools Workbench, Best AI Coding Agents, AI Model Benchmarks, OpenAI vs Anthropic API, or LLM Security Tools depending on the decision you need to make.
Can this article alone choose an AI product or model?
No. Treat the article as evidence and context, then validate fit with pricing, privacy requirements, integration effort, benchmark results, workflow tests, and fallback planning.
Continue