-
Notifications
You must be signed in to change notification settings - Fork 25
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
Feature Request: Rate Limiting #107
Comments
Hi @shubharao, I've noticed that this feature request has been accepted but it's not in the roadmap project --> https://github.com/aws/aws-app-mesh-roadmap/projects/1 Any ideas of when you guys will start working on ti? |
Hey @isaac-mj , fixed that. It is on our roadmap, but we're not actively working on it at the moment. Is this one of interest to you? Have any requirements or thoughts you could share on what you'd want if so? :) |
When using Virtual Gateway as the Ingress, having API rate limiting is a very natural requirement since it's not fulfilled by NLB/ALB either. I really don't want to integrate WAF for the purpose, since in many cases calls come from internal services residing in another data centre or cloud provider. |
I am also interested in this. I will probably be potentially implementing this in the coming months. Is there any way to inject arbitrary envoy config into appMesh config? I see something like that for stats and tracing, but nothing else. Thanks |
We are also not interested in rate limiting. |
+1 |
@koresar, App Mesh does not configure any rate limitation for Envoy proxies, at does not allow for custom configuration of rate limiting at the moment. Please open a support case with the details of your environment / configuration and error logs, so our team can look into it. |
Thanks @herrhound |
+1 - Would be fantastic if this was added! |
+1, this would be cool! |
+1 - much needed feature and other service mesh alternatives like Istio already support it. |
+1 - any updates on this? |
Tell us about your request
App Mesh should support the ability to configure rate limiting for requests coming into or out of a Virtual Node. This could be enabled by using Envoy Proxy's Global Rate Limiting. With this setting, customers could define thresholds for how many transactions (i.e. requests) per time period to allow from a given caller before throttling further traffic.
This is similar to #6 (Circuit Breaker Policy) but solves additional use cases depending on the traffic characteristics being handled by the service.
Which integration(s) is this request for?
All
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
The text was updated successfully, but these errors were encountered: