Amazon Elastic Block Store (EBS) vs. Amazon S3 Glacier

It provides the optimized storage performance and cost for your workload and these options really work with SSD-backed storage and it improves the database performance. Keeping backups of your EC2 resources, including EBS volumes is a little bit tricky and its takes some more time and increase through put is also a tiring job to do.

Incentivized

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.

Incentivized

• Raw storage capacity attached to your instance operative system
• Frequent data rewriting (mission critical for reporting)
• Low latency connectivity (14 reporting subsidiaries in different time zones)
• Videly spreaded for implementation
• Fast accessible drive
• Block storage are core for Java, Net mobile applications

Incentivized

• Cheap storage of backup data.
• Can be used as a part of the entire suite of tools from Amazon, without requiring you to leave the familiar stack.

Incentivized

• Creating too much EBS can be disaster if you are not properly organized by tags
• In terms of pricing it's a bit on higher side.
• In terms of performance, there is room for improvement as sometimes reading or saving the data can be painful.

Incentivized

• Accessing data stored in Glacier is slow. That shouldn't be a surprise, but it is undesirable nonetheless.
• Retrieving a large amount of data can be expensive; Glacier's intended use is as an archive of rarely-accessed data.
• Some users regard Glacier with fear and uncertainty. Slow retrieval time and high retrieval cost are the greatest risks of using Glacier, and they are also the Glacier interaction that most users have the least experience with.

Incentivized

Amazon EBS is a great tool and fairly easy to use as long as you are familiar with the Amazon Web Service ecosystem. It allows a great way for you to move storage around easily and allows you to quickly provision storage as needed based on the business requirement. For us, it's easy to move between our EC2 images that had been linked with EBS storage between these Amazon accounts.

It is difficult to delete the data as you have to wait for inventory and then bucket modification has to expire.

Incentivized

The support for Amazon Elastic Block Store is great as long as you can articulate your needs. Like most tools, there may be some back and forth before you find a support person that is knowledgable in the tool and can provide you with necessary insights.

So far I have only used Amazon Elastic Block Store (EBS) and Azure but comparatively [I] prefer AWS elastic Block store as its having more advantages than Azure and I found it quite satisfactory and it helped a lot for information storage. We are not looking for any other hosting provider at this time.

Incentivized

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.

Incentivized

• When your application needs high IOPS storage, this is a great solution that will keep your business functioning.
• Without Amazon Elastic Block Store you could try spreading your data across several standard drives, but that introduces complexity and still has IOPS limits.

Incentivized

• Helped us meet compliance requirements while minimizing costs.
• Simple integration with almost no changes required to our existing S3 management policies.

Incentivized