there is an important notation to it: if you are keeping db connections in the global scope of the lambda function, it may be reused by a next lambda run; buuuut, depending the situation, it may be better to close connections when terminating lambda request.
I am facing kind of two, three different errors while I am adding path in api mapping (custom domain) there is no video on how to map apis with paths. If possible can you help
@@GokceDB “missing authentication token” I have not used any authentication for that api I feel it is bcz of endpoint mismatch. Also getting “Forbidden” and “Internal Server Error”
there is an important notation to it:
if you are keeping db connections in the global scope of the lambda function, it may be reused by a next lambda run; buuuut, depending the situation, it may be better to close connections when terminating lambda request.
❤️🔥❤️🔥 it really helped me
Great! :)
I am facing kind of two, three different errors while I am adding path in api mapping (custom domain) there is no video on how to map apis with paths. If possible can you help
What's the error message?
@@GokceDB “missing authentication token” I have not used any authentication for that api I feel it is bcz of endpoint mismatch. Also getting “Forbidden” and “Internal Server Error”
@@pateljemit5459 Can you paste the API Gateway logs here when you get the Internal Server Error? That usually has the root cause.