Use Cloud SQL regional endpoints

Overview

Cloud SQL supports regional endpoints for Admin APIs. This feature enhances data residency for data in-transit and improves regional reliability.

There are two options for routing Cloud SQL Admin API requests:

• Through the global endpoint, which routes the requests through a global load balancer before they reach the appropriate region.
• Through regional endpoints, which let you direct your API calls to a region-specific endpoint where they're handled by that region's frontend infrastructure. This improves data locality and helps meet strict compliance expectations.

Supported regions

Regional endpoint differences from the global endpoint

When migrating to regional endpoints, be aware of the following behavior changes compared to the global endpoint:

Strict region matching

Regional endpoints enforce strict region boundaries. If you send an API request such as INSERT, UPDATE, PATCH, DELETE, or GET to a regional endpoint, then the target resource defined in your request body must match the region of the endpoint.

Behavior: If the region in the endpoint and the region in the request don't match, then the request is rejected with a 4xx error.

Instance.List behavior

When using the Instance.List API:

• The global endpoint queries and returns instances across all regions where the user has resources.
• A regional endpoint only lists instances that exist within that specific region.

v1 example (Regional):

GET https://sqladmin.{region}.rep.googleapis.com/v1/projects/{project}/instances

v1beta4 example (Regional):

GET https://sqladmin.{region}.rep.googleapis.com/sql/v1beta4/projects/{project}/instances

Backups and disaster recovery

For backups, regional endpoints behave the same way as the global endpoint, with no change in behavior, which means that you can use them to access backups for disaster recovery (DR) scenarios involving cross-region restores,

However, because backups are treated as global resources to ensure that they can be restored across regions during a single-region outage, we strongly recommend that you use the global endpoint rather than regional endpoints for accessing backups.

Global API example:

GET https://sqladmin.googleapis.com/v1/projects/{project}/backups

Regional API example:

GET https://sqladmin.{region}.rep.googleapis.com/v1/projects/{project}/backups

Use regional endpoints in API requests

Authentication methods (such as Bearer tokens), API paths, request bodies, and API versions remain completely unchanged when using regional endpoints.

To make a request to a regional endpoint using curl or a custom HTTP client, replace the global base URL (sqladmin.googleapis.com) with a specific regional base URL (like sqladmin.us-west1.rep.googleapis.com).

Examples using curl

Global API example

curl -H "Authorization: Bearer $(gcloud auth print-access-token)" https://sqladmin.googleapis.com/v1/projects/{project}/instances

Regional API example (us-central1)

curl -H "Authorization: Bearer $(gcloud auth print-access-token)" https://sqladmin.us-central1.rep.googleapis.com/v1/projects/{project}/instances

Use manual overrides for gcloud CLI and Terraform

You can use Cloud SQL regional endpoints with the gcloud CLI and Terraform by using a manual configuration override that explicitly directs the tool to your specific regional URL (sqladmin.{region}.rep.googleapis.com).

Example gcloud CLI override:

gcloud config set api_endpoint_overrides/sql https://sqladmin.us-central1.rep.googleapis.com/

Example Terraform override:

export GOOGLE_SQL_CUSTOM_ENDPOINT="https://sqladmin.us-central1.rep.googleapis.com/sql"

Limitations

Cloud SQL regional endpoints has the following limitations.

• Regional boundary restrictions: Cloud SQL regional endpoints enforce strict matching. The region of the target API resource must match the region of the endpoint exactly. Otherwise, the request is rejected with a 4xx error.

• Restricted API visibility: when you use a regional endpoint, the Instance.List API only returns resources located within that specific region.

• Limited network support: access to a Cloud SQL Admin API regional endpoint is restricted to public network connections only. You can't connect to a regional endpoint from a Virtual Private Cloud network or a private network connection.

• No multi-regional support: multi-regional endpoints, which are endpoints that are include multiple regions (for example, us.rep.googleapis.com), aren't supported.

• Backend dependencies: although the frontend of the Cloud SQL Admin API is regionalized, certain backend dependencies of the API and metadata can still rely on global components.

• Manual tooling configuration: built-in support isn't provided for the gcloud CLI and Terraform. You must use configuration overrides to use regional endpoints with the gcloud CLI and Terraform.

• Google Cloud console and Kubernetes Config Connector support: there isn't support for regional endpoints within the Google Cloud console or Config Connector.

• Backup and recovery: backups are treated as global resources to help ensure that they can be restored across regions. While you can create backups using regional endpoints for disaster recovery, we recommend that you continue to use the global endpoint for creating and restoring backups to avoid complications.

• Cloud SQL remote MCP server doesn't support regional endpoints: you can't use regional endpoints to access the remote Cloud SQL MCP server. Connect using the global endpoint, https://sqladmin.googleapis.com/mcp. For more information about the remote Cloud SQL MCP server, see Use the Cloud SQL remote MCP server.