Christoph Gysin

Does it work if you use the example command in the README? https://github.com/serverless/examples/tree/master/aws-node-fetch-file-and-store-in-s3#usage

This seems to be a quoting issue. According to a quick search, the default windows command prompt seems to have weird quoting behaviour. Maybe try powershell instead?

The stacktrace shows you where it fails: ``` "module.exports.save.fetch.then.then.response.then.buffer.then (/var/task/handler.js:9:3)" ``` Which is the line: ``` fetch(event.image_url) ``` So it seems that `image_url` is undefined, hence my assumption that the...

This is not the same issue. Please double check the example command in the README: https://github.com/serverless/examples/tree/master/aws-node-fetch-file-and-store-in-s3#usage

Why not have the client upload the file directly to S3? No need to pay for Lambda execution time just to forward a file to S3.

For uploading files, the best way would be to return a [pre-signed URL](http://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html), then have the client upload the file directly to S3. Otherwise you'll have to implement uploading the...

Uploading a file can be slow. If you upload through lambda, you will have to pay for lamda compute time while you are essentially just waiting for the data the...

You can create a database record when the signed URL is created, and then update it from a lambda triggered by an S3 event when the object has been created....

Yes, you could store the state of the upload (e.g. initiated/completed). The serverless approach often requires you to think asynchronously. The advantage is that you don't have to pay compute...

@vinyoliver As mentioned before, just store the state of the upload in your database. You could use Lambda, S3 triggers and DynamoDB TTL to implement a flow like: - client...