Account Tiers
Default Quotas
Configuration Rules
When configuring CPU and memory, your configuration must meet the following requirements:- vCPU must not exceed the maximum vCPU limit for your account tier.
- Memory must not exceed the maximum memory limit for your account tier.
- vCPU must be configured as an integer value, such as 1, 2, 4, or 8 vCPU.
- Memory must be configured in 512 MiB increments.
- Memory must be within the allowed range of 0.5-4 GiB per vCPU.
- 1 vCPU supports 512 MiB to 4 GiB of memory.
- 2 vCPU supports 1 GiB to 8 GiB of memory.
- 4 vCPU can support up to 16 GiB of memory based on the memory-per-vCPU range, but the actual available memory is still limited by the maximum memory quota of your account tier.
Check Current Quota Usage
Use the quota API to check the quota limits available to your account and the resources currently in use. This is useful before launching a large batch of sandboxes or when troubleshooting quota-related launch failures.Check quota usage using the SDKs
Quota response fields
The quota response includeslimit and usage objects.
Quota usage is intended for capacity planning and troubleshooting. Usage data may have a short delay, depending on the backend resource reporting path.
Notes
- If your resource configuration exceeds the quota for your account tier, the request will fail.
- If a region has no available capacity, sandbox creation may fail with a quota or rate-limit related error even when your account-level quota has not been fully used.
- Choose CPU and memory based on your workload requirements to avoid out-of-memory errors or unnecessary resource usage.
- Enterprise quotas can be customized based on your requirements. To request a quota increase, please contact our support team.