Service Directory uses quotas and system limits to maintain fair resource
allocation, prevent service overloads, and help you manage resource use.

Quotas and system limits are similar but differ in the following ways:

- *Quotas* have default values, but you can typically request adjustments.
- *System limits* are fixed values that can't be changed.

To change a quota, see
[requesting additional quota](https://docs.cloud.google.com/service-directory/quotas.md.txt#requesting-additional-quota).

Google Cloud uses quotas to help maintain 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](https://docs.cloud.google.com/docs/quotas/help/request_increase) and [automate quota adjustments](https://docs.cloud.google.com/docs/quotas/quota-adjuster.md.txt)

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.


For more information, see the
[Cloud Quotas overview](https://docs.cloud.google.com/docs/quotas/overview.md.txt).


There are also *system limits* on Service Directory resources.
System limits can't be changed.

## Quotas

Service Directory has the following quotas:

- Namespaces per project per region
- Services per namespace
- Endpoints per service
- Registration requests per minute per region
- Lookup requests per minute per region

You can see your existing quotas and usage on the
[**Quotas** page](https://console.cloud.google.com/iam-admin/quotas?service=servicedirectory.googleapis.com).

## Limits

General Service Directory limitations:

- There is no health-status or health-checking for endpoints. There are two alternatives:
  - Use internal load balancers for integrated health checking, and register the load balancer with Service Directory.
  - Store individual endpoint health status as endpoint annotations in Service Directory.

Cloud DNS integration limits:

- The Cloud DNS integration only serves endpoints that are a valid IPv4 or IPv6 address. Any endpoints that are registered that do not have a valid IP address are ignored by DNS requests.
- SRV records cannot be customized. The symbolic service, protocol, TTL, weight, and priority are managed by Service Directory.
- Service and endpoint annotations are not served in DNS requests. If your service needs to make use of custom annotations, it should use HTTP support in Service Directory.
- You cannot add resource records to the Service Directory zone. Only resource records generated internally from existing Service Directory endpoints are allowed.

## Manage quotas

Service Directory 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](https://docs.cloud.google.com/free/docs/gcp-free-tier)
to stay within their trial.

All projects start with the same quotas, which you can change by
[requesting additional quota](https://docs.cloud.google.com/service-directory/quotas.md.txt#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: - Project [Owner](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#basic) (`roles/owner`) - Project [Editor](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#basic) (`roles/editor`) - [Quota Viewer](https://docs.cloud.google.com/iam/docs/roles-permissions/servicemanagement.md.txt) (`roles/servicemanagement.quotaViewer`) |
| Modify quotas, request additional quota | One of the following: - Project [Owner](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#basic) (`roles/owner`) - Project [Editor](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#basic) (`roles/editor`) - [Quota Administrator](https://docs.cloud.google.com/iam/docs/roles-permissions/servicemanagement.md.txt) (`roles/servicemanagement.quotaAdmin`) - A custom role with the `serviceusage.quotas.update` permission |

### Check your quota

### Console

1. In the Google Cloud console, go to the **Quotas** page.

   [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)
2. 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_ID
```

To 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](https://docs.cloud.google.com/docs/quotas/help/request_increase).

### 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 a given 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.