CORS support

[onassar]

After deploying the stack, I'm trying to figure out how to enable CORS so that assets coming back from the Lambda function can be used in the Canvas element.

Would be helpful if a parameter could be defined so that when someone runs this template, they can choose YES or NO for adding CORS support.

[stevemorad]

Thanks for the feedback. Question for you on this. Would you like YES/NO to implement a wildcard for Access-Control-Allow-Origin; or YES/NO for CORS support, with an parameter to specify the Access-Control-Allow-Origin value (which could be either a wild card or specific URL)?

Is the CORS support use case for a single website or multiple websites?

[onassar]

For me, it was good enough to just specify the wildcard value for the header. Here's what I changed:

But maybe a YES/NO for CORS support, and then the parameter value (with a default value of *) would give people more control.

[stevemorad]

I have a test build with CORS support added. Would you test it and make sure it works for you?
https://s3.amazonaws.com/solutions-test-reference/serverless-image-handler/latest/serverless-image-handler.template

[onassar]

Works perfectly thanks!

[stevemorad]

Template and code updated with version 2.1, and also at the published site:
https://aws.amazon.com/answers/web-applications/serverless-image-handler/