1 Answer
- Newest
- Most votes
- Most comments
4
The retry operation should be implemented on the client side, not on the API Gateway.
https://docs.aws.amazon.com/sdkref/latest/guide/feature-retry-behavior.html
Ensure that the client that executes the API reruns it when it receives a 503 error.
In such cases, if the program is reexecuted without an interval, the same error may occur again, so design the program to allow a small interval.
Relevant content
- asked a year ago
- asked 9 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Agreed, client side issue to retry. The max value of 30s cannot be changed: see https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html
Integration timeout 50 milliseconds - 29 seconds for all integration types, including Lambda, Lambda proxy, HTTP, HTTP proxy, and AWS integrations.
Check this post from the AWS Builders Library about retries, jitter, and exponential backoff. https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/?did=ba_card&trk=ba_card