The Amazon S3 Glacier storage classes are purpose-built for data archiving, providing a low cost archive storage in the cloud. According to AWS, S3 Glacier storage classes provide virtually unlimited scalability and are designed for 99.999999999% (11 nines) of data durability, and they provide fast access to archive data and low cost.
$0
Per GB Per Month
Azure Blob Storage
Score 9.0 out of 10
N/A
Microsoft's Blob Storage system on Azure is designed to make unstructured data available to customers anywhere through REST-based object storage.
If your organization has a lot of archival data that it needs to be backed up for safekeeping, where it won't be touched except in a dire emergency, Amazon Glacier is perfect. In our case, we had a client that generates many TB of video and photo data at annual events and wanted to retain ALL of it, pre- and post- edit for potential use in a future museum. Using the Snowball device, we were able to move hundreds of TB of existing media data that was previously housed on multiple Thunderbolt drives, external RAIDs, etc, in an organized manner, to Amazon Glacier. Then, we were able to setup CloudBerry Backup on their production computers to continually backup any new media that they generated during their annual events.
In Azure, it is the storage to use, and in my view, the Blob Storage offers more, or finer-grained configuration options, than S3. So my recommendation would be to check in detail what is offered. As the Blob Storage is more or less a Microsoft exclusive product, the "interoperability" is more limited than, for example, with S3. The S3 is more widely adopted, and if you cannot exclude a migration scenario from one cloud provider to another, additional effort is needed.
Blob storage is fairly simple, with several different options/settings that can be configured. The file explorer has enhanced its usability. Some areas could be improved, such as providing more details or stats on how many times a file has been accessed. It is an obvious choice if you're already using Azure/Entra.
Microsoft has improved its customer service standpoint over the years. The ability to chat with an issue, get a callback, schedule a call or work with an architecture team(for free) is a huge plus. I can get mentorship and guidance on where to go with my environment without pushy sales tactics. This is very refreshing. Typically support can get me to where I need to be on the first contact, which is also nice.
Since the rest of our infrastructure is in Amazon AWS, coding for sending data to Glacier just makes sense. The others are great as well, for their specific needs and uses, but having *another* third-party software to manage, be billed for, and learn/utilize can be costly in money and time.
Azure Blob Storage was used only because we were already using it for other projects, and it has a good reputation for being a reliable cloud provider. It also has widespread regional availability and allows for data replication. It can also be easily accessed via the API or by the console, which makes it a solid, user-friendly option.
We seldom need to access our data in Glacier; this means that it is a fraction of the cost of S3, including the infrequent-access storage class.
Transitioning data to Glacier is managed by AWS. We don't need our engineers to build or maintain log pipelines.
Configuring lifecycle policies for S3 and Glacier is simple; it takes our engineers very little time, and there is little risk of errant configuration.
Azure Blob Storage is just way cheaper than anything we could afford to do on-prem. Forecasting spend is way easier with predictable growth than it is with large capital expenditures every few years, and that ability to grow or shrink dynamically is simplifies things.
