Even though i have increased timeout time to 50 sec but still failing at 29.31 sec with msg endpoint request timed out through api gateway postman.. How? How resolve that Thanks
A couple of things we can verify - 1) Increase the quota for the region where the APIs (Regional or Private) are deployed 2) using integration type that supports integration timeout increase 3) execution time, latency of backend
I didn't notice any defined max limit while requesting the quota increase. I am not sure which scenario you may require that large timeout. But you can try that. However, a large quota increase requires approval from AWS support.
![[New] Amazon #GuardDuty Malware Protection for #S3](http://i.ytimg.com/vi/Colh5QsNy7w/mqdefault.jpg)
Thank you so much, I desperately needed it for my project.
You're very welcome!
Thank you so much for this information. I have been struggling to get my application to work before it timeout. Thank you
Happy to help! Thanks for your feedback.
Thank you very much for the showcase! :)
Welcome!
Thanks a lot!
Welcome!
@@SrcCodes Hi, it seems like it doesn't work for the HTTP API Gateway. How can I increase it for this type?
Woww..
Thanks for update...looking for this only. Working
its working thankyou somuch for post this video
Thanks for confirming!
Thank you so much! Very useful video!!! :D
Thanks for your kind feedback!
Even though i have increased timeout time to 50 sec but still failing at 29.31 sec with msg endpoint request timed out through api gateway postman..
How? How resolve that
Thanks
Thanks brother.. Redeploying my api work... It's take some time to update.
Subscribed☺️
Make more videos like this
A couple of things we can verify - 1) Increase the quota for the region where the APIs (Regional or Private) are deployed 2) using integration type that supports integration timeout increase 3) execution time, latency of backend
Ohk.. great to hear that it is resolved. Thanks Raushan!
Hi
Is this increase covered in free tier?
Yes, I think so...
Can I raise it to 5 minutes?
I didn't notice any defined max limit while requesting the quota increase. I am not sure which scenario you may require that large timeout. But you can try that. However, a large quota increase requires approval from AWS support.