Throttling: Rate exceeded

When deploying multiple CDK stacks simultaneously, a throttling error occurs when trying to check the status of the stack. The CloudFormation runs just fine, but CDK returns an error because the rate limit was exceeded.

We’re using typescript.

The issue #1647 says that this error was resolved, but looking at the fix (#2053), it only increased the default number of retries, just making it less likely to happen.

Is there at least a way to override the base retryOptions in a CDK project? If there is, I can just override it in my side so the error does not occurs.

Even if there is, I think that this should be solved in the base project. I don’t think CDK should ever fail because of rate limiting while trying to check the stack status in CloudFormation, as it does not affect the end-result (the deployment of the stack).

Use Case

One of our applications have one CDK stack per customer (27 in total). When there’s an important fix that needs to be sent to every customer, we run the cdk deploy command for each stack, simultaneously, via a Jenkins pipeline.

Error Log

00:03:13   ❌  MyStackName failed: Throttling: Rate exceeded
00:03:13  Rate exceeded

[tobias-bardino]

We hit this issue regularly and it is getting really annoying 🤨

Last build 2 of 10 stacks failed with the “Throttling: Rate exceeded” error …a retrigger of the CICD pipeline will most likely succeed!

[phcyso]

Just to add another voice to this This is affecting my team as well.

In particular we have several CDK apps which creates over 100 stacks each If more then one of these apps are deploying at once time they fail with the rate exceeded message and just exit failing our CI build with no apparent retries.