This article will briefly provide details about HCP's rate limit quotas and address a common error associated with the rate limit quotas.
When running API requests to HCP Vault, you may run into a similar error which relates to rate limit quotas:
hvac.exceptions.RateLimitExceeded: request path "transit/encrypt/designs":
rate limit quota exceeded, on post https://vault-cluster....
HashiCorp Cloud Platform offers Vault as a managed service. In order to ensure that the incoming requests aren't overwhelming system resources through consistent and high volume API requests (which could result in denial-of-service issues in some Vault nodes or even the entire Vault cluster), HCP imposes a rate limit quota on our resources.
The rate limit quotas are as follows:
DEVELOPMENT (extra small only)
- 1 node
- Request limit 60 requests/sec*
STARTER (small only)
- 3 nodes
- Request limit 200 requests/sec*
STANDARD (small, medium, large)
- Small - Request limit 400 requests/sec*
- Medium & Large - Request limit not implemented at this time*
*Initial limits, subject to change. Rates may be constrained by workload type and cluster resource availability and usage.
**Stay up to date with HCP changes by reviewing our change logs.
Please adjust your workflows to be within the rate limit quotas which are listed above.
If you are interested in or have additional questions about HashiCorp's Cloud Platform Offerings, please fill out this sales form (check the Vault option) and a Sales Representative will be assigned to you so that they may discuss the features more in depth.
For information on HCP pricing, please review our HCP Pricing page.