- 最新
- 投票最多
- 评论最多
Hi,
"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
--Syd
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 [1]. This is identical to the "not configured" setting as this account-level throttling is implicitly enforced all the time.
Thanks so much! Seems it is the only workaround possible. Maybe in the future.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
Thanks for your help in that. Yes it seems it is the only way to make it happen but I wanted to see if we get a different approach to this question. Thank you!!