Aqua Security · Rate Limits
Aqua Security Rate Limits
Aqua Security does not publish concrete rate-limit numbers, throttling thresholds, or response-header conventions. This artifact records the gap; see notes for research findings.
Aqua Security Rate Limits is the machine-readable rate-limit profile for Aqua Security on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition, measuring varies.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Cloud Native, Containers, Kubernetes, Runtime Protection, and Security.
1 Limits
Throttle: 429
Cloud NativeContainersKubernetesRuntime ProtectionSecurityVulnerability ScanningRate LimitingQuotasThrottling
Limits
Per-contract limits account
see provider integration agreement
No public rate-limit numbers; throughput is governed by individual customer or partner contracts.
Policies
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header that may be returned, even though the provider does not publish formal retry semantics.
Contract-Scoped Limits
Quotas, burst, and concurrency ceilings are governed by the individual customer or partner contract rather than a public policy. Coordinate with the provider to confirm thresholds before scaling traffic.
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.