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.7 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.
$0.01
per GB/per month
Pricing
Amazon S3 Glacier
Azure Blob Storage
Editions & Modules
Bulk Retrieval Pricing
$0.0025
Per GB Per Month
Storage Pricing
$0.004
Per GB Per Month
Retrieval Pricing
$0.01
Per GB Per Month
Expedited Retrieval Pricing
$0.03
Per GB Per Month
Block Blobs
$0.0081
per GB/per month
Azure Data Lake Storage
$0.0081
per GB/per month
Files
$0.058
per GB/per month
Managed Discs
$1.54
per month
Offerings
Pricing Offerings
Amazon S3 Glacier
Azure Blob Storage
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon S3 Glacier
Azure Blob Storage
Considered Both Products
Amazon S3 Glacier
Verified User
Anonymous
Chose Amazon S3 Glacier
We only compared the costs but as most of our machines and services are AWS centric and final call was with client so they decided to go with AWS Glacier only.
Amazon Glacier isn't a direct competitor to the products I've listed; it could compare to the clouds/data warehouses each of these products use to store their data. In the case of CloudBerry, Amazon Glacier is used with it to create a complete archival backup system. That …
Glacier is convenient with systems already on AWS and cheaper than S3 for data that needs to be accessed infrequently. A great tool for any team to use that has a legacy system or data.
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 …
The other alternatives for us would involve moving objects out of S3 to some other object storage services, which would generate a lot of network traffic, or keep the objects on more expensive storage.
It is significantly cheaper than other services, however, it is because it actually is a slightly different service. The other services we've tried allow live reading/writing of data as needed, whereas Glacier is a "cold storage" service. So essentially your choice ends up …
Blob storage lets us control the file source/hosting and retain everything within our Microsoft ecosystem. Blob is less feature-rich than some of the other products. Still, we consider it as a value-added product included within our environment, and alternative products are not …
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 …
We didn't actually evaluate anything but Azure Blob Storage since it worked so well for backups and Audit logs and the price point was good enough for us.
Azure Blob Storage is the best choice to store files when the app runs in Azure. It also has some advantages over S3, like Shared Access Signatures, that make it easy to control access to files directly via a URL. Azure Blob Storage is very fast and we have not had any major …
S3 seemed to be just as functional as blob storage in our analysis. The only real difference is we already were on the Microsoft platform with 365, and it was an easy system to continue to learn. That was the only real deciding factor between the two that made any difference …
Ease of use and availability to actual usage makes it my first choice. I feel like IBM Cloud is where azure was 5 years ago in terms of implementation and ease of use. AWS has some great functionality but it almost feels like you need to learn how to work under the hood of a …
As described in the use case, it is perfect for backup data storage where you do not expect to retrieve the data often. Think of it as a data dump; it is nice to know you have a backup, but it actually is expensive and somewhat difficult to retrieve everything.
Azure Blob Storage is well suited for cases where you are working with different data formats and looking for cost-effective storage solutions based on access frequency. Another area of strength is the encryption of data at rest, and encryption can be managed on your own. However, it may not be appropriate for transferring large data very fast.
Reduced cost. We were able to reduce our storage infrastructure by several hundred terabytes by consolidating redundant copies and dedupe/compression on files.
Extremely high level of redundancy. We can replicate data in a variety of ways that we would never have been capable of on our own hardware.
If we are transferring huge amount of data (outbound), it can get quite expensive.
With new features being added constantly, although a good thing, at times it becomes difficult to keep up with the changes. Documentation needs to keep UpToDate and should include best practices.
Performance can be improved especially when it comes to cold storage.
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.
Documentation sometimes appears to be out of date or not fully documented properly with new releases. It is like documentation comes out for a specific version and is quickly out of date. Another issue is documentation is scarce on new releases and only seems to get properly updated (and sometimes is still wrong) once enough people hit the forums to complain.
Amazon Glacier isn't a direct competitor to the products I've listed; it could compare to the clouds/data warehouses each of these products use to store their data. In the case of CloudBerry, Amazon Glacier is used with it to create a complete archival backup system. That said, when using Amazon Glacier along with a product like CloudBerry, you can create a reliable, inexpensive cloud backup system for retaining HUGE quantities of data for much less than these other cloud backup solutions. HOWEVER, if you want to restore said data, the cost and complexity begin to become a major concern, so Amazon Glacier should only be considered in situations where you don't plan to touch the data regularly, if at all, once it's at Glacier.
Blob storage lets us control the file source/hosting and retain everything within our Microsoft ecosystem. Blob is less feature-rich than some of the other products. Still, we consider it as a value-added product included within our environment, and alternative products are not needed for our requirements. Keeping the hosting within our tenant locale is vital to us.