Yoshiaki Sugimoto

@itinance It seems a running user permission issue. What is user running a command? and Does that user have a permission to execute add `iam` and `lambda` roles?

Refers to https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#putObject-property, `Tagging` or `Metadata` should be fine and it can declare at config.json

Currently I don't know why process fails on larger files. Could you try to set memory size in Lambda setting and run again?

Hmm, can I try to process that image which you failed? I guess that sum of processed image is larger than Lambda's memory setting, it might be failed.

@amacks Thank you for your PR. This seems useful for CF users, but those templates cannot change easily themselves. So in order to add this feature, I want to consider...

I think you can do it with a couple of ways: One is use fixed ACL setting in `config.json`. We have `ACL` configuration in all three of `backup` , `reduce`,...

Hi @scottybo I think it is difficult to decide the best combination of resizing and reducing by each image. However, this processor treats an image as `Buffer`, so you can...

I suspect that once script gets an image from S3, all resize/reduce is processed on the fly so any processing binary buffers will be allocated on that process, then some...

This project will work in single event to single configuration, so we won't switch its configuration by dealing image filename or someway. Probably you can do by following approach: -...

Yes, ImageMagick doesn't have to know. `ImageData.js` detects MIMEType from raw data using `image-type` package. If we do reduce after resize, Is there the resized image's raw data like `JPEG`...