-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[proposal] Add support for throttling per route #615
Comments
It might be good to mention that we could potentially attach the |
3 years later... any updates on this? Very useful feature |
4 years later... any updates on this? Very useful feature |
Would be awesome to have |
We are getting this when? |
5 years later... any updates on this? very useful feature |
6 years later.... i guess it never comes |
API Gateway has various forms of API throttling. This proposal adds support for throttling at the routing level. This allows you to specify a rate and burst limit per
@app.route
.Similar to CORS and authorizers, there will be a new param,
throttle
, that takes an instance ofThrottleConfig
:ThrottleConfig
accepts two arguments,rate
andburst
:The
rate
andburst
params map to the corresponding concepts described in the API Gateway throttling docsThe text was updated successfully, but these errors were encountered: