1 Answer
- Newest
- Most votes
- Most comments
2
Hi,
Look at this thread on StackOverflow: it provides some answers (issued by AWS Support) to CodePipeline throttling: mostly due to too many API calls.
Best,
Didier
Relevant content
- asked 3 years ago
Hi,
Look at this thread on StackOverflow: it provides some answers (issued by AWS Support) to CodePipeline throttling: mostly due to too many API calls.
Best,
Didier
Thank you for providing the link to the Stack Overflow thread regarding the ThrottlingException. Although the thread specifically discusses the CodeDeploy API and not the CodePipeline API, it's valuable information since AWS Support mentions that rate limits are variable and dynamic, thus not documented.
Given this, we can infer that similar considerations may apply to AWS CodePipeline. As recommended by AWS Support, implementing retries with exponential backoff is a good practice when encountering ThrottlingException errors. This approach helps manage API calls more effectively by spacing out retries and reducing the likelihood of overwhelming the service.
Thank you again for the helpful insights!
Hi Rafael, yes: throttling management in code is a good universal practice: I currently do it heavily with Bedrock when GenAI resources are constrained. Thanks for accepting my answer!