If you're running into throttling, I would suggest reaching out to your AWS account team to work with a solutions architect to dive in and understand your use case to ensure the right architecture. They can ensure that your call volume is expected, and propose alternatives (for example, spreading load across multiple AWS accounts, or using multiple regions).
If not what's the recommend way of proceeding when we get such exception, Wait before retry? any specific algorithm or wait times suggested that could help to mitigate this issue?
To directly answer this question, the recommendation is to use exponential backoff with jitter. You can learn more here: https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/
S3 Select from pre-signed URLs?Accepted Answerasked 4 years ago
ThrottlingException when requesting Appstream streaming urls
Can you configure AppStream to stream a specific application, rather than a desktop experience?Accepted Answerasked 2 years ago
Is there an extra fee for the use of signed URLs in S3?Accepted Answerasked 9 months ago
Error when requesting thing shadow - TOO_MANY_REQUESTSasked 4 months ago
Service Quota Automationasked 3 years ago
CloudFront Live Streaming - Active ViewersAccepted Answerasked 2 years ago
AWS Transcribe Streaming Dutch Supportasked 9 months ago
No streaming resources are available when connecting to an Appstream streaming url
Query HTTP Request Headers When Using Function URLs?Accepted Answerasked 3 months ago