-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: DescribeOrganizationConfigRules, failed to get rate limit token, retry quota exceeded #36094
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
@damianarata Thanks for raising this issue 👏. |
This functionality has been released in v5.42.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.7.4
AWS Provider Version
5.39.1
Affected Resource(s)
resource "aws_config_organization_managed_rule" "alb_waf_enabled" { name = "alb_waf_enabled" rule_identifier = "ALB_WAF_ENABLED" resource_types_scope = [ "AWS::ElasticLoadBalancingV2::LoadBalancer", ] }
Expected Behavior
It should try to create the resource or validate the current status.
Actual Behavior
When I try to run the plan I get this error message:
│ Error: reading ConfigService Organization Managed Rule (ALB_WAF_ENABLED): operation error Config Service: DescribeOrganizationConfigRules, failed to get rate limit token, retry quota exceeded, 3 available, 5 requested
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
From my security perspective will not provide my log because of the confidential information. It is easy to reproduce creating the aws_config_organization_managed_rule resource.
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: