Amazon S3 Reviews

I use Amazon S3 as storage and a platform for installing various types of software.

Amazon S3's best features are its reliability and capacity to expand.

Amazon S3's unit of measure for expansion should be smaller.

I've been using Amazon S3 for three years.

Amazon S3 is very stable.

Amazon S3 is scalable.

Previously I used Microsoft and Oracle.

I'd advise those thinking of implementing Amazon S3 to carefully plan their requirements and not use too many servers. I would recommend Amazon S3 to others and rate it eight out of ten.

I'm a consultant who provides services for companies of various sizes here in South Africa. Our company is still small, with only about 20 clients. I use S3 for hosting my websites and other storage services. S3 can be used for static and dynamic websites as well as file storage. In terms of dynamic websites, I use S3 in addition to other technologies in a computerless environment. In other words, I don't need a virtual machine to have a dynamic website hosted on Amazon Web Services.

E3's most valuable feature is CloudFront.

You need to do some things to make the files and updates immediately accessible. If you don't know those steps, you will wait forever for your updates to take effect or be seen by the public.

That is the only area where a newcomer might get frustrated with hosting on S3. The files are available immediately when they are first deployed, but it takes some time when they make changes if you don't understand the simple procedure you need to follow for it to happen immediately.

The process needed to show updates immediately is a problem. You have to go somewhere to delete whatever is propagated and restart the propagation somehow. That is the only issue that I think they could fix with hosting on S3 as far as websites are concerned.

I would also like S3 to have the ability to do dynamic websites without the need to do reconfigurations outside of S3. You should be able to switch on dynamic websites in S3, and then it works. I shouldn't need to go elsewhere within Amazon Web Services to get a dynamic website to work.

I've been using S3 for about three years 

It's a cloud service, so our scalability is good. I haven't had any issues. At the same time, I haven't had a situation where a client needed to expand the footprint of their site tremendously. I don't have massive clients like Netflix.

I was never in a position where I needed to request AWS tech support.

I've also used Azure's tool, and S3 is far more stable I haven't seen the same issues on AWS that I'm having on Azure. Amazon CloudFront is way faster. The websites are loading way faster than when you do it on Azure CDN.

Another advantage of S3 over CDN is the fact that I can deploy my websites on Amazon S3 with the root domain and the sub-domain loading the website. When using CDN, you cannot load the website with the root domain.

In the beginning, it wasn't easy. S3 was a little cumbersome when I started using it. With updates, it became easier to set up static websites. However, deploying dynamic websites in S3 is still difficult. You need to take notes on what you're doing so you can do the next dynamic website. 

The deployment is quite fast. You upload files, and that's it.

There a no license fees. E3 is a cloud service, and you pay as you go. Your encryption licenses are free, so you only pay for the storage you're using. It's extremely inexpensive. 

I rate Amazon S3 10 out of 10. S3 is highly cost-effective, so I would definitely recommend it.

Amazon S3 can be used for central storage, backup, log, and storage.

The reliability that Amazon S3 has provided has improved organizations.

Amazon S3 needs to simplify the backup features.

I have been using Amazon S3 for approximately 10 years.

Amazon S3 is a stable solution.

The scalability of Amazon S3 is good.

The support from Amazon S3 has been knowledgable and responsive.

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

The initial setup of Amazon S3 is easy, it can be done in less than one day.

We handle the implementation of Amazon S3. We have approximately 40 people that are able to do it.

It has been difficult for us to determine ROI.

The license of Amazon S3 is based on volume, capacity, and time. The overall price of the solution could improve. The support has to be added if you want it at an additional cost.

My advice to others is to pay attention to the backups and copies in Snapshots.

I rate Amazon S3 a seven out of ten.

We are using Amazon S3 for storage. This is a Cloud solution. We have developed a new application which has partly been released to the end customer, but not the complete solution. In the housing market, we have a lot of buying and they use the application to manage their lectures and receipts. This is what we are using Amazon S3 for the storage.

Amazon S3 can improve by decreasing the overall costs.

I have been using Amazon S3 for approximately one and a half years.

Amazon S3 is reliable.

We have not used Amazon S3 extensively, but the usage has been very high.

We have approximately 40 to 50 people using this solution. There might be an increased usage.

I have not contacted the technical support form Amazon S3.

I have not used other similar solutions to Amazon S3.

The implementation of Amazon S3 is done by a third party.

The price of Amazon S3 could be less expensive.

I rate Amazon S3 a nine out of ten.

Amazon S3 is our file storage solution. We use it for all of the backups of our storage and databases.

The most useful features of Amazon S3 are the intelligent multipart upload.

Amazon S3 could improve by being more secure.

I have been using Amazon S3 for approximately five years.

Amazon S3 is a stable solution.

I have found Amazon S3 very scalable, you can scale it on the fly and it is very easy to do.

Most all the cloud applications that are being used by our developer are using Amazon S3. More than 200 people are using this solution. At this moment we do not plan to increase usage.

I have used the support from Amazon S3 multiple times and they are good.

I have not used any other similar solution to  Amazon S3.

The initial setup of Amazon S3 is straightforward and the documentation is very good. You can do the setup of Amazon S3 in a few minutes.

We did the implementation ourselves.

The price of the Amazon S3 is low. The license model is based on what you use.

If users are looking for highly scalable, competent solutions, then Amazon S3 would be a good choice.

I rate Amazon S3 a nine out of ten.

I am managing the S3 storage solution from Amazon. From Microsoft, I'm managing the Azure administration. I handle that. As a part of that, I need to create the virtual machines, a point to site to VPN and Azure AD, AD synchronization with Windows server, a database server, mail server, and web server. I administrate all that.

We use Amazon S3 for storing files and documents on the cloud. I fill out the user whenever the files they use are downloaded. That is fully automated. After a few days, it can delete it. I've done the policy for the automated deletion.

