Amazon S3 Reviews

Our primary use of S3 is for storing data. I'm a senior associate. 

This solution is valuable in that it helps us store all types of data. It's also easy to delete data when necessary and it's very user-friendly.

The upload speed for data and documents is sometimes slow and it would be helpful if that were improved. The other issue is that downloading data is quite expensive. 

I have used this solution for the past three years. 

We occasionally face stability issues with respect to upload speed but it's very rare. 

The customer support is good but it could be improved. When we raise a ticket, sometimes we have to make a follow-up call because we haven't heard back from them. 

Positive

The initial setup was easy. 

I find Amazon to be more efficient and more scalable compared to other solutions on the market. 

I find this solution good for both structured and non-structured data, as well as data access and encryption. It reads more requests per second than other solutions. 

I rate this solution seven out of 10. 

The primary use case of this solution is for storage.

The most valuable feature of the solution is auto-scaling.

I would like to see an easier setup that doesn't require as much training.

I have been using the solution for three years.

It is stable.

The solution auto-scales so it is easily scalable.

The initial setup is straightforward as long as you are familiar with the cloud services.

The cost varies based on the type of subscription you chose.

Currently, I use the solution for my phishing server and I pay $15 per month.

Before choosing the solution I evaluated DigitalOcean.

I rate the solution nine out of ten.

I suggest if you are interested in using the solution you should also use the other services offered by Amazon such as AWS, and EC2 so you have access to everything in one place.

Auto-scaling is very costly if you don't manage to control it. You need to have good training and understanding of the solution.

Our company has 30 staff members who use the solution for data storage. 

Uploads are secure and occur instantly.

The solution provides good data movement from Snowball to the S3 bucket. 

It is difficult to retrieve files in an emergency because the public cloud has data limits for immediate downloads so they often take twelve hours. We need better, immediate control of our content. 

The cloud and on-premises solutions should sync all data. 

Infrastructure services could be improved to provide free education related to the solution's features. For example, developers who do not have experience building games could learn how to do so with free support. 

I have been using the solution for nine years. 

The solution is very stable and I rate it an eight out of ten. 

The solution is scalable and there are no limits on data uploads. We upload four TB of data a day. 

Technical support can be challenging because we have to work through account managers. For urgent situations, our tech team contacts support to get assistance. 

I rate support a four out of ten. 

Neutral

The initial setup and creating buckets are very simple. 

We implemented the solution in-house. 

Not many products in the market beat the solution in terms of quality or price. 

The solution charges for data downloads. 

We currently use the public cloud but want to use a private cloud because there are speed issues when retrieving files in an emergency. For example, retrieving emergency video files might take twelve hours because the cloud will not allow immediate downloads. A private cloud will allow us to retrieve files immediately without a data limit. 

We are in talks with GreenLake, Atlassian, and Dell to find the best solution that optimizes our cost. There is a retrieval cost associated with the public cloud so we want to optimize these costs and switch to a private cloud. 

The solution offers great quality and price. We are closely evaluating the cost of other solutions to determine if it is worth it to move from a solution that works well for us. 

Cost is a primary concern because we manage three petabits of data. 

I rate the solution an eight out of ten. 

Currently, I am a cloud solution architect. I consult with developers and set up the architecture needed to deploy a solution. If a solution needs to be deployed within AWS, we sit down with the client and discuss the services that are most appropriate for that solution and design the architecture, which is given to the review board for approval. The AWS services we consume are dependent on the solution. Users from various departments will use the solution, depending on what's being deployed there. 

We have cold storage here, and I think that's useful. When it comes to commercialization, it's cheaper to put data that you won't be using into the data storage. You only use a little bit of the data needed each day for your transition, so you pay less. 

There could be more flexibility in configuration to allow more ways to connect to outside the PPC.

I started using S3 at my previous company, so I have been using it for five years. 

S3 is very stable.

Amazon S3 is highly scalable.

I rate AWS support 10 out of 10. 

Positive

Setting up S3 is straightforward.  At first, it was difficult because I didn't know how to use the solution. Now it takes less than five minutes to deploy S3. 

A solution architect needs to create a plan for what needs to be deployed, and the developer will deploy the solution. Most of the engagement happens before the deployment when the architect and the developer come to an agreement about the approach. One person procures the services, and others will test them and put them into the live environment.

We deployed the solution with the help of a consultant, who helped us implement some of the heavier stuff in the data lake. However, we did the basic stuff in-house because we've got the VPC to do it ourselves. 

The licensing cost is not bad. However, you need an understanding of the solution you're deploying and the services running. You will save money by shutting down some of the services when they're not in use.

I rate Amazon S3 nine out of 10. It's an excellent product. I'm also working with it for my personal use. I'm putting my documents and pictures into the S3 bucket.

We have multiple use cases for Amazon S3. We use Amazon S3 for storing static data and as a static site load balancer.

Amazon S3 could improve the load balancers. They are very basic compared to other solutions in the industry, such as F5. It has to be able to be analyzed up to a certain level. 

The basic features need some improvement, users should not have to use any third-party solutions, Amazon S3 should provide those particular features. The feature at present does not suffice most of the requirements of an enterprise-class organization.

