Lambda function triggered by API Gateway and Lambda tests, but not by POST request to API Gateway domain name.

Question

I have a Lambda function that is set up to be triggered via API Gateway. When I test from AWS Lambda, the function executes correctly. When I test from API Gateway, the function executes just fine. However, when I attempt to post to the custom domain name I set up in API Gateway, I get a 500. Additionally, the function does not put any logs to CloudWatch, which leads me to believe it's not being invoked. I have a trigger set up with API Gateway to invoke the function, so I'm not sure why it's not being invoked.
![API Gateway Trigger](/media/postImages/original/IMpOxxibFST6WmlvIAH28Fuw)
![API Gateway Test](/media/postImages/original/IMMMLiLFzpSniKb8of3gTO_w)
![Lambda Test](/media/postImages/original/IMdvhM966bRP6cfU74-HQi2Q)
![Error Message](/media/postImages/original/IM0D8qmIpdTDqfAsKz3_BjLQ)

Didier Durand · Accepted Answer

Hi,

You have the explanations re. CORS issues (see you error message) and API Gateway in this page: see https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-cors.html

```
If it is a POST method request, it must include an Origin header.
```

So, you probably need to add this header in your request when you POST to the API Gateway,

This post shows how to configure CORS from console: https://medium.com/geekculture/simple-steps-to-enable-cors-in-api-gateway-through-console-cloud-formation-c09d9df31c07

Best,

Didier

Lambda function triggered by API Gateway and Lambda tests, but not by POST request to API Gateway domain name.

Añade tu respuesta

Contenido relevante