This document covers the request quotas for the maximum number of requests that you can make to the OS Config API for the VM Manager suite of tools in a project. It also covers the allocation quotas for OS Config resources.
Google Cloud uses quotas to help ensure fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components. For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources.
The Cloud Quotas system does the following:
- Monitors your consumption of Google Cloud products and services
- Restricts your consumption of those resources
- Provides a means to request changes to the quota value
In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.
Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses.
Request quotas
When you use the Google Cloud CLI or the Google Cloud console, you are also making requests to the API and these requests count towards your request quota. If you use service accounts to access the API, that also counts towards your quota.
Quotas are enforced at intervals of every 60 seconds. That means that if you reach a specific limit anytime within 60 seconds, you need to wait for your quota bucket to refresh to make more requests.
Per user quotas
Quota group | Detail | Default quota |
---|---|---|
Read requests |
|
60 requests per user per minute |
Write requests |
|
60 requests per user per minute |
Lookup requests (Legacy beta) |
|
600 requests per user per minute |
Per region quotas
Quota group | Detail | Default quota |
---|---|---|
Read requests |
|
100 requests per region per minute |
Write requests |
|
60 requests per region per minute |
Allocation quotas
Allocation quotas are the maximum number of resources you can create of that resource type. OS Config resources include the following: patch deployments, OS policy assignments, and guest policies.
The following quotas don't reset over time and instead are released when you release the resource.
Resource | Detail | Default quota |
---|---|---|
Patch jobs |
|
100 patch jobs per project |
OS policy assignments |
|
20 OS policy assignments per zone per project |
Guest policies (Legacy beta) |
|
100 guest policies per project |
Manage request and allocation quotas
To manage the request and allocation quotas for your project, do the following:
- Follow the best practices for preserving API rate limits.
Use the Google Cloud console to view and edit request quotas:
- If you want to lower request quotas, see Capping usage.
- If you need higher request quotas than the default maximum, request a higher quota limit. In your request, add information showing the consumption rate in your environment. These include VM Manager audit logs or other error messages stating that the rate limit is exceeded. It's also useful to include information such as future growth plans, region or zone spread, and any additional requirements or dependencies.
What's next?
- Learn more about VM Manager
- Learn more about Service Quota Model.