- 最新
- 最多得票
- 最多評論
Have you tried testing the lambda on its own. You can create a test event using the apigateway-api-proxy
or apigateway-http-api-proxy
templates depending on whether your API is a REST or HTTP API. You don't have to fill out all of the parameters listed in the template just the ones needed for the successful invocation of the function. You can print to stdout or stderr using print()
or the python logging library. You can then get some insight in the "Monitor" tab of the Lambda Console or look in CloudWatch for more details. Internal Server Error
indicates that the error is most likely happening in the Lambda function. I would only introduce the API Gateway in the troubleshooting only after confirming that the Lambda is working as expected.
Let me know if you have any other question or concerns.
相關內容
- 已提問 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
Wrong integration - duplicate old function name