Amazon Simple Storage Service (S3)の評判・口コミ 全64件

What do you dislike?

Generating time-sensitive URLs is harder than it ought to be, although this is pretty quickly overcome using a plugin.

What do you like best?

High reliability in terms of availability and uptime, which is essential.

It is easy to use, both standalone and to integrate with other applications.

Multiple different security options and configurations make it easy to create areas and files which are publicly accessible, as well as ones which can only be accessed either by specific people / groups, or for specific windows of time. This makes it idea both for general storage, and also for the sharing of more private information.

My greatest use of S3 is for podcast storage/serving, and for integration with my Wordpress-based sites.

It works very well in both cases - you can make use of their feature - rich API, or of the plethora of plugins available.

Recommendations to others considering the product

Remember that S3 data are not owned by you, so make sure you keep your own local copy of all data just in case of any issues or data loss!

Take a little time upfront to map out your intended data structures, as it is harder to rearrange later.

What do you dislike?

The software to management of it is not quite easy to use and the administration to create folders isn't so friendly.

What do you like best?

Easy way to store large data files to process it.'

Recommendations to others considering the product

Usefull to store large data files, tested up to 5GB.

What do you dislike?

The pricing can be very complicated to figure out, and the documentation can be a bit intimidating.

What do you like best?

The ease of use of the service and the uptime of it which is really 2nd to none.

What do you dislike?

In my opinion, it's quite difficult to have a quick overview on public objects inside a private bucket. Let me explain: S3 buckets have a default ACL (private or public), but single objects can override it, so you can have public objects on private buckets. When a bucket contains a lot of objects (from hundred thousands to millions) it's tricky to check if - for any reason (ie. mistake, software bug, ...) - there are public objects in private buckets. This should be improved.

What do you like best?

S3 is a "infinite scaling" key-value store for textual and binary data. It's not a database (doesn't provide features and latency of a DB), but more like a distributed file system where you can store large data and access it via an HTTP interface (or the AWS console, the API or cli), designed to be store and retrieve data reliably.

What I love the most? It works. It's probably one of the most solid AWS products (thanks also to the facts of being the oldest one, if I'm not mistaken). Over the time, AWS introduced many great features, like the ability to host static websites on S3, fine-granted access control, access logs, and so on. All features are very useful if you start building products on top of it.

Recommendations to others considering the product

I strongly recommend S3.