Filestore instances live in zones within regions. A region is a specific
geographical location where you can run your resources. Each region is
subdivided into several zones. For example, the us-central1
region in the
central United States has zones us-central1-a
, us-central1-b
, us-central1-
c
, and us-central1-f
. For more information, see
Geography and regions.
Some Google Cloud APIs, including the Filestore API, use the concept of locations, which can represent either regions or zones. For Filestore instances, locations map to zones.
To decrease network latency, we recommend creating a Filestore instance in a region and zone that is close to where you plan to use it. For example, if you plan to access the instance from Asia, then you should create it in one of the asia-east1 zones. Similarly, you will get the best performance by mounting Filestore file shares on clients in the same region.
Supported regions
Filestore is available in the following regions and zones.
An asterisk * next to the region indicates that the region supports High Scale tier instances.
AMERICAS
REGION | NAME | ZONES |
---|---|---|
OREGON* | us-west1 |
|
LOS ANGELES | us-west2 |
|
SALT LAKE CITY | us-west3 |
|
LAS VEGAS | us-west4 |
|
IOWA* | us-central1 |
|
SOUTH CAROLINA* | us-east1 |
|
N. VIRGINIA | us-east4 |
|
MONTRÉAL | northamerica-northeast1 |
|
SÃO PAULO | southamerica-east1 |
|
EUROPE
REGION | NAME | ZONES |
---|---|---|
LONDON | europe-west2 |
|
BELGIUM* | europe-west1 |
|
NETHERLANDS* | europe-west4 |
|
ZURICH | europe-west6 |
|
FRANKFURT | europe-west3 |
|
FINLAND | europe-north1 |
|
WARSAW | europe-central2 |
|
ASIA PACIFIC
REGION | NAME | ZONES |
---|---|---|
MUMBAI | asia-south1 |
|
SINGAPORE* | asia-southeast1 |
|
JAKARTA | asia-southeast2 |
|
HONG KONG | asia-east2 |
|
TAIWAN* | asia-east1 |
|
TOKYO | asia-northeast1 |
|
OSAKA | asia-northeast2 |
|
SYDNEY | australia-southeast1 |
|
SEOUL | asia-northeast3 |
|