api gateway ratelimit problem.
See original GitHub issuek8s: v1.19.7 image: ambassador:1.12.4 installation: helm3 Follow the doc https://www.getambassador.io/docs/edge-stack/latest/howtos/rate-limiting-tutorial/
simple limit service deployed and running. when create the mapping:
---
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
name: service-backend
spec:
prefix: /backend/
service: quote
labels:
ambassador:
- request_label_group:
- x-ambassador-test-allow:
header: "x-ambassador-test-allow"
omit_if_not_present: true
ambassador pod report error, pod log:
could not validate the envoy configuration above after 5 retries, failed with error
[2021-04-23 06:10:45.637][117][info][main] [source/server/server.cc:555] runtime: layers:
- name: static_layer
static_layer:
envoy.deprecated_features:envoy.api.v2.route.HeaderMatcher.regex_match: true
envoy.deprecated_features:envoy.config.filter.http.ext_authz.v2.ExtAuthz.use_alpha: true
envoy.reloadable_features.ext_authz_http_service_enable_case_sensitive_string_matcher: false
envoy.deprecated_features:envoy.config.trace.v2.ZipkinConfig.HTTP_JSON_V1: true
envoy.deprecated_features:envoy.api.v2.route.RouteMatch.regex: true
[2021-04-23 06:10:45.637][117][info][config] [source/server/configuration_impl.cc:103] loading tracing configuration
[2021-04-23 06:10:45.637][117][info][config] [source/server/configuration_impl.cc:69] loading 0 static secret(s)
[2021-04-23 06:10:45.637][117][info][config] [source/server/configuration_impl.cc:75] loading 6 cluster(s)
[2021-04-23 06:10:45.638][117][info][config] [source/server/configuration_impl.cc:79] loading 1 listener(s)
[2021-04-23 06:10:45.643][117][critical][main] [source/server/config_validation/server.cc:60] error initializing configuration '/ambassador/snapshots/econf-tmp.json': Proto constraint validation failed (HttpConnectionManagerValidationError.RouteConfig: ["embedded message failed validation"] | caused by RouteConfigurationValidationError.VirtualHosts[i]: ["embedded message failed validation"] | caused by VirtualHostValidationError.Routes[i]: ["embedded message failed validation"] | caused by RouteValidationError.Route: ["embedded message failed validation"] | caused by RouteActionValidationError.RateLimits[i]: ["embedded message failed validation"] | caused by RateLimitValidationError.Actions[i]: ["embedded message failed validation"] | caused by ActionValidationError.GenericKey: ["embedded message failed validation"] | caused by GenericKeyValidationError.DescriptorValue: ["value length must be at least " '\x01' " bytes"]): stat_prefix: "ingress_http"
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Throttle API requests for better throughput - AWS Documentation
When request submissions exceed the steady-state request rate and burst limits, API Gateway begins to throttle requests. Clients may receive 429 Too Many ......
Read more >Part2: Rate Limiting for API gateways - Ambassador Labs
This article dives into the need for rate limiting with API gateways and how it can make your API more reliable. And we...
Read more >How precise is API Gateway throttling? | AWS re:Post
Our team has started to work with stage-based API Gateway throttling and noticed some irregular behavior. To prevent our system from being overrun...
Read more >Rate Limiting on AWS API Gateway: Beyond Usage Plans
Hence by default, API gateway can have 10,000 (RPS limit) x 29 (timeout limit) = 290,000 open connections. The 10,000 RPS is a...
Read more >Amazon API Gateway Hourly rate limit - Stack Overflow
The API Gateway throttling implementation currently purges keys which don't receive any requests/activity for more than 60 seconds. Thus, the slowest rate which ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Almost 1 year later, it still doesn’t work…
I also tested the RateLimitService with the latest and 2.0 versions and I can confirm that the functionality is not working. Any update on this?