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.
| Endpoint Type | URL Format | Example | Use Case |
|---|---|---|---|
| Global | sqladmin.googleapis.com |
sqladmin.googleapis.com |
Managing resources globally across multiple regions. |
| Regional | sqladmin.{region}.rep.googleapis.com |
sqladmin.us-central1.rep.googleapis.com |
Provides strict data residency at the frontend level. |
Supported regions
| Region | API |
|---|---|
| africa-south1 | sqladmin.africa-south1.rep.googleapis.com |
| asia-east1 | sqladmin.asia-east1.rep.googleapis.com |
| asia-east2 | sqladmin.asia-east2.rep.googleapis.com |
| asia-northeast1 | sqladmin.asia-northeast1.rep.googleapis.com |
| asia-northeast2 | sqladmin.asia-northeast2.rep.googleapis.com |
| asia-northeast3 | sqladmin.asia-northeast3.rep.googleapis.com |
| asia-south1 | sqladmin.asia-south1.rep.googleapis.com |
| asia-south2 | sqladmin.asia-south2.rep.googleapis.com |
| asia-southeast1 | sqladmin.asia-southeast1.rep.googleapis.com |
| asia-southeast2 | sqladmin.asia-southeast2.rep.googleapis.com |
| asia-southeast3 | sqladmin.asia-southeast3.rep.googleapis.com |
| australia-southeast1 | sqladmin.australia-southeast1.rep.googleapis.com |
| australia-southeast2 | sqladmin.australia-southeast2.rep.googleapis.com |
| europe-central2 | sqladmin.europe-central2.rep.googleapis.com |
| europe-north1 | sqladmin.europe-north1.rep.googleapis.com |
| europe-north2 | sqladmin.europe-north2.rep.googleapis.com |
| europe-southwest1 | sqladmin.europe-southwest1.rep.googleapis.com |
| europe-west1 | sqladmin.europe-west1.rep.googleapis.com |
| europe-west10 | sqladmin.europe-west10.rep.googleapis.com |
| europe-west12 | sqladmin.europe-west12.rep.googleapis.com |
| europe-west2 | sqladmin.europe-west2.rep.googleapis.com |
| europe-west3 | sqladmin.europe-west3.rep.googleapis.com |
| europe-west4 | sqladmin.europe-west4.rep.googleapis.com |
| europe-west6 | sqladmin.europe-west6.rep.googleapis.com |
| europe-west8 | sqladmin.europe-west8.rep.googleapis.com |
| europe-west9 | sqladmin.europe-west9.rep.googleapis.com |
| me-central1 | sqladmin.me-central1.rep.googleapis.com |
| me-central2 | sqladmin.me-central2.rep.googleapis.com |
| me-west1 | sqladmin.me-west1.rep.googleapis.com |
| northamerica-northeast1 | sqladmin.northamerica-northeast1.rep.googleapis.com |
| northamerica-northeast2 | sqladmin.northamerica-northeast2.rep.googleapis.com |
| northamerica-south1 | sqladmin.northamerica-south1.rep.googleapis.com |
| southamerica-east1 | sqladmin.southamerica-east1.rep.googleapis.com |
| southamerica-west1 | sqladmin.southamerica-west1.rep.googleapis.com |
| us-central1 | sqladmin.us-central1.rep.googleapis.com |
| us-central2 | sqladmin.us-central2.rep.googleapis.com |
| us-east1 | sqladmin.us-east1.rep.googleapis.com |
| us-east4 | sqladmin.us-east4.rep.googleapis.com |
| us-east5 | sqladmin.us-east5.rep.googleapis.com |
| us-south1 | sqladmin.us-south1.rep.googleapis.com |
| us-west1 | sqladmin.us-west1.rep.googleapis.com |
| us-west2 | sqladmin.us-west2.rep.googleapis.com |
| us-west3 | sqladmin.us-west3.rep.googleapis.com |
| us-west4 | sqladmin.us-west4.rep.googleapis.com |
| us-west8 | sqladmin.us-west8.rep.googleapis.com |
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,