Implement ECR API retry/backoff logic when throttling is detected

Hello,

We have been running into throttling limits with AWS ECR, and AWS has requested that we do the following:

Implement a retry exception or exponential backoff on the API calls that you suspect that you are being throttled.

Since the majority of our ECR usage is due to concourse (many of our custom resources are hosted there, as well as the final build artifacts from our pipelines), we don't have much control over this behavior. AWS has requested that we implement the above before they will increase our API limits.

Is it possible to introduce some sort of retry logic with increasing wait timers when the throttling errors are detected? It seems like a 400 status with a specific message about throttling is returned from the API. Here is a sample error we found in another tool we use (image and tag removed):

Failed to query image details "<image>" "<tag>" ThrottlingException: Rate exceeded
status code: 400

Start by locating the AWS ECR API calls responsible for querying image details and inspect how throttling errors with status 400 and the message "Rate exceeded" are handled. Define the retry and increasing-wait behavior for the affected calls, then verify that throttled requests eventually recover without changing normal error handling.