The security could improve in Amazon S3. I am not seeing any value in the solution in security.

I have been using Amazon S3 for more than two and a half years.

Amazon S3 is a stable solution.

The scalability of Amazon S3 is good. However, it could be changed to make it much better than it is today.

We have approximately 25 projects that are using this solution.

We have 24/h support from Amazon S3 and their support has been very good. We have had quick response times. Within two to three days our issue gets resolved.

I rate the support from Amazon S3 a four out of five.

Positive

The initial setup of Amazon S3 is of a medium level of difficulty. It's not easy or difficult. There are certain things that need to change from a documentation perspective, or from an ease of use perspective. The configuration needs to be more user-friendly. The full deployment of Amazon S3 took approximately 15 days.

We did the implementation of Amazon S3 in-house.

There is a license to use Amazon S3.

Before doing any project we have criteria sheets to follow, we evaluate any solution on-premise or on the cloud. We compare all the cloud solutions, such as Oracle, Azure, and GCP, and whichever solution we find better for our requirement, we design a solution using it.

Our main corporate website is posted on Amazon S3 and our evaluations determined Amazon S3 was the best solution for our use case. This is why we choose it.

My advice to others is Amazon S3 is a good solution. However, it depends on the use case that you have. This will determine if this solution is the best fit or if another solution would be better. The requirements of your use case have to be met.

I rate Amazon S3 an eight out of ten.

I am using Amazon S3 for our retail portal sites and data scientist users are using it for analytics and Athena.

The most valuable features of Amazon S3 are the global availability, resiliency, and ease of access control.

Amazon S3 could improve the performance reports. It would be a benefit if they were more comprehensive.

I have been using Amazon S3 for three years.

Amazon S3 stable is very high.

The scalability of Amazon S3 is very good.

We have approximately eight to 10 concurrent users using this solution.

The technical support is good.

I rate the support from Amazon S3 a five out of five.

I previously used Blob Storage in Microsoft Azure. We had a multi-cloud strategy, and we had both solutions available to use. For some projects, we used Amazon S3, and for the others depending on what services they needed to use, we used Microsoft Azure. We got Amazon S3 and Microsoft Azure for different projects.

Amazon S3's initial setup is easy, and simple to work with.

I rate the setup of Amazon S3 a four out of five.

Once Amazon S3 is set up, the developers use it for doing analytics and there isn't much in the way of ongoing maintenance.

We have received a return on investment using Amazon S3, we find it inexpensive.

Amazon S3 is straightforward, scalable, and globally available and there are some good security features for making sure control over access is taken care of. I would recommend this solution to others.

I rate Amazon S3 a nine out of ten.

We use Amazon S3 primarily as a repository for storing objects such as images and files. It serves as a storage solution where we can efficiently save and manage the data we collect.

Lifecycle policies in Amazon S3 is an important feature because they help manage transitions effectively. We can monitor how frequently objects are accessed and transition them to more cost-effective storage tiers. Additionally, the security architecture, including access control policies, is crucial for protecting our data. These three features—lifecycle management, cost-effective storage transitions, and robust security

From a pricing perspective, there’s still room for improvement, especially for smaller or startup entities that are very cost-conscious. If Amazon could repackage their S3 products to be more affordable and appealing for these smaller users, it could attract more customers, particularly at the lower end of the market. 

You can easily add more space as needed, and you can leverage the available metrics to set up alerts for when utilization reaches certain thresholds. It is highly scalable.

Our internal staff population exceeds one hundred. However, the number of clients accessing the application has surpassed ten thousand and continues to grow.

There are occasional support issues where parts of the application might misbehave, often after scheduled upgrades. When this happens, we need to raise a support ticket. However, the team has been very agile in addressing these issues and quickly resolving them.

The initial setup is straightforward. I have a DevOps team that handles the setup and management tasks. By the time I joined, a lot of the S3 configurations were already in place. For the few instances where we needed to set up S3, it involved just a few clicks. As the Chief Technical Officer, I focus on architecting solutions and providing guidance, while the DevOps team implements them. Overall, the process has been seamless.

For disaster recovery, we're just starting to implement our strategy. Amazon fulfills its part of the shared responsibility model by providing highly available infrastructure, including data redundancy and regional instance deployment. Their infrastructure is designed to support high availability, which aligns with their disaster recovery stipulations. We’re still in the process of testing our own disaster recovery plans, including running full-scale disaster scenarios to ensure we meet our recovery time objectives (MTTR) and recovery point objectives (MTTD). Although we haven't experienced any outages or data loss since starting operations, we are content with Amazon's disaster recovery infrastructure and will continue to build and test our own processes at our own pace.

Overall, I rate the solution a nine out of ten.

We use Amazon S3 for a file storing system. The solution is cloud-based.

We're working with 10-15 applications.

The most valuable feature is the sharing capabilities.

I would like there to be more support without needing to use Transfer Family. 

I have used Amazon S3 for about five years but not at my current organization.

I would rate the stability as eight out of ten.

The scalability is good.

I have also used Azure.

The price is okay.

I would rate this solution as nine out of ten.

I would recommend Amazon S3 if you have the use case for it, but Azure provides a similar service.