Alternatively, use Filepicker.io.
filepicker.store(myFile, {location: "S3"}, function(FPFile){console.log("File stored in S3 at "+FPFile.key+" and available at "+FPFile.url);});
filepicker.store(myFile, {location: "S3"}, function(FPFile){console.log("File stored in S3 at "+FPFile.key+" and available at "+FPFile.url);});
Filepicker is awesome.
At my job I just had to implement direct to s3 uploads, and filepicker cut down the work by 10x. It's basically a one line implementation to save the contents of a file input to s3. That's awesome.
The pricing is extremely liberal, and the docs are good. I haven't used many of the more advanced features, but even at its simplest form it's an excellent tool.
As for the complaints here, they seem to be mostly pedantic - I would much rather concat a few strings to build the proper s3 URL when the alternative is building the whole upload infrastructure, and once again, that's without considering all the advanced features filepicker gives you.
This post was intended for the people who want to have a specific and stand-alone building block just for S3.
Just with their image manipulations were a bit more fully featured, like imagemagic
overall as someone who is currently using filepicker, i would recommend people avoid it if all you want to do is upload to files to your own bucket without any transformations like image resizing