What is our primary use case?
I use the solution for storage. We use it for application data storage and retrieval and for data backup. It has various use cases for storing applications, platforms, or other data types.
What is most valuable?
I like creating buckets where data can be segregated at a high level and then routing the appropriate data to each designated bucket. In terms of value, I would say that the tool gets the job done in a simpler manner.
What needs improvement?
I believe the usage reporting could be simplified, particularly for billing purposes. Overall, I find Amazon S3 Glacier's reporting system somewhat confusing compared to other hyperscalers in the market.
In terms of improvements, I believe AWS could enhance the service by providing regional accelerators to reduce network latency and offering options for caching buckets for easier configuration. Additionally, providing options to specify usage duration for particular sessions or partitions would be beneficial. While it is intuitive to some extent, there is room for improvement to make it even more user-friendly.
For how long have I used the solution?
I have been using the product for two years.
What do I think about the stability of the solution?
Monitoring apps and systems should be part of deployment. You should be able to set up auto-scaling and alerts during deployment. For example, you could get a warning if CPU usage hits 70 percent and a critical alert at 80 percent.
What do I think about the scalability of the solution?
We haven't come across many instances of large data volume. However, when we encounter it, it seems to be more about ensuring that our applications can handle the workload. Fortunately, we haven't experienced any significant lag issues.
How are customer service and support?
I haven't contacted the support team yet. We don't have any specific support package from Amazon for the services we're using. Instead, we rely on Amazon's public support.
How was the initial setup?
Amazon S3 Glacier's deployment is straightforward. The deployment process typically involves several steps. Firstly, you must acquire the image, select the appropriate zone, and deploy it within it. Following that, you would define the necessary parameters. In my experience, I've mostly worked with virtual machines rather than containers.
Typically, a team of just one person is sufficient for deployment and maintenance, maybe with a mentor.
What's my experience with pricing, setup cost, and licensing?
I've operated with Amazon S3 Glacier in two modes. Firstly, there's the trial mode, where I experimented with the platform, learned its functionalities, and applied it to my work. Secondly, there's the corporate account mode, where my team handles the operations, and I receive billing reports.
What other advice do I have?
I haven't extensively used the retrieval options. Generally, we haven't encountered any significant issues with the service, although occasional network latency might occur due to various factors such as server positioning. However, the retrieval process has been fairly reliable.
Rating the tool on a scale from one to ten is quite challenging. It's akin to comparing different brands of ovens, such as Murphy Richards, Samsung, or LG. All of them are excellent in performing their basic function. However, the differences lie in their operation, user interface, and user-friendliness. Similarly, AWS stands out as a leader in virtual services, but comparing it directly to others is not straightforward.
I rate it a nine out of ten. The tool's integration into existing workflows is simple. Whether or not to recommend it depends on the requirements of the individual or organization. It's essential to assess what kind of data they intend to use it for and what their data needs are. Appropriate recommendations can be made based on these factors and other qualifying queries.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.