ARMO · Rate Limits

Armosec Rate Limits

ARMO does not publish fixed numeric rate limits for the ARMO Platform API. Access is gated by an account access key (X-API-KEY), and practical throughput is bounded by the size of your subscription (vCPU-based) and the scanning cadence of your connected clusters, registries, and repositories rather than by a documented per-minute request cap. Callers should implement retry with exponential backoff and honor 429 responses if throttled.

Armosec Rate Limits is the machine-readable rate-limit profile for ARMO on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, keys, and scans.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Kubernetes Security, Cloud Native Security, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Kubernetes SecurityCloud Native SecurityRate LimitingQuotas

Limits

Platform API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the ARMO Platform API.
Access Key Scope account
keys
per account
API calls require an Agent Access Key; keys are managed under Settings and via the Access Keys API.
Scan Cadence cluster
scans
configurable
Posture and image scans run on the operator's schedule; registry scans can be cron-scheduled via the API.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Regional Endpoints
Use the correct regional base URL (api.armosec.io for EU, api.us.armosec.io for US) for your tenant to avoid cross-region errors.

Sources