Cloud Run functions locations
Cloud Run functions is regional, which means the infrastructure that runs a Cloud Run function is located in a specific region and is managed by Google to be redundantly available across all the zones within that region.
When selecting a region to run your Cloud Run functions in, your primary considerations should be latency and availability. You can generally select the region closest to your Cloud Run function's users, but you should also consider the location of the other Google Cloud products and services that your app uses. Using services across multiple locations can affect your app's latency, as well as pricing.
The available regions for Cloud Run functions are listed below. The different versions of Cloud Run functions have different regional availability - see the "Supported product versions" column in the tables.
Tier 1 pricing
Cloud Run functions is available in the following regions with Tier 1 pricing:
| Region | Location | CO2 emissions |
|---|---|---|
asia-east1 |
Taiwan | |
asia-northeast1 |
Tokyo | |
asia-northeast2 |
Osaka | |
europe-north1 |
Finland |
 Low CO2
|
europe-southwest1 |
Madrid | |
europe-west1 |
Belgium |
Low CO2
|
europe-west4 |
Netherlands | |
europe-west8 |
Milan | |
europe-west9 |
Paris |
Low CO2
|
me-west1 |
Tel Aviv | |
us-central1 |
Iowa |
Low CO2
|
us-east1 |
South Carolina | |
us-east4 |
Northern Virginia | |
us-east5 |
Columbus | |
us-south1 |
Dallas | |
us-west1 |
Oregon |
Low CO2 |
Tier 2 pricing
Cloud Run functions is available in the following regions with Tier 2 pricing:
| Region | Location | CO2 emissions |
|---|---|---|
asia-east2 |
Hong Kong | |
asia-northeast3 |
Seoul | |
asia-southeast1 |
Singapore | |
asia-southeast2 |
Jakarta | |
asia-south1 |
Mumbai | |
asia-south2 |
Delhi, India | |
australia-southeast1 |
Sydney | |
australia-southeast2 |
Melbourne | |
europe-central2 |
Warsaw | |
europe-west2 |
London | |
europe-west3 |
Frankfurt |
Low CO2
|
europe-west6 |
Zurich |
Low CO2
|
europe-west10 |
Berlin | |
europe-west12 |
Turin | |
me-central1 |
Doha | |
me-central2 |
Dammam | |
northamerica-northeast1 |
Montreal |
Low CO2
|
northamerica-northeast2 |
Toronto |
Low CO2
|
southamerica-east1 |
São Paulo |
Low CO2
|
southamerica-west1 |
Santiago, Chile | |
us-west2 |
Los Angeles | |
us-west3 |
Salt Lake City | |
us-west4 |
Las Vegas |
Select the region
You can select a region for your function during deployment.
gcloud
If you are using the Google Cloud CLI, you can specify the region by using
the --region flag:
gcloud functions deploy FUNCTION_NAME --region=REGION ...
Where REGION is one of the regions listed above.
Console
If you are using the Google Cloud console, you can select the region when you create and deploy a function.
In the Google Cloud console, go to the Cloud Run functions Overview page.
Go to the Cloud Run functions Overview page
Make sure that the project for which you enabled Cloud Run functions is selected.
Click Create Function.
In the Region field, select a region.
You can deploy functions to different regions within a project, but once the region has been selected for a function it cannot be changed.
Functions in a given region in a given project must have unique (case sensitive) names, but functions across regions or across projects can share the same name.
Setting a default region
You can set a default region using the Google Cloud CLI as follows:
gcloud config set functions/region REGION
For example:
gcloud config set functions/region europe-west1
Data residency
Cloud Run functions provides a data residency guarantee at the function execution scope (Scope A Compliance—function execution), wherein a given function provides for data residency for the function invocation/execution.
This compliance applies to both HTTP functions and event-driven functions. For event-driven functions, Cloud Run functions is data residency-compliant from the moment the upstream product (triggering product) delivers the event to Cloud Run functions. Hence, it's important to ensure that the upstream product (such as Cloud Storage or Pub/Sub) is itself data residency-compliant.
Best practices for changing region
If you need to change a region where a function is deployed, follow the recommendations below.
HTTP functions
For HTTP functions, we recommend that you first redeploy your HTTP function to
the destination region (it can have the same name), and then alter your original
function to redirect its HTTP request to the new function. If clients of your
HTTP function support redirects, you can simply change your original function
to return an HTTP redirect status (301) along with the URL of your new
function. If your clients do not handle redirects well, you can proxy the
request from the original function to the new function by initiating a new
request from the original function to the new function. The final step is to
ensure that all clients are calling the new function.
Event-driven functions
Event-driven functions adopt an at-least-once event delivery semantic, which means that under some circumstances they can receive duplicate events, and so should always be implemented to be idempotent. If your function is already idempotent then you can simply redeploy the function in the new region with the same event trigger, and remove the old function after you verify that the new function is correctly receiving traffic. During this transition both functions will receive events.
If your function is not currently idempotent, or its idempotency does not extend beyond the region, then we recommend that you first implement idempotency before moving the function.