Joey van Dijk 660e0b3a8f Support "Task timed out" warnings as HTTP 504-errors
Currently if Lambda functions have a timeout then you will not see any errors in Cloudwatch, while the user gets a 200 http response code with `{ errorMessage: 'Task timed out in 10.0 s'}`. 

This change will show 5XX errors in Cloudwatch.

To support this I need to copy all the default patterns in `serverless.yml` per function, so therefore I think this need to be a default setting, while this is not caused by the Serverless(/our) code but by AWS Lambda itself.
2017-06-08 10:36:36 +02:00
..
2017-04-10 10:12:27 +02:00
2017-03-23 12:29:07 +01:00
2017-04-27 11:20:50 +02:00
2017-06-01 14:35:21 +02:00
2017-03-23 12:29:07 +01:00
2017-05-29 13:50:03 +02:00
2017-03-23 12:40:49 +01:00
2017-05-17 12:46:46 +02:00