Quotas and limits

This document lists the quotas and limits that apply to Infrastructure Manager.

Infra Manager is subject to the Cloud Build quotas and limits and to the Cloud Storage quotas and limits.

For information about quota validation for resources provisioned using Infra Manager, see quota validation of provisioned 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.

There are also limits on Infra Manager resources. These limits are unrelated to the quota system. Limits cannot be changed unless otherwise stated.

Allocation quotas

The following quotas don't reset over time and instead are released when you release the resource:

Quotas	Value
Deployments per project per region	1,000
Previews per project per region	1,000

Request quotas

The following quotas apply to Infra Manager requests:

Quota	Value
Mutating requests per minute per project per region	20
Number of API requests per minute per project per region	1,200

Usage limits

Infra Manager enforces the following usage limits:

Usage limit	Value
Number of Terraform input variables	50
Number of resources returned when listing resources	500
Length of identifiers in characters	40
Size of the API payload in bytes	9,500
Number of the historical revisions	100

Caution: The API payload limit is inclusive of metadata associated with your API payload. To avoid exceeding your API payload limits, ensure that the size of your payload is less than 9,500 bytes.

Request a quota increase

To increase or decrease most quotas, use the Google Cloud console. For more information, see Request a higher quota.

Quota validation of provisioned resources

Infra Manager provisions Google Cloud resources. These resources have their own quotas and limitations. For example, Virtual Private Cloud has its own quotas and limitations.

You can enable quota validation when using Infra Manager to create or update a deployment to ensure that the infrastructure outlined using your Terraform configuration doesn't exceed your quota values.

Infra Manager uses the quota-validation flag to determine whether to validate the resources outlined in your Terraform configuration as part of the gcloud infra-manager deployments apply command. When the quota-validation flag is in use, Infra Manager either logs when a deployment exceeds quota values (ENABLED), or prevents the deployment altogether (ENFORCED).

Infra Manager quota values are assessed for only the following Google Cloud resource types:

• google_compute_network
• google_compute_disk
• google_compute_instance

For more information about how to use quota validation with Infra Manager, see deploy resources, or update a deployment.

Cloud Build quotas and limits implications

Infra Manager uses Cloud Build to create and update deployments. As part of the deployment and update process, Infra Manager checks the status of the deployments using Cloud Build approximately 12 times per minute.

Cloud Build API rate limits affect the rate at which you can call the Cloud Build API. If you are running several deployments concurrently (for example, across multiple regions or environments), check the Cloud Build API rate limits for your organization to ensure that the number of your Cloud Build operation requests are within your API rate limits. You can view and edit your API rate limits by going to the Quotas console page.

Caution: You may experience deployment errors if the number of deployments you are running concurrently exceeds the API rate limits for your organization. To workaround Infra Manager deployment errors with your API rate limits, you should serialize your deployments or logically separate deployments into separate projects.