本页面上的部分或全部信息可能不适用于 Trusted Cloud by S3NS。
配额和限制
本文档列出了适用于 VPC Service Controls 的配额和限制。本主题中指定的配额和限制随时可能更改。
配额利用率计算是基于强制模式和模拟运行模式的利用率总和。例如,如果服务边界在实施模式下保护五个资源,在试运行模式下保护七个资源,则系统会根据相应的限制对两者的总和(即 12 个)进行测试。此外,每个条目计为一个,即使该条目出现在政策的其他位置也是如此。例如,如果项目包含在一个常规边界和五个网桥边界内,则系统会计算所有六个实例,并且不会执行去重操作。
不过,VPC Service Controls 计算服务边界限制的方式有所不同。如需了解详情,请参阅本文档的服务边界限制部分。
在 Trusted Cloud 控制台中查看配额
在 Trusted Cloud 控制台导航菜单中,点击安全,然后点击 VPC Service Controls。
转到 VPC Service Controls
如果出现提示,请选择您的组织、文件夹或项目。
在 VPC Service Controls 页面上,选择要查看配额的访问权限政策。
点击查看配额。
配额页面会显示以下访问权限政策限制的用量指标,这些限制会累计适用于给定访问权限政策中的所有服务边界:
- 服务边界
- 受保护资源
- 访问权限级别
- 入站流量和出站流量属性总数
服务边界限制
以下限制适用于每个服务边界配置。也就是说,此限制分别适用于边界的试运行配置和实施配置:
类型 |
限制 |
备注 |
特性
|
6,000
|
此限制适用于入站流量和出站流量规则中指定的属性总数。该属性限制包括对这些规则中项目、VPC 网络、访问权限级别、方法选择器、身份和角色的引用。属性总数还包括方法、服务和项目属性中使用的通配符 * 。 |
属性限制注意事项
VPC Service Controls 会将以下入站流量规则和出站流量规则字段中的每个条目计为一个属性:
规则块 |
字段 |
ingressFrom |
|
ingressTo |
resources
methodSelectors
roles
|
egressFrom |
|
egressTo |
resources
methodSelectors
externalResources
roles
|
如需详细了解这些字段,请参阅入站流量规则参考和出站流量规则参考。
VPC Service Controls 会考虑以下规则来检查边界是否超出属性限制:
入站流量规则和出站流量规则中的每个字段都可以包含多个条目,并且每个条目都计入限制。
例如,如果您在 egressFrom
规则块的 identities
字段中提及服务账号和用户账号,VPC Service Controls 会将这两个属性计入限制。
即使您在多个规则中重复使用同一资源,VPC Service Controls 也会分别统计规则中资源的每一次出现。
例如,如果您在两个不同的入站流量或出站流量规则 rule-1
和 rule-2
中提及项目 project-1
,VPC Service Controls 会将两个属性计入限制。
每个服务边界可以分别设置实施和试运行配置。VPC Service Controls 会为每个配置单独应用属性限制。
例如,如果边界的强制配置和模拟运行配置的属性总数分别为 3,500 个和 3,000 个,则 VPC Service Controls 会认为该边界仍在属性上限范围内。
访问权限政策限制
以下访问权限政策限制累计适用于给定访问权限政策中的所有服务边界:
类型 |
限制 |
备注 |
服务边界
|
10000
|
服务边界网桥会计入此限额。 |
受保护资源
|
40,000
|
仅在入站流量和出站流量政策中引用的项目不计入此限额。请仅以 1 万个或更少的资源的批量为政策添加受保护资源,以防止政策修改请求超时。建议您等待 30 秒,然后再进行下一次政策修改。 |
身份群组 |
1000
|
此限制适用于入站流量和出站流量规则中配置的身份群组的数量。 |
VPC 网络
|
500
|
此限制适用于实施模式、试运行模式和入站规则中引用的 VPC 网络的计数。
|
所有规则标题的总字符数 |
240,000
|
所有入站流量和出站流量规则标题的总长度不得超过此限制。规则标题中的空白字符也会计入此限制。不过,如果您未为某条规则提供标题,则该规则不会计入此限制。 |
以下访问权限政策限制累计适用于给定访问权限政策中的所有访问权限级别:
类型 |
限制 |
备注 |
VPC 网络
|
500
|
此限制适用于访问权限级别中引用的 VPC 网络的数量。 |
组织限制
以下限制适用于给定组织中的所有访问权限政策:
类型 |
限制 |
组织级访问权限政策
|
1 |
文件夹级和项目级访问权限政策
|
50
|
Access Context Manager 配额和限制
您还需要遵循 Access Context Manager 配额和限制,因为 VPC Service Controls 会使用 Access Context Manager API。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-18。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[],[],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."]]