1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
What is the backend for your APIs? Have you tested the backend directly (without going through API Gateway) and do they work fine? If your backend is a lambda function and it gives you the same error when run directly, then try increasing the memory allocated to the lambda function
If the backend endpoints all work fine, then I would test locally from the API Gateway AWS console next.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Well backend is .NET WebServices and it's working fine. These HTTP calls I am making from Lambda to API Gateway resource endpoints.If I directly test on API Gateway AWS console,that also correctly working.I am getting error only when I am trying to make HTTP calls from Lambda to API Gateway resource endpoints.Another thing I would like to highlight,Lambda is developed in GoLang.
I did some search on the net and found this article - http://bindersfullofcode.com/2019/02/16/golang-lambda-reuse.html
This may be the issue you are running into because of the way Go implements HTTP connections.