# Cloud SQL regional API endpoints are now GA across MySQL, PostgreSQL and SQL Server Google Cloud has moved regional Cloud SQL Admin API endpoints to general availability across all three managed database engines, giving regulated workloads a region-local control-plane path with isolated frontends, load balancers and TLS termination. The change is not about where database rows live; Cloud SQL already has regional instance placement. It changes where API control traffic is processed, reducing dependence on global frontend infrastructure and making data-in-transit boundaries easier to align with sovereignty requirements. - Status: Active - Published: 2026-09-09T20:33:25+12:00 - Updated: 2026-09-09T20:33:25+12:00 - Categories: Cloud & Infrastructure, Cloud Platforms, Databases & Storage - Tags: Cloud SQL, data residency, Google Cloud, regional infrastructure - Canonical HTML: https://beyondthe.news/dossiers/google-cloud-sql-regional-admin-api-endpoints-data-residency-ga ## What changed On September 8, 2026, Google Cloud made regional endpoints generally available for the Cloud SQL Admin API across MySQL, PostgreSQL and SQL Server. Instead of sending management calls through the global `sqladmin.googleapis.com` endpoint, applications and automation can use a region-specific URL such as `sqladmin.{region}.rep.googleapis.com`. Google says the regional frontend, load balancer, control plane and TLS termination keep the relevant management traffic within the chosen region and isolate one region’s frontend failures from others. The feature had previously been in preview. ## Why it matters Data residency is not only a storage-location question. Provisioning, configuration, metadata and administrative API traffic can cross different infrastructure paths from the database connection itself. Regional Cloud SQL endpoints let teams with sovereignty or regulated-workload requirements keep this control-plane traffic inside the committed region while also reducing dependency on a global API frontend. That gives infrastructure teams a clearer design for workloads governed by controls such as Assured Workloads Regions or ITAR-sensitive regional boundaries. ## The regional endpoint replaces a global control-plane route Cloud SQL automation can now target a regionalized Admin API hostname tied to the database region. Google enforces region matching: requests made through a regional endpoint are scoped to resources in that region rather than behaving as a global inventory surface. ## Regional isolation includes frontend and load-balancing infrastructure Google says each regional endpoint uses regionally isolated frontend and load-balancing infrastructure with a separate regional control plane. A failure in one regional frontend is therefore designed not to affect another region’s endpoint, reducing one class of dependency on global API infrastructure. ## TLS terminates inside the region Certificate management and TLS termination for the endpoint occur on the regional load balancer. Google’s stated design is that API traffic remains encrypted until it reaches the destination region and stays within that region while being processed there. ## GA now covers all three Cloud SQL engines The September release applies to Cloud SQL for MySQL, PostgreSQL and SQL Server. That makes the regional control-plane pattern consistent across mixed database estates rather than forcing one engine onto a different management architecture. ## This does not automatically regionalize every dependency Using a regional Admin API endpoint does not mean every service involved in an application is region-bound. Infrastructure-as-code runners, secrets, logging, monitoring, identity systems and third-party integrations can still create cross-region data paths. Teams should map the full management workflow before treating a database deployment as sovereignty-complete. ## Key details - Regional Cloud SQL Admin API endpoints became generally available September 8, 2026. - GA covers Cloud SQL for MySQL, PostgreSQL and SQL Server. - Regional endpoint hostnames follow the form `sqladmin.{region}.rep.googleapis.com`. - Regional endpoints keep relevant Admin API network traffic within the same region as the target instance. - The regional frontend and load balancer infrastructure have regional isolation and a separate regional control plane. - Google says a frontend/load-balancer failure in one region does not affect other regional endpoints. - TLS termination and certificate handling occur in the destination region. - Google positions regional endpoints for stringent residency and sovereignty requirements including ITAR and Assured Workloads Regions. - The feature previously entered preview in May 2026. ## Builder takeaways - If Cloud SQL management traffic is in your compliance scope, update SDK/API endpoints in automation rather than assuming regional database placement already constrains the Admin API path. - Keep the target endpoint region aligned with the resource region and test failure handling for requests accidentally pointed at the wrong regional endpoint. - Audit infrastructure-as-code, CI/CD and operational scripts for hard-coded global Cloud SQL Admin API URLs before migrating. - Treat regional endpoints as one layer of sovereignty architecture; separately map identity, logging, secrets, monitoring and application data paths. - For multi-region estates, decide whether each deployment pipeline should be region-bound rather than giving one global runner management access across every region. ## What to watch - Whether Google makes regional endpoints the recommended/default path for regulated Cloud SQL deployments. - SDK and infrastructure-as-code support that reduces manual regional endpoint configuration. - Expansion of similar regional control-plane endpoints across other Google Cloud managed services. - Independent operational evidence on regional isolation during Google Cloud control-plane incidents. ## Uncertainties - Google’s residency and isolation guarantees are first-party service claims and should be mapped against the exact compliance regime an organization must satisfy. - The feature regionalizes Cloud SQL Admin API processing, not every data/control path in an application stack. - Existing tools may default to the global endpoint until explicitly configured for the regional hostname. ## Sources - [Cloud SQL release notes](https://cloud.google.com/sql/docs/release-notes) — Google Cloud · primary release notes · 2026-09-08T00:00:00+12:00. Primary GA announcement across MySQL, PostgreSQL and SQL Server, including isolation, TLS termination and residency details. - [Cloud SQL regional endpoints](https://cloud.google.com/sql/docs/mysql/regional-endpoints) — Google Cloud · primary documentation. Implementation and regional-scoping guidance for Cloud SQL regional Admin API endpoints.