Amazon S3 is a cloud-based object storage service from Amazon Web Services. It's key features are storage management and monitoring, access management and security, data querying, and data transfer.
N/A
Azure Blob Storage
Score 8.5 out of 10
N/A
Microsoft's Blob Storage system on Azure is designed to make unstructured data available to customers anywhere through REST-based object storage.
I think [Amazon S3 (Simple Storage Service)] is cheaper than Azure Blob Storage (at least at the time I selected it). It is a low maintenance product and it is more reliable.
All other alternatives are also good but as our infrastructure was on AWS, Amazon S3 (Simple Storage Service) was a better choice due to its better integration with other AWS services. It was serving the purpose in an economical way. All of our needs were being fulfilled by …
We are an AWS shop, thus it is much easier to use with other AWS services. It may not always be the cheapest but once you are in AWS if you can decouple your apps and use this as one of your services it will certainly make developer's life easier and admin life easier.
We had already decided to use Amazon S3 (Simple Storage Service) for other compute services, so it made sense to use Amazon for blob storage as well. By using the same cloud vendor, we can more easily integrate between AWS services like Cloudfront. Blob storage is essentially a …
Amazon S3 provides a variety of tools for uploading short and large objects to the cloud. AWS S3 is a key-value store, one of the major categories of NoSQL databases used for accumulating voluminous, mutating, unstructured, or semistructured data. S3 object retrieval is fast. …
They're both great. I really don't know the differences, but both have the same basic set of features, in my opinion. But, S3 is widely know as a greater tool, safer, and much easier. Also, it's used by and compatible with a lot of applications around the world. That made us …
Azure Blob Storage was used only because we were already using it for other projects, and it has a good reputation for being a reliable cloud provider. It also has widespread regional availability and allows for data replication. It can also be easily accessed via the API or by …
Azure Blob Storage is the best choice to store files when the app runs in Azure. It also has some advantages over S3, like Shared Access Signatures, that make it easy to control access to files directly via a URL. Azure Blob Storage is very fast and we have not had any major …
S3 seemed to be just as functional as blob storage in our analysis. The only real difference is we already were on the Microsoft platform with 365, and it was an easy system to continue to learn. That was the only real deciding factor between the two that made any difference …
Amazon S3 is a great service to safely backup your data where redundancy is guaranteed and the cost is fair. We use Amazon S3 for data that we backup and hope we never need to access but in the case of a catastrophic or even small slip of the finger with the delete command we know our data and our client's data is safely backed up by Amazon S3. Transferring data into Amazon S3 is free but transferring data out has an associated, albeit low, cost per GB. This needs to be kept in mind if you plan on transferring out a lot of data frequently. There may be other cost effective options although Amazon S3 prices are really low per GB. Transferring 150TB would cost approximately $50 per month.
Azure Blob Storage is well suited for cases where you are working with different data formats and looking for cost-effective storage solutions based on access frequency. Another area of strength is the encryption of data at rest, and encryption can be managed on your own. However, it may not be appropriate for transferring large data very fast.
Fantastic developer API, including AWS command line and library utilities.
Strong integration with the AWS ecosystem, especially with regards to access permissions.
It's astoundingly stable- you can trust it'll stay online and available for anywhere in the world.
Its static website hosting feature is a hidden gem-- it provides perhaps the cheapest, most stable, most high-performing static web hosting available in PaaS.
Web console can be very confusing and challenging to use, especially for new users
Bucket policies are very flexible, but the composability of the security rules can be very confusing to get right, often leading to security rules in use on buckets other than what you believe they are
It is tricky to get it all set up correctly with policies and getting the IAM settings right. There is also a lot of lifecycle config you can do in terms of moving data to cold/glacier storage. It is also not to be confused with being a OneDrive or SharePoint replacement, they each have their own place in our environment, and S3 is used more by the IT team and accessed by our PHP applications. It is not necessarily used by an average everyday user for storing their pictures or documents, etc.
AWS has always been quick to resolve any support ticket raised. S3 is no exception. We have only ever used it once to get a clarification regarding the costs involved when data is transferred between S3 and other AWS services or the public internet. We got a response from AWS support team within a day.
Documentation sometimes appears to be out of date or not fully documented properly with new releases. It is like documentation comes out for a specific version and is quickly out of date. Another issue is documentation is scarce on new releases and only seems to get properly updated (and sometimes is still wrong) once enough people hit the forums to complain.
Overall, we found that Amazon S3 provided a lot of backend features Google Cloud Storage (GCS) simply couldn't compare to. GCS was way more expensive and really did not live up to it. In terms of setup, Google Cloud Storage may have Amazon S3 beat, however, as it is more of a pseudo advanced version of Google Drive, that was not a hard feat for it to achieve. Overall, evaluating GCS, in comparison to S3, was an utter disappointment.
Azure Blob Storage is the best choice to store files when the app runs in Azure. It also has some advantages over S3, like Shared Access Signatures, that make it easy to control access to files directly via a URL. Azure Blob Storage is very fast and we have not had any major issues with it after using it for several years.
It practically eliminated some real heavy storage servers from our premises and reduced maintenance cost.
The excellent durability and reliability make sure the return of money you invested in.
If the objects which are not active or stale, one needs to remove them. Those objects keep adding cost to each billing cycle. If you are handling a really big infrastructure, sometimes this creates quite a huge bill for preserving un-necessary objects/documents.