Quotas and limits

This document lists the quotas and system limits that apply to VPC Service Controls. Quotas and limits specified in this document are subject to change.

VPC Service Controls and Access Context Manager quota enforcement is integrated with Cloud Quotas.

The quota utilization computation is based on the sum of the utilization across the enforced and the dry-run modes. For example, if a service perimeter protects five resources in enforced mode and seven resources in dry-run mode, then the sum of both, which is 12, is tested against the corresponding limit. Also, each individual entry is counted as one even if it occurs elsewhere in the policy. For example, if a project is included in one regular perimeter and five bridge perimeters, all six instances are counted and no deduplication is performed.

However, VPC Service Controls calculates the service perimeter limits differently. For more information, see the Service perimeter limits section of this document.

View quotas in the Google Cloud console

You can view your VPC Service Controls quota utilization and system limits directly on the VPC Service Controls page or through the centralized Quotas & System Limits page in the Google Cloud console.

View quotas in the VPC Service Controls console

  1. In the Google Cloud console, go to the VPC Service Controls page.

    Go to VPC Service Controls

  2. If you are prompted, select your organization, folder, or project.

  3. On the VPC Service Controls page, select the access policy that you want to view quotas for.

  4. Click View Quota.

    The Quota page displays the usage metrics for the following scoped access policy limits that apply cumulatively across all service perimeters in a given access policy:

    • Service perimeters
    • Protected resources
    • Access levels
    • Total ingress and egress attributes

View quotas in Cloud Quotas

To view organization-level VPC Service Controls quotas and system limits across all access policies in the standard Google Cloud console Quotas & System Limits dashboard, do the following:

  1. In the Google Cloud console navigation menu, click IAM & Admin, and then click Quotas & System Limits.

    Go to Quotas & System Limits

  2. Select your organization in the resource picker.

  3. To inspect effective limits and current utilization, filter by service name accesscontextmanager.googleapis.com.

You can also query quota metrics programmatically using the Cloud Quotas API.

Service perimeter limits

The following limit applies to each service perimeter configuration. Unlike the cumulative quotas described previously, this limit applies separately for the dry-run and enforced configurations of a perimeter.

Type Limit Notes
Attributes 6,000 This limit applies to the total number of attributes specified in the ingress and egress rules. The attribute limit includes the references to projects, VPC networks, access levels, method selectors, identities, and roles in these rules. The total attribute count also includes the use of wildcard characters, *, in the methods, services, and project attributes.
Private Service Connect endpoints 500 This limit applies to the total number of Private Service Connect endpoints you can specify across all ingress and egress rules in a single service perimeter.

Attribute limit considerations

VPC Service Controls counts each entry in the following ingress and egress rule fields as one attribute:

Rule block Fields
ingressFrom
  • sources
  • identities
ingressTo
  • resources
  • methodSelectors
  • roles
egressFrom
  • sources
  • identities
egressTo
  • resources
  • methodSelectors
  • externalResources
  • roles

For more information about these fields, see Ingress rules reference and Egress rules reference.

VPC Service Controls considers the following rules to check if a perimeter exceeds the attribute limit:

  • Each field in an ingress and egress rule can have multiple entries, and each entry counts towards the limit.

    For example, if you mention a service account and a user account in the identities field of an egressFrom rule block, VPC Service Controls counts two attributes towards the limit.

  • VPC Service Controls counts each occurrence of a resource in the rules separately, even if you repeat the same resource in multiple rules.

    For example, if you mention a project, project-1, in two different ingress or egress rules, rule-1 and rule-2, VPC Service Controls counts two attributes towards the limit.

  • Each service perimeter can have an enforced and a dry run configuration. VPC Service Controls applies the attribute limit separately for each configuration.

    For example, if the total attribute counts for the enforced and dry run configurations of a perimeter are 3,500 and 3,000 attributes, respectively, VPC Service Controls considers that the perimeter is still within the attribute limit.

Access policy limits

The following access policy limits apply cumulatively across all service perimeters in a given access policy:

Type Limit Notes
Service perimeters 10,000 Service perimeter bridges count towards this limit.
Protected resources 40,000 Projects that are only referenced in ingress and egress policies don't count towards this limit. Add protected resources to a policy only in batches of 10,000 resources or fewer to prevent policy modification requests from timing out. We recommend that you wait 30 seconds before making the next policy modification.
Identity groups 1,000 This limit is on the count of identity groups configured in the ingress and egress rules.
Agent identities 1,000 This limit is on the count of agent identities configured in the ingress and egress rules.
Deleted identities (Preview) 500 This limit applies to the number of deleted identities configured in the access policy.
Workload Identity Federation for GKE (Preview) 1,000 The maximum number of Workload Identity Federation for GKE principals that you can configure across ingress and egress rules.
VPC networks 500 This limit is on the count of VPC networks referenced in the enforced mode, dry-run mode, and ingress rules.
Total character length of all rule titles 240,000 The combined length of all ingress and egress rule titles must not exceed this limit. Whitespace characters in the rule titles also count toward this limit. However, any rule for which you haven't provided a title doesn't count toward this limit.

The following access policy limits apply cumulatively across all access levels in a given access policy:

Type Limit Notes
VPC networks 500 This limit is on the count of VPC networks referenced in access levels.

Organization limits

The following limits apply across all access policies in a given organization:

Type Limit
Organization-level access policy 1
Folder and project-scoped access policies 50

Request quota increases

Most quotas and system limits specified on this page are fixed platform constraints designed to ensure system scalability and availability.

Only the Protected resources quota per access policy is eligible for an increase. To request an increase for protected resources:

  1. Check your current quota usage in the Google Cloud console and confirm that your access policy is close to the 40,000 resource limit.
  2. Create a case with Google Cloud Support.

  3. Provide a clear business justification. Valid justifications include that it's required for projected resource growth and specific architecture requirements. A detailed justification is strictly required.

Requests generally take 2 to 3 weeks to process and require manual review and approval by Google Cloud Support and engineering teams.

Access Context Manager quotas and limits

You're also subject to the Access Context Manager quotas and limits because VPC Service Controls uses Access Context Manager APIs.