Amazon S3 Reviews

We have a data warehouse and a data lake using Amazon S3. Additionally, we use it for application streaming.

We have our computer systems that have storage but we do use the cloud storage available from Amazon S3. However, it depends on the type of data we have and whether we use the cloud or not.

The most valuable feature of Amazon S3 is its flexibility as a solution to suit many different use cases.

I have been using Amazon S3 for approximately six years.

Two third of our company use this solution.

The support is better than other cloud providers but sometimes it takes a while to have a resolution to our issues.

I rate the support from Amazon S3 a seven out of ten.

The initial setup of Amazon S3 was straightforward.

I rate the initial setup of Amazon S3 a ten out of ten.

We have a few developers that we use for deployment.

The solution is worth the money and we have seen an ROI. However, it is not our primary goal. We are trying to optimize different areas. 

Amazon S3 is a cost-effective solution compared to the others.

I rate the price of Amazon S3 a two out of ten.

I rate Amazon S3 a nine out of ten.

We use Amazon s3 to store objects like data in my environment.

In one of my previous environments, I was brought in to help with the challenges they were facing resulting from a data breach in the S3 bucket. What I noticed in that environment was that every user had full access into their S3 bucket, and accidentally deleted data without a trace.

They did not know how some of their data was missing. One of the first services I suggested was enforcing access control by applying IM best practices, such as granting list privilege permission to our users to avoid overpowering them. I created a single group and then applied specific permissions to that group.

All users added to that group were able to inherit the same permission and privileges. Versioning was enabled which keeps multiple variant of objects in the same bucket and also safeguards against accidental deletions. I also enabled multi-factor authentication which prevented accidental bug deletion by requiring the user who initiate the delete action to prove physical possession of an MFA device with an MFA code. 

The versioning of this solution for accidental deletion has been most valuable. 

You need to fully understand the solution's best practices to get the most out of its security features. 

This is a stable solution. 

This is a scalable solution. 

The initial setup is straightforward. 

We have seen a return on investment with S3.

I would rate the pricing a nine out of ten. Pricing depends on a particular class where you want save your objects. There are different classes when it comes to storage in S3.

I would advise others that this is a scalable solution that offers comprehensive security. 

I would rate this solution a ten out of ten. 

We use this solution for storing the input-output of our processing. We are customers of Amazon. 

Version control is great, it means we can store incremental data, and get high availability and fault tolerance. If we accidentally delete something we can recover it by using S3. It also enables the option of reverting to old files. 

The read drive speed is not as fast as it should be. If we want to access data, we should be able to do it quickly. 

I've been using this solution for five years. 

The solution is scalable, there are no limitations on storage. There are around 10,000 users in the company. 

Amazon provides good documentation for this solution so we've never contacted technical support. 

The initial setup is easy. It just requires logging in to AWS, and it's available.

This is a pay-as-you-use, on-demand service. It's not very expensive. 

We went with S3 because of its high availability, fault tolerance and scalability. Those are the three main reasons we chose it. 

We are very flexible with our use cases and it fits most clients.

The most valuable feature is the automated replication of the data. You can store things and they automatically replicate somewhere else. So if you have an issue, you have a backup, and that is very good. You can set up how often you want it backed up, and I find that extremely useful.

I would like to see the API for beginners improved because it is hard to understand. It is based on the idea of a container when most programmers just understand directories and subdirectories. For a beginner, the API is a bit confusing.

I have been working with Amazon S3 for the past four years

The solution is very stable.

The scalability is definitely present from hundreds to thousands depending on the client.

I have used other solutions in the past, but none of them are as scalable.

The initial setup If you have the experience is fairly simple. If you do not, then it is fairly complex.

I know it is very inexpensive compared to other solutions.

I would basically recommend that individuals just follow the guidelines AWS as they are very good. I would rate Amazon S3 an eight on a scale of one to ten.

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 uses the solution for deep CI backups. We have thousands of customers who use the solution and access our application. 

The solution is good and includes all the features we expect. 

The solution's pricing should be modified to automatically expand storage based on prior usage. For example, our monthly usage is very low so our storage allotment should be increased by 200%.

I have been using the solution for five years. 

The solution is stable. 

The solution is scalable. 

Technical support is good so I rate it them a nine out of ten. 

Positive

I did not previously use another solution. 

The setup is very easy. 

The pricing depends on your region and is reasonable. For example, the price per gigabyte is .0025 in the South Pacific and .0023 in Europe.  

We use the solution and EC2 with similar frequency depending on use case. 

I recommend the solution and rate it a nine out of ten. 

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.