Quotas

The following sections describe quotas and limits for Cloud VPN. To change a quota, simply request additional quota using the GCP Console. Limits cannot generally be increased unless specifically noted.

Quotas

This table covers important quotas per project. See the Console quotas page for other quotas.

Per project

Item Quota Notes
VPN gateways Quota For HA VPN only
External VPN gateways Quota For HA VPN only
VPN tunnels Quota This quota represents the combined total number of Classic VPN tunnels and HA VPN tunnels.
Routers Quota This quota represents the number of Cloud Routers you can create within your project, in any network and region. Networks also have a limit on the number of Cloud Routers in any given region. See Cloud Router quotas and limits for more details.

Subject to the Cloud Router quotas and limits, the number of Cloud Routers is entirely independent of the type of Cloud VPN gateway, Classic VPN or HA VPN, that a tunnel is attached to, although the quota is applied the same to either type of gateway.
Target VPN gateways Quota For Classic VPN only
Forwarding rules Quota For Classic VPN only

Limits

The following limits apply to Cloud VPN. In this table, VPN tunnel means either a Classic VPN tunnel or a HA VPN tunnel. Unless otherwise stated, these limits cannot be increased.

Item Limit Notes
Bandwidth per VPN tunnel Up to 3 Gbps ingress
Up to 3 Gbps egress
This maximum bandwidth can only be achieved by using a MTU size of 1,460 bytes and a packet rate of 250,000 packets per second (pps).

Cloud VPN only throttles egress IPsec traffic. It does not throttle ingress traffic.

Refer to Network bandwidth for more details.

Overview

Cloud VPN enforces quotas on resource usage for a variety of reasons. For example, quotas protect the community of Google Cloud Platform users by preventing unforeseen spikes in usage. Quotas also help users who are exploring GCP 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 may increase automatically, based on your use of a product.

Permissions

To view quotas or request quota increases, IAM members need one of the following roles.

Task Required Role
Check quotas for a project Project owner or editor or Quota Viewer
Modify quotas, request additional quota Project owner or editor, Quota Admin, or custom role with the serviceusage.quotas.update permission

Checking your quota

In the GCP Console, go to the Quotas page.

Using the gcloud command-line tool, run the following command to check your quotas. Replace [PROJECT_ID] with your own project ID.

    gcloud compute project-info describe --project [PROJECT_ID]

To check your used quota in a region, run:

    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, GCP returns the following HTTP status code: HTTP 413 Request Entity Too Large.

Requesting additional quota

Request additional quota from the Quotas page in the GCP Console. Quota requests take 24 to 48 hours to process.

  1. Go to the Quotas page.

    Go to the Quotas page

  2. In the Quotas page, select the quotas you want to change.
  3. Click the Edit Quotas button at the top of the page.
  4. Fill out your name, email, and phone number and click Next.
  5. Fill in your quota request and click Next.
  6. Submit your request.

Resource availability

Each quota represents a maximum number for a particular type of resource that you can create, provided that resource is available. It's important to note that quotas do not guarantee resource availability. Even if you have available quota, you won't be able to create a new resource if it is not available. For example, you might have sufficient quota to create new regional, external IP address in the us-central1 region, but that would not be possible if there were 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 SLA for the type of resource. For more information, review the relevant Service Level Agreement (SLA) for the resource.

Var denne siden nyttig? Si fra hva du synes:

Send tilbakemelding om ...