[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-01。"],[],[],null,["# Quotas and limits\n\nThis document lists the quotas and limits that apply to\nVPC Service Controls. Quotas and limits specified in this document are subject to change.\n\nThe quota utilization computation is based on the sum of the utilization\nacross the enforced and the dry-run modes. For example, if a\nservice perimeter protects five resources in enforced mode\nand seven resources in dry-run mode, then the sum of both, which is 12, is tested\nagainst the corresponding limit. Also, each individual entry is counted as one\neven if it occurs elsewhere in the policy. For example, if a project is included\nin one regular perimeter and five bridge perimeters, all six instances are\ncounted and no deduplication is performed.\n\nHowever, VPC Service Controls calculates the service perimeter limits differently.\nFor more information, see the [Service perimeter limits](/vpc-service-controls/quotas#perimeter-limits)\nsection of this document.\n\nView quotas in the Google Cloud console\n---------------------------------------\n\n1. In the Google Cloud console navigation menu, click **Security** , and then\n click **VPC Service Controls**.\n\n [Go to VPC Service Controls](https://console.cloud.google.com/security/service-perimeter)\n2. If you are prompted, select your organization, folder, or project.\n\n3. On the **VPC Service Controls** page, select the access policy for which you want to view quotas.\n\n4. Click **View Quota**.\n\n The **Quota** page displays the usage metrics\n for the following [access policy](/access-context-manager/docs/scoped-policies) limits that\n apply cumulatively across all service perimeters in a given access policy:\n - Service perimeters\n - Protected resources\n - Access levels\n - Total ingress and egress attributes\n\nService perimeter limits\n------------------------\n\nThe following limit applies to each service perimeter configuration. That is,\nthis limit applies separately for the dry-run and enforced configurations of a\nperimeter:\n\n### Attribute limit considerations\n\nVPC Service Controls counts each entry in the following ingress and egress rule\nfields as one attribute:\n\nFor more information about these fields, see [Ingress rules reference](/vpc-service-controls/docs/ingress-egress-rules#ingress-rules-reference)\nand [Egress rules reference](/vpc-service-controls/docs/ingress-egress-rules#egress-rules-reference).\n\nVPC Service Controls considers the following rules to check if a perimeter exceeds\nthe attribute limit:\n\n- Each field in an ingress and egress rule can have multiple entries, and each\n entry counts towards the limit.\n\n For example, if you mention a service account and a user account in the `identities`\n field of an `egressFrom` rule block, VPC Service Controls counts two attributes\n towards the limit.\n- VPC Service Controls counts each occurrence of a resource in the rules separately,\n even if you repeat the same resource in multiple rules.\n\n For example, if you mention a project, `project-1`, in two different ingress or\n egress rules, `rule-1` and `rule-2`, VPC Service Controls counts two attributes\n towards the limit.\n- Each service perimeter can have an [enforced](/vpc-service-controls/docs/service-perimeters#enforced-mode)\n and a [dry run](/vpc-service-controls/docs/service-perimeters#dry-run-mode) configuration.\n VPC Service Controls applies the attribute limit separately for each configuration.\n\n For example, if the total attribute counts for the enforced and dry run configurations\n of a perimeter are 3,500 and 3,000 attributes, respectively, VPC Service Controls\n considers that the perimeter is still within the attribute limit.\n\nAccess policy limits\n--------------------\n\nThe following [access policy](/access-context-manager/docs/scoped-policies) limits\napply cumulatively across all service perimeters in a given access policy:\n\nThe following [access policy](/access-context-manager/docs/scoped-policies) limits\napply cumulatively across all access levels in a given access policy:\n\nOrganization limits\n-------------------\n\nThe following limits apply across all access policies in a given organization:\n\nAccess Context Manager quotas and limits\n----------------------------------------\n\nYou're also subject to the [Access Context Manager quotas and\nlimits](/access-context-manager/quotas#limits) because VPC Service Controls uses\nAccess Context Manager APIs."]]