-
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]: Removal of the Default route throttling for an API GatewayV2 sets the limits to 0 #30373
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
@davidg-idealo I can confirm, bit me last night 😂 |
Related issue. Including a different optional setting in your TF for an APIGW stage like e.g. include the following under
Effectively you get the following optional params set for "free" to 0 - which to me is unexpected and surprising and high impact as it cuts off the APIGW from any usage.
Note - there is a long thread on this over at #14742 and it does appear this is at least partially an issue on the AWS side (see https://stackref.substack.com/p/psa-aws-api-gateway-429-errors-and?s=r) However I would not expect that setting |
Would really appreciate this receive the attention it deserves. Having your API rate limited for seemingly no reason is not fun. |
The problem still exists. Updating Terraform Core version 1.2.0
|
Can confirm, suddenly being throttled to 0 is NOT fun, especially when you were expecting to just get better metrics |
Terraform Core Version
1.1.7
AWS Provider Version
4.61.0
Affected Resource(s)
aws_apigatewayv2_api
aws_apigatewayv2_stage
Expected Behavior
Before configuring the Default route throttling for an API-GW2 the Burst- and Rate limit is set to
Not configured
. This means that the account wide throttling limits are taken into account.After configuring these values and remove them again afterwards my exception would be that the values are set to the initial value
Not configured
.Actual Behavior
After removing the configuration for Default route throttling the values are set to 0.
The problem is that the underlaying API is immediately unavailable because the API GW responds with 429 - Too many requests.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Step 1:
Step 2:
Steps to Reproduce
First create an API-GW2 with default route limits. (Step1)
Afterwards remove the limits. (Step 2)
Check the limits and you will see that they are set to 0 and it is not possible to set them back to
Not configured
in the console.Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: