This document lists the quotas and system limits that apply to Cloud Next Generation Firewall. Quotas specify the amount of a countable, shared resource that you can use, and they are defined by Google Cloud services such as Cloud Next Generation Firewall. System limits are fixed values that cannot be changed.
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 way 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 system limits on Cloud NGFW resources. System limits can't be changed.
Quotas
This section lists the quotas that apply to Cloud Next Generation Firewall.
To monitor per-project quotas that use Cloud Monitoring, set up monitoring
for the metric serviceruntime.googleapis.com/quota/allocation/usage on the
Consumer Quota resource type. Set additional label filters (service,
quota_metric) to get to the quota type. For information about monitoring quota
metrics, see Chart and monitor quota metrics.
Each quota has a limit and a usage value.
Unless noted otherwise, to change a quota, see Request a higher quota.
Per project
The following table highlights Cloud NGFW quotas that are per project:
| Quota | Description |
|---|---|
| VPC firewall rules | The number of VPC firewall rules that you can create in a project, regardless of the VPC network to which each firewall rule applies. |
| Global network firewall policies | The number of Global network firewall policies in a project, regardless of how many VPC networks are associated with each policy. |
| Regional network firewall policies | The number of Regional network firewall policies in each region of a project, regardless of how many VPC networks are associated with each policy. |
| Global address groups per project | The number of global address groups that you can define in a project. |
| Regional address groups per project per region | The number of regional address groups that you can define in each region of a project. |
Per organization
The following table highlights Cloud NGFW quotas that are per organization. To change an organization-level quota, file a Support case.
| Quota | Description |
|---|---|
| Unassociated Hierarchical firewall policies in an organization | The number of Hierarchical firewall policies in an organization that are not associated with any folder or organization resource. There is no limit on the number of Hierarchical firewall policies in an organization that are associated with a resource. |
Per firewall policy
The following table highlights Cloud NGFW quotas that are per firewall policy resource:
| Quota | Description |
|---|---|
| Hierarchical firewall policies | |
| Rule attributes per hierarchical firewall policy | This quota is the sum of rule attributes from all rules in a hierarchical firewall policy. For more information, see Rule attribute count details. |
| Domain names (FQDNs) per hierarchical firewall policy | The number of domain names that you can include in all rules of a hierarchical firewall policy. This quota is the sum of all source domain names from all ingress rules in the policy plus the sum of all destination domain names from all egress rules in the policy. |
| Global network firewall policies | |
| Rule attributes per global network firewall policy | The sum of rule attributes from all rules in a global network firewall policy. For more information, see Rule attribute count details. |
| Domain names (FQDNs) per global network firewall policy | The number of domain names that you can include in all rules of a global network firewall policy. This quota is the sum of all source domain names from all ingress rules in the policy plus the sum of all destination domain names from all egress rules in the policy. |
| Regional network firewall policies | |
| Rule attributes per regional network firewall policy | The sum of rule attributes from all rules in a regional network firewall policy. For more information, see Rule attribute count details. |
| Domain names (FQDNs) per regional network firewall policy | The number of domain names (FQDNs) that you can include in all rules of a regional network firewall policy: This quota is the sum of all source domain names from all ingress rules in the policy plus the sum of all destination domain names from all egress rules in the policy. |
Rule attribute count details
Each firewall policy supports a maximum total number of attributes from all rules in the policy. To determine the rule attribute count for a given firewall policy, describe the policy. For directions, see the following:
- Describe a policy in the hierarchical firewall policy documentation
- Describe a global network firewall policy
- Describe a regional network firewall policy
The following table lists example rules and the attribute count for each example rule.
| Example firewall rule | Rule attribute count | Explanation |
|---|---|---|
Ingress allow firewall rule with source IP address range
10.100.0.1/32, tcp protocol, and
5000-6000 port range.
|
3 | One source range; one protocol, one port range. |
Ingress deny firewall rule with source IP address ranges
10.0.0.0/8, 192.168.0.0/16, destination IP
address range 100.64.0.7/32, tcp and
udp protocols, port ranges 53-53 and
5353-5353.
|
11 | There are four protocol and port combinations: tcp:53-53,
tcp:5353-5353, udp:53-53, and
udp:5353-5353. Each protocol and port combination uses two
attributes. One attribute each for the two source IP address ranges, one
attribute for the destination IP address range, and eight attributes for the
protocol and port combinations produces an attribute count of 11. |
Egress deny firewall rule with source IP address range
100.64.0.7/32, destination IP address range
10.100.0.1/32, 10.100.1.1/32, tcp:80,
tcp:443, and udp:4000-5000.
|
9 | Protocol and port combinations expand to three: tcp:80-80,
tcp:443-443, and udp:4000-5000. Each protocol and
port combination uses two attributes. One attribute for the source range,
one attribute each for the two destination IP address ranges, and six
attributes for the protocol and port combinations produces an attribute
count of 9. |
Limits
Limits cannot be increased unless specifically noted.
Per organization
The following limits apply to organizations:
| Item | limit | Notes |
|---|---|---|
| Global address groups per organization | 100 | The maximum number of global address groups that you can create per organization. |
| Regional address groups per organization per region | 100 | The maximum number of regional address groups that you can create per organization in a region. |
| Organization address groups | 100 | The maximum number of address groups that you can create per organization regardless of location (global or regional). |
| Maximum address group capacity | 1,000 | The maximum capacity of an address group per organization or project. |
| Maximum secure tag keys per organization or per project | 1,000 | The maximum number of secure tag keys that you can create per organization or project. For more information, see Tag limits. |
| Maximum secure tag values per key per organization or per project | 1,000 | The maximum number of secure tag values that you can add per key in an organization or project. For more information, see Tag limits. |
| Maximum secure tags key-value pairs per resource per organization | 50 | The maximum number of secure tag key-value pairs that you can add per resource in an organization or project. For more information, see Tag limits.
For network limits, see Per network limits. |
| Threat prevention security profiles per organization | 40 | The maximum number of security profiles of type threat prevention that you can create per organization. |
| Security profile groups per organization | 40 | The maximum number of security profile groups that use a threat prevention security profile that you can create per organization. |
| Firewall endpoints per zone per organization | 10 | The maximum number of firewall endpoints that you can create per zone per organization. |
Per network
The following limits apply to VPC networks:
| Item | Limit | Notes |
|---|---|---|
| Maximum global network firewall policies per network | 1 | The maximum number of global network firewall policies that you can associate with a VPC network. |
| Maximum regional network firewall policies per region per network | 1 | The maximum number of regional network firewall policies that you can associate with a combination of VPC network and region. |
| Maximum number of domain names (FQDNs) per network | 1,000 | The maximum total number of domain names that can be used in firewall rules that come from hierarchical firewall policies, global network firewall policies, and regional network firewall policies associated with a VPC network. |
| Firewall endpoints per zone per network | 1 | The maximum number of firewall endpoints that you can assign per zone per network. |
Per firewall rule
The following limits apply to firewall rules:
| Item | Limit | Notes |
|---|---|---|
| Maximum number of source secure tags per ingress firewall policy rule | 256 | Applicable only to ingress firewall policy rule—the maximum number of secure tags that you can use as source tags in the firewall rule. This limit cannot be increased. |
| Maximum number of target secure tags per firewall policy rule | 256 | Applicable only to firewall policy rule—the maximum number of secure tags that you can use as target tags in the firewall rule. This limit cannot be increased. |
| Maximum number of source network tags per ingress VPC firewall rule | 30 | Applicable only to ingress VPC firewall rules—the maximum number of network tags that you can use as source tags in the firewall rule. This limit cannot be increased. |
| Maximum number of target network tags per VPC firewall rule | 70 | Applicable only to VPC firewall rules—the maximum number of network tags that you can use as target tags in the firewall rule. This limit cannot be increased. |
| Maximum number of source service accounts per ingress VPC firewall rule | 10 | Applicable only to ingress VPC firewall rules—the maximum number of service accounts that you can use as sources in the firewall rule. This limit cannot be increased. |
| Maximum number of target service accounts per firewall rule | 10 | The maximum number of service accounts that you can use as targets in a VPC firewall rule or rule in a firewall policy. This limit cannot be increased. |
| Maximum number of source IP address ranges per firewall rule | 5,000 | The maximum number of source IP address ranges that you can specify in a VPC firewall rule or rule in a firewall policy. IP address ranges are either IPv4 only or IPv6 only. This limit cannot be increased. |
| Maximum number of destination IP address ranges per firewall rule | 5,000 | The maximum number of destination IP address ranges that you can specify in a VPC firewall rule or rule in a firewall policy. IP address ranges are either IPv4 only or IPv6 only. This limit cannot be increased. |
| Maximum number of source address groups per ingress firewall rule in a firewall policy | 10 | The maximum number of source address groups that you can specify in an ingress firewall rule in a firewall policy. This limit cannot be increased. |
| Maximum number of destination address groups per firewall rule in a firewall policy | 10 | The maximum number of destination address groups that you can specify in an egress firewall rule in a firewall policy. This limit cannot be increased. |
| Maximum number of domain names (FQDNs) per firewall rule in a firewall policy | 100 | The number of domain names (FQDNs) that you can include in a rule of a firewall policy. This limit cannot be increased. |
Per firewall endpoint
The following limits apply to firewall endpoints:
| Item | Limit | Notes |
|---|---|---|
| Associations per firewall endpoint | 50 | The maximum number of VPC networks that you can associate with a firewall endpoint. You can create additional firewall endpoints in the same zone to overcome this limit. |
Per security profile
The following limits apply to security profiles:
| Item | Limit | Notes |
|---|---|---|
| Number of threat overrides per security profile | 100 | The maximum number of threat overrides you can add in a threat prevention security profile. |
Per VM network interface
The following limits apply to VM network interfaces:
| Item | Limit | Notes |
|---|---|---|
| Maximum secure tags per VM interface | 10 | The maximum number of secure tags that you can add per VM per NIC. |
Manage quotas
Cloud Next Generation Firewall enforces quotas on resource usage for various reasons. For example, quotas protect the community of Google Cloud users by preventing unforeseen spikes in usage. Quotas also help users who are exploring Google Cloud with the free tier to stay within their trial.
All projects start with the same quotas, which you can change by requesting additional quota. Some quotas might increase automatically based on your use of a product.
Permissions
To view quotas or request quota increases, Identity and Access Management (IAM) principals need one of the following roles.
| Task | Required role |
|---|---|
| Check quotas for a project | One of the following:
|
| Modify quotas, request additional quota | One of the following:
|
Check your quota
Console
- In the Google Cloud console, go to the Quotas page.
- To search for the quota that you want to update, use the Filter table. If you don't know the name of the quota, use the links on this page instead.
gcloud
Using the Google Cloud CLI, run the following command to
check your quotas. Replace PROJECT_ID with your own project ID.
gcloud compute project-info describe --project PROJECT_IDTo check your used quota in a region, run the following command:
gcloud compute regions describe example-region
Errors when exceeding your quota
If you exceed a quota with a gcloud command,
gcloud outputs a quota exceeded error
message and returns with the exit code 1.
If you exceed a quota with an API request, Google Cloud returns the
following HTTP status code: 413 Request Entity Too Large.
Request additional quota
To adjust most quotas, use the Google Cloud console. For more information, see Request a quota adjustment.
Console
- In the Google Cloud console, go to the Quotas page.
- On the Quotas page, select the quotas that you want to change.
- At the top of the page, click Edit quotas.
- For Name, enter your name.
- Optional: For Phone, enter a phone number.
- Submit your request. Quota requests take 24 to 48 hours to process.
Resource availability
Each quota represents a maximum number for a particular type of resource that you can create, if that resource is available. It's important to note that quotas don't guarantee resource availability. Even if you have available quota, you can't create a new resource if it is not available.
For example, you might have sufficient quota to create a new regional, external IP address
in the us-central1 region. However, that is not possible if there are no
available external IP addresses in that region. Zonal resource
availability can also affect your ability to create a new resource.
Situations where resources are unavailable in an entire region are rare. However, resources within a zone can be depleted from time to time, typically without impact to the service level agreement (SLA) for the type of resource. For more information, review the relevant SLA for the resource.