Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can think of the Storage product as an upload server that sits in front of S3.

Generally, you would want to place an upload server to accept uploads from your customers, that is because you want to do some sort of file validation, access control or anything else once the file is uploaded. The nice thing is that we run Storage within the same AWS network, so the upload latency is as small as it can be.

In terms of serving files, we provide a CDN out-of-the-box for any files that you upload to Storage, minimising latencies geographically



> Generally, you would want to place an upload server to accept uploads from your customers

A common pattern on AWS is to not handle the upload on your own servers. Checks are made ahead of time, conditions baked into the signed URL, and processing is handled after the fact via bucket events.


That is also a common pattern I agree, both ways are fine if the upload server is optimised accordingly :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: