News for hackers. Stuff that matters.

A comment on Handling thousands of image upload per second with Amazon S3.

Re:Handling thousands of image upload per second with Amazon S3 by blowski on Sunday March 24, 2019 @06:37AM (#19475553)
The OP’s solution is the backend getting a pre-signed URL from S3 and giving it to the front-end, so the file doesn’t need to touch the back-end servers - it goes straight to S3.

This is what I do, and it works great, with one caveat: it tightly couples you to S3 (or at least a service that can give pre-signed URLs). That makes non-production workflows more complicated. So I’d recommend using it only if you’re uploading massive files (e.g. > 50MB) or lots of files where the extra hassle is worth it.

[ Parent | on HN ]
Re:Handling thousands of image upload per second with Amazon S3 by philliphaydon on Sunday March 24, 2019 @07:36AM (#19475748)
Why does it make non-production workflows difficult? You could do many things for non-production environment. Use a different bucket for development, abstract the generation of the url away so local development just uses another url to upload to yourself.
[ Parent | on HN ]