Aruba · Rate Limits

Aruba Rate Limits

Aruba (HPE Aruba Networking) APIs (Aruba Central, ClearPass, AOS-CX, EdgeConnect) implement per-cluster, per-account, and per-controller rate-limiting. Aruba Central documents a 1-second / 7-per-IP (token endpoint) limit and per-API quotas, but a single canonical public rate-limit table for the full Aruba API estate is not published; check each product's developer docs.

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

It captures 3 rate-limit definitions, measuring varies and concurrent_requests.

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

Tagged areas include Cloud, Network Management, Networking, SD-WAN, and Security.

3 Limits Throttle: 429
CloudNetwork ManagementNetworkingSD-WANSecurityWirelessRate Limiting

Limits

Aruba Central API (per-cluster) account/cluster
varies
per-product per-cluster quotas; see Aruba Central API rate limit docs
Aruba Central documents API rate limits per cluster and per token; consult the developer portal for the specific cluster.
ClearPass API appliance
varies
enforced per ClearPass appliance configuration
ClearPass rate-limiting is operator-configured on the appliance, not platform-imposed.
AOS-CX REST API (on-switch) switch
concurrent_requests
see AOS-CX REST API guide for the running firmware version
AOS-CX runs the API on the switch itself; concurrency and CPU pressure dominate over fixed per-second quotas.

Policies

Backoff Strategy
Honor Retry-After when present; use exponential backoff with jitter on 429.
Per-Product Variation
Each Aruba product (Central, ClearPass, AOS-CX, EdgeConnect, AirWave) enforces limits independently — implement per-product limit tracking rather than a single global budget.
Token Endpoint Throttling
OAuth/token endpoints in Aruba Central are aggressively rate-limited (low single-digit requests per second per IP); cache and reuse tokens within their TTL.

Sources