AWS API Gateway : Execution failed due to configuration error: No match for output mapping and no default output mapping configured

Question

In AWS API Gateway, I have a GET method that invokes a lambda function.

When I test the method in the API Gateway dashboard, the lambda function executes successfully but API Gateway is not mapping the context.success() call to a 200 result despite having default mapping set to yes.

Instead I get this error:

Execution failed due to configuration error: No match for output mapping and no default output mapping configured

This is my Integration Response setup:

And this is my method response setup:

Basically I would expect the API Gateway to recognize the successful lambda execution and then map it by default to a 200 response but that doesn't happen.

Does anyone know why this isn't working?

Answer 1

I had the similar issue, got it resolved by adding the method response 200

Answer 2

I have same issue while uploading api using serverless framework. You can simply follow bellow steps which resolve my issue.

1- Navigate to aws api gateway
2- find your api and click on method(Post, Get, Any, etc)
3- click on method response
4- Add method with 200 response.
5- Save it & test

Answer 3

There was an issue when saving the default integration response mapping which has been resolved. The bug caused requests to API methods that were saved incorrectly to return a 500 error, the CloudWatch logs should contain:

Execution failed due to configuration error: 
No match for output mapping and no default output mapping configured. 

Since the 'ENABLE CORS' saves the default integration response, this issue also appeared in your scenario.

For more information, please refer to the AWS forums entry: https://forums.aws.amazon.com/thread.jspa?threadID=221197&tstart=0

Best,

Jurgen