"Not Configured" would not mean that rate limiting was not applicable for the API gateway. In the absence on any configuration the account level settings would take effect and that is the 10000 you see as the max value . Though it's kind of weird that you cannot set the value back to Not configured or null, I would assume setting it to the max permissible for the account would essentially (logically) mean the same as not have configured the value specifically and hence be bound by the account upper limits per region
Hello Carlos, thanks for the clear description. Currently, it's not possible to revert the change back to "not configured."
While you cannot "disable" the default route throttling, the workaround is to set it to account-level throttling rates, namely 5000/10000 respectively for burst/rate limit . This is identical to the "not configured" setting as this account-level throttling is implicitly enforced all the time.
How to change back throttling to "not configured" on HTTP API Gateway after configuring values on it.Accepted Answerasked 2 months ago
Client API throttling in API GatewayAccepted Answer
Is it possible to change the Amazon API Gateway 10 second timeout value?Accepted AnswerEXPERTasked 7 years ago
Client API Throttling in API GatewayAccepted Answer
Http API Gateway using stage variables on a private integrationasked a year ago
API Gateway - Gateway response - HTTP APIAccepted Answerasked 2 years ago
API Gateway HTTP + Lambda integration not enabling CORSasked 9 months ago
How precise is API Gateway throttling?Accepted Answerasked a year ago
Protect HTTP Api Gateway with WAFasked 8 months ago
Route Based throttling in a stage for HTTP endpoint of API Gateway via Cloudformationasked 9 months ago