Amazon Glacier Tutorial

Here in this section of AWS tutorial you will learn the major concepts of Amazon Glacier and also learn how to create an Amazon S3 Glacier at the end of this blog.

Amazon Glacier Tutorial
 23rd Aug, 2019
 157 Views

AWS Glacier

Among the wide variety of storage solutions that are provided by Amazon, Amazon Glacier is the one that is designed to be the most economical cloud storage solution. And of course, coming from Amazon Web services, this storage service is also well known for the data security that it offers. Any kind of data can be stored in AWS Glacier, regardless of the format of the data, be it a video file, an image file, a single text file or zip files. In this tutorial, we will dive deeper into the concepts of Amazon Glacier and understand all the fundamentals of this cloud storage solutions.

Check this Intellipaat Amazon Glacier video :

Following is the list of all the topics that I’m going to cover in this tutorial, in case you want to jump to any particular topic.

So without any further ado, let’s get started.

What is Amazon Glacier?

Amazon Glacier, as we have already discussed is an economical cloud storage solution provided by AWS. But then so is Amazon S3, isn’t it? So why did we need Amazon Glacier if we already had an inexpensive storage solution, which is Amazon S3? To answer that, let me explain Amazon Glacier again and this time in depth.

Amazon Glacier is an economical and online storage solution by AWS and like S3 it provides simple, secure, cloud-based data storage that can be easily scaled up and down as needed. But unlike S3, which is designed for frequently accessed data and is mainly intended to provide quick access to data, AWS Glacier is designed for long term storage  for cold data that will not be needed to retrieve very frequently and quickly.

Get certified from top AWS course in Hyderabad Now!

So, to define Amazon Glacier again, AWS Glacier is a long term and low-cost cloud storage solution, optimized for infrequently used data or otherwise known as “cold data”.

Following are some interesting facts about Amazon Glacier:

  • Unlimited amount of data can be stored in Amazon Glacier.
  • Amazon Glacier provides average annual durability of 99.999999999%
  • While the data is uploaded in Amazon Glacier, it stores the data across multiple availability zones before it confirms the successful upload.
  • One can enjoy the Amazon Glacier storage solution at the cost of just $0.007 per GB per month.
  • Data stored in Amazon Glacier is immutable and is encrypted at rest by default.

We now know what is Amazon Glacier and why we need it. Now, let us take a look at the data model of Amazon Glacier.

If you have any doubts or queries related to AWS, do post on AWS Community.

Archives and Vaults in AWS Glacier

Archives and Vaults are at the core of the Glacier data model. Glacier is a REST-based web service, which means that it relies on the REST architecture. Job and Notification-configuration resources are included in the Glacier data model.

Before starting with AWS  Glacier, we need to know why Glacier needs archives and vaults. Glacier uses Archives and Vaults to store data.

Archives

The actual data is stored in archives. You can store any type of data in an archive, such as images, video, audio and documents. There are two ways to upload files to an archive. You can directly upload a single file and create an archive or you can “TAR” or “ZIP” multiple files and upload it as a single archive.

Following are some important pointers about Archives:

  • Maximum size of a single archive is 40 terabytes
  • Unlimited number of archives can be created
  • Virtually unlimited data can be stored in S3 Glacier
  • An archive cannot be updated after creation

Want to read more about AWS? Go through this AWS Tutorial!

Vaults

We have stored the data in the archives, but where will the archives be stored and grouped? That is where Vaults come into play. Vaults are containers where you can store multiple archives.

Following are some important pointers about Vaults:

  • 1000 vaults are allowed for a single AWS account.
  • You can set every vault with access policies to make it available or deny for users
  • You can use AWS SDKs to do a variety of vault operations
    • create vault
    • delete vault
    • lock vault
    • list vault metadata
    • tag vaults

Features in Amazon Glacier

In this part of the blog, we will be looking at the key features of Amazon S3 Glacier.

The key features of Glacier are:

  1. Data Retrieval features
  2. Amazon Glacier select
  3. Vault lock
  4. Access control
  5. Vault inventory
  6. AWS Software Development Kits (SDKs)

Data Retrieval features

  • These are features provided by Amazon Glacier for different speeds and making it more cost-effective. There are three different retrieval methods – Expedited, Standard, and Bulk. We will look at these methods in depth in the next part of this blog.

Amazon Glacier Select

  • AWS Let’s you to run queries directly on the archives rather than extracting the entire archive which reduces the access time.

Get certified from top AWS course in Chicago Now!

Vault lock

  • Glacier lets you create locks on individual vaults by applying policies. For instance, WORM (Write Once Read Many) policies can be used to prevent further edits after uploading.

Access control

  • AWS IAM can be used to securely access the management console and also secure the S3 Glacier data.
  • You can create multiple users using IAM and specify separate user policies for every individual to restrict or allow access to certain parts

Vault Inventory

  • Amazon S3 Glacier always has an inventory of all the archives in every vault. The inventory will contain the name, creation date, and description of the archives.

AWS SDKs

  • All upload and retrieval functions are done by AWS SDKs or the APIs (Application Programming Interfaces). AWS SDK is supported by multiple programming languages and frameworks like JAVA, .NET, Python and PHP. Programming is made easy by SDKs and APIs.

Data retrieval and retrieval policies in Glacier

As we know, Data retrieval is a key feature in Glacier. Now, let us look at it in detail. There are three types of Data Retrieval:

  • Expedited
    • These type of retrievals can happen within 1 – 5 minutes. This is used under an urgent circumstances when you need to access data quickly from a subset of archives.
  • Standard
    • This retrieval takes 3 – 5 hours to make the data accessible. This is the most commonly used retrieval method.
  • Bulk
    • Bulk retrieval is used to access significant portions of data with cost-effectiveness.

Are you preparing for AWS interview? Then here are latest AWS interview questions

Retrieval policies in Glacier

Amazon S3 Glacier data retrieval policies can be user-defined. You can add policies with just a few clicks. You can limit retrievals to “Free Tier Only” or “Max Retrieval Rate” to limit speed and save costs.

Glacier will not exceed the conditions which you have mentioned in the policies. Also, even if you have to upload more data than you have provided, the policy will not allow. There are two ways you can set up data retrieval policies, first is using the AWS Management Console and another way is using Amazon Glacier APIs.

Benefits of AWS Glacier

  1. Fast Retrievals (1 – 5 minutes)
    • AWS Glacier provides lightning fast data retrieval. You can retrieve data within 1 – 5 mins if it is Expedited. Also, Standard is available which takes 3 – 5 hours.
  2. Scalability & Durability
    • Glacier has a 99.999999999% durability. Uploaded data is automatically distributed across a minimum of three physical Availability Zones that are geographically separated.
  3. Low Cost
    • Glacier allows you to store large amounts of data at a very low cost and also provide fast retrieval speeds. It would only cost you 0.0007$ per month for storing per GB and this is applicable only when it exceeds the free tier limit. You can receive 10 GB of data every month.
  4. Highly supported by Partners, Vendors, and other AWS services
    • Not only AWS services support Glacier. Third-party software and MNC vendors who need to do Backup & Recovery, Archiving and Disaster Recovery use Amazon S3 Glacier.
  5. Easy Querying
      • Amazon S3 Glacier is the only archiving service which allows a user to query in the management console itself and retrieve separate datasets from a huge data archive.

    When can Amazon Glacier be used?

Let me list down all the scenarios where you can use Amazon S3 Glacier.

  1. Applications who have a lot of multimedia data coming in can use Amazon Glacier because of the amount of data can sometimes reach petabytes too. For example, Twitter needs Glacier.
  2. Research and Development organizations use huge data sets for their scientific analysis. They need a way to store all the input, training and output data.
  3. To replace legacy storage systems. Firms who want to shift from traditional data storage to cloud storage can use Amazon Glacier. The main reason is there is no upfront cost and also there is no burden of maintaining the hardware.
  4. Hospitals need to store patient information for decades to meet regulatory requirements. Huge hospital networks need Glacier because the data can often cross petabytes.

Creating an Amazon Glacier Vault

Step 1: Open AWS Management Console and go to Amazon S3 Glacier service. After that click on “create vault” to move forward.

Step 2: There are 4 steps normally. First, choose the Region and then provide a name for your vault. Then click on “Next step”

Step 3: As this is a demo, do not enable notifications and that means there is no “Step 3: Event  Notification Details”.

Step 4: Review the content and click on “Submit”.

Step 5: An Amazon S3 Glacier vault has been successfully created.

Step 6: You can set up Retrieval policies according to your needs. I have provided it as “Free Tier only” as it is just a demo.

This is how you create an Amazon Glacier Vault. That’s all about Amazon S3 Glacier. Now it is in your hands that how you are going to use it.

Please acknowledge that this a backup service, and can be used in conjuction with S3 for taking backup data. Also the reason it is used is, because it is more cheap than S3. Please include this point, in the starting of the page as well.

If you have any doubts or queries related to AWS, do post on AWS Community.

 

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *