Issues with AWS lambda proxy integration

Question

I have an AWS API Gateway endpoint that uses lambda proxy integration to retrieve data from an AWS RDS instance.

I use a yaml file to re-deploy the api, Once the API is re-deployed, The endpoint, illustrated above, throws an "Internal Server Error" every time I re-deploy the api.

The error goes off if I uncheck and then check the lambda proxy integration option/tick-box on the endpoint. This manual step is cumbersome and extremely unintuitive and can raise serious production issues.

Anyone facing similar issue know how to solve it without the additional "unchecking and checking" (manual) step? What change in YAML can solve this problem ?

Also check whether it still works if you change name of lambda in API gateway and again rename it to old one. — siraj pathan
I would expect that unchecking and rechecking is also setting or clearing some other field that is initially populatee incorrectly. — Michael - sqlbot

Prathamesh Jagtap Prathamesh Jagtap · Accepted Answer · 2018-05-17T15:35:25

Under your AWS::ApiGateway::Method resource, make your Integration.Type as AWS_PROXY

https://docs.aws.amazon.com/apigateway/api-reference/resource/integration/#type

Issues with AWS lambda proxy integration

1 Answers