Known Issues

1. Service error (code 500) when invoking Lambda function from API Gateway

    Endpoint response body before transformations:
    {
      "Message": "An error occurred and the request cannot be processed.",
      "Type": "Service"
    }
   

   • By design, API Gateway maps 429 errors from Lambda to 500 responses. There is no way to map Lambda’s 429 to any status code. It will always be considered as 500. See this post.
   • And it is possible to have a 200 code returned for certain function errors. See this documentation.

2. CloudWatch Event Rules

   • When creating a Event Rule with CloudFormation, it somehow changes the digital value (e.g. exitCode: 1) in EventPattern to exitCode: '1'.
   • You need to manually change the value back from '1' to 1 from the Console.
   • Then when you update the CloudFormation stack later, the value will not get changed back to '1'.