Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(core): Rate limit errors deploying CloudWatch Log groups #807

Open
ddneilson opened this issue Sep 9, 2022 · 0 comments
Open

(core): Rate limit errors deploying CloudWatch Log groups #807

ddneilson opened this issue Sep 9, 2022 · 0 comments
Labels
bug This issue is a bug.

Comments

@ddneilson
Copy link
Contributor

ddneilson commented Sep 9, 2022

When the RFDK creates a CloudWatch Log group it does it via the CDK's LogRetention construct. The CloudWatch Logs APIs that the LogRetention construct calls have a very low TPS limit (5 TPS). The result is that when deploying multiple RFDK constructs one can encounter rate limit errors in the deployment -- this is particularly seen, randomly, with the RFDK's integration tests.

CDK's LogRetention construct provides a way to configure the Javascript SDK that it's using to make the CloudWatch API calls. Using this, the RFDK should set higher max retries and retry delay.

Specifically, the RFDK should set the logRetentionRetryOptions option in these two places:

  1. new LogRetention(scope, logWrapperId, {
  2. const logRetention = new LogRetention(this, 'LogRetention', {

Probably go for something really high for maxRetries (20?) and a delay base of 1s.

edit: The same option exists on Lambda Function constructs, and should be set there as well.


This is 🐛 Bug Report

@ddneilson ddneilson added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. and removed needs-triage This issue or PR still needs to be triaged. labels Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

1 participant