When you create a Cloud SQL instance, you choose a region where the instance and its data are stored. To reduce latency and increase availability, choose the same region for your data and your Compute Engine instances, App Engine apps, and other services.
Regional locations are specific geographic locations within a multi-region location. You can create a Cloud SQL instance in the following regions:
|Region Name||Region Description||Notes|
||Montréal||Second Generation instances only|
||Iowa||First Generation instances only|
||Iowa||Second Generation instances only|
||Northern Virginia||Second Generation instances only|
||Oregon||Second Generation instances only|
||Los Angeles||Second Generation instances only|
||São Paulo||Second Generation instances only|
||Finland||Second Generation instances only|
||London||Second Generation instances only|
||Frankfurt||Second Generation instances only|
||Netherlands||Second Generation instances only|
||Hong Kong||Second Generation instances only|
||Tokyo||Second Generation instances only|
||Mumbai||Second Generation instances only|
||Singapore||Second Generation instances only|
||Sydney||Second Generation instances only|
Zones are sub-locations within a region where you can create zonal
resources such as Second Generation instances. For example, a zone named
us-central1-a indicates a zone within the
us-central1 region. A zone is
independent of other zones in the same region.
For Second Generation instances, you can choose your zone, and you can choose whether your data is replicated between zones or not. If you want your Second Generation instance to be replicated between zones, configure it for high availability.
For First Generation instances, you cannot choose your zone. Data in First Generation instances is replicated across multiple zones, so a zonal failure does not affect the availability of your instance.
For Second Generation instances, you can select your zone.
For First Generation instances, you can store your data close to a Compute Engine or App Engine service hosted within the same region. Choosing a preferred location will reduce latency and improve availability for that service. Note that if the service you have requested to remain close to moves to another zone, your Cloud SQL instance is moved also, which causes downtime.
For more information about zones, see Geography and Regions.
- Get more information about building applications to meet your latency, availability, and durability requirements.
- See a worldwide region map.