Amazon S3 is great. We are using it for storage solutions.

Due to using S3, our data documents are safe and easy to access. It is better to keep them in the cloud as opposed to in our internal drive. You can access them from anywhere. Especially during the pandemic period, we are able to access remotely, as well. So it's good.

We are using the basic S3 bucket. It is easy to manage and easy to understand.

We need the mapping to Windows. That feature is needed in S3. That feature is in the Azure cloud where we can map it like a drive. We can map the cloud storage to the effort driving our Windows PC. But Amazon is not providing that feature for the S3 solution.

In the next release I would like to see mapping on the Windows machine. In Windows, there are drives right in volumes. We need to map these Amazon S3 storage to the Windows. That usually is available in the Azure. I would like to have that in the Amazon as well.

We have been using Amazon S3 for just six months as of now.

In terms of stability, it is good and has no issues.

We can scale Amazon S3 for storage. We can increase or scale up and we can scale down. It's easy to manage.

I'm happy where I'm at right now. If we need more storage, we will implement. We'll scale it up.

As of now, I haven't needed to contact support. It is really easy to manage. Even for the small issues, we can just Google the issues and find the solution. For complex issues, we may need to contact them, but as of now, I haven't needed to. I haven't faced any issues like that, so I didn't contact support. We have found that there is enough online documentation regarding S3.

We switched because of the security and scalability. It is highly secure because nobody can access it. Before we had solutions using an FTP and SFTP. That protocol is different and we are now using the S3. We need a shared key and an access secret key to access the particular storage. Without that, we cannot access. We cannot do anything. So security is more important. That's why we switched to Amazon S3.

The initial setup is simple and easy to manage.

It's not actually a deployment. It is a simple step. Within five minutes, we can deploy it.

Our implementation strategy for the solution is based on the user's document files and how much GB they want and how they want to access that particular story's solution. Based on that scenario, I create the S3 bucket on the cloud for the particular users - whoever wants to access that particular S3. I created that particular IM user, the user access for that particular storage. I make an access policy to that particular storage.

Our ROI is good based on our usage. We have multiple users who are accessing this S3 storage.

It's a monthly pricing.

We are happy with the pricing.

Amazon S3 is a great solution.

My advice is to have an implementation strategy based on the user usage.

On a scale of one to ten, I would give Amazon S3 an eight.

I am using Amazon S3 for storing all the organization data, which comes from a data pipeline.

The most valuable features of Amazon S3 are the accuracy and the life cycle policies, which helps when moving from Amazon S3 to Amazon Glacier.

Amazon S3 could improve some of the features, such as indexing, or we should have more information about all the data stored in a single place. This way we can see what data resides where instead of going in different buckets, file locations manually, or searching. An index would be nice, allowing us to directly go to a location to use the date.

I have used Amazon S3 within the last 12 months.

Amazon S3 is 99.99 percent stable. The solution is highly stable.

The scalability of Amazon S3 is good. If we want more storage we only need to pay extra.

All the workloads of the whole company go to Amazon S3. As our workloads increase, the data increases, and we will use more storage in Amazon S3.

I have not used the support from Amazon S3.

Positive

I have not used another solution similar to Amazon S3.

The initial setup of Amazon S3 is not complex. We are only using it for a storage layer and there were not any complexities.

The cost of Amazon S3 is good. The pricing model is based on the usage of the solution.

I would recommend this solution to others, it is one of the most used storage solutions.

I rate Amazon S3 a nine out of ten.

I use Amazon S3 mainly for daily backups of our database.

Amazon S3 has helped our organization because the daily backups can be done automatically with automation. We do not have to spend time on it and I am confident with Amazon S3 in its ability to recover our data.

Amazon S3 is easy to use and it is beneficial to use the CLI to make the backups. Since I use the CLI I do not have to do it on a web portal which is a big advantage because everything can be automatized. Automation can be done very well in Amazon S3.

The solution could improve by having a simpler way to have the detail size of a file in the CLI to be read or understood easier. Today, it's a little raw in the way the details are presented. You have to make some scripts and some modifications to be able to see the information properly of the size of a given bucket or the size of a file.

I have been using Amazon S3 for a long time. I used the latest version because the CLI is normally updated.

The stability of the Amazon S3 is good.

The scalability of Amazon S3 is great.

We are a small company and we have approximately five developers that use Amazon S3. We use the solution on a daily basis for hourly backups.

I have used the support from Amazon S3 a long time ago, I have not needed much help. When I did have contact with them there were times it took a while for a response.

I would rate the technical support of Amazon S3 a three out of five.

Positive

The main difference from other solutions I have used is Amazon is the leader, and it has a very large number of zones and capacity, while others can be smaller and can have different options. Not all the options that are available in Amazon S3 are offered by other competitors, but for the main features, most of them are working fine. I have been evaluating two different solutions, one from a French cloud-based company called Scaleway, and the other is peer-to-peer storage.

The installation was simple. Creating a new bucket and deploying it is very straightforward. To make the script deploy a new bucket takes approximately one hour. 

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

We did the implementation ourselves and we have two developers that do the maintenance of the solution.

The return on investment has been very good because the backups of our database are critical for our business to operate.

I would rate the return on investment of Amazon S3 a four out of five.

The price of the Amazon S3 is reasonable. There are not any licensing costs, they have a pay-as-you-use model. 

When backups are more than 6 months old, I would recommend keeping less of them and storing the remaining ones in Glacier (long-term, cheaper storage).

I have evaluated other options.

My advice to others is to separate the buckets project, not to put everything in the same bucket, and be sure to implement IAM rules to avoid problems between users and not to lose any backups. The implementation process is important. 

I rate Amazon S3 an eight out of ten.