Cloud Build locations

Cloud Build supports regional builds in private pools and default pools.

When selecting a region for your builds, your primary considerations should be latency and availability. You can generally select the region closest to your Cloud Build's users, but you should also consider the location of the other Google Cloud products and services that your build might integrate with. Using services across multiple locations can affect your app's latency, as well as pricing.

Cloud Build is available in the following regions:

  • africa-south1
  • asia-east1
  • asia-east2
  • asia-northeast1
  • asia-northeast2
  • asia-northeast3
  • asia-south1
  • asia-south2
  • asia-southeast1
  • asia-southeast2
  • australia-southeast1
  • australia-southeast2
  • europe-central2
  • europe-north1
  • europe-north2
  • europe-southwest1
  • europe-west1
  • europe-west2
  • europe-west3
  • europe-west4
  • europe-west6
  • europe-west8
  • europe-west9
  • europe-west10
  • europe-west12
  • me-central1
  • me-central2
  • me-west1
  • northamerica-northeast1
  • northamerica-northeast2
  • northamerica-south1
  • southamerica-east1
  • southamerica-west1
  • us-central1
  • us-east1
  • us-east4
  • us-east5
  • us-south1
  • us-west1
  • us-west2
  • us-west3
  • us-west4

Select a region

To run regional builds, specify the region when starting a build via the command line or when creating a build trigger.

To select a region for your private pool, specify the region when creating the private pool. Once you create a private pool within a region, you can't move it to another region. When you create a private pool in a specific region, it is managed by Google to be redundantly available across all the zones within that region.

If the build config file associated with your trigger specifies a private pool, then the region you select for your trigger must match the region of the private pool.

If you select global as the region for the build trigger, then Cloud Build uses the region specified in the build config file associated with the trigger to run the build. This can either be the region of the private pool, if you specify a private pool in your build config file, or the global default pool if you don't specify a private pool.

Access Cloud Build resources using regional endpoints

You can use regional endpoints to access resources in Cloud Build. Using regional endpoints lets you run your workloads in a manner that complies with data residency and data sovereignty requirements, where your request traffic is routed directly to the region specified in the endpoint.

Regional endpoints are request endpoints that only allow requests to proceed if the affected resource exists in the location specified by the endpoint. For example, when you use the endpoint https://cloudBuild.me-central2.rep.googleapis.com in a create builds request, the request only proceeds if the build config file is located in me-central2.

Unlike global endpoints, where requests can be processed in a different location from where the resource resides, regional endpoints guarantee that your requests are processed only within the location specified by the endpoint where the resource resides. Regional endpoints terminate TLS sessions in the location specified by the endpoint for requests received from the Internet, from other Google Cloud resources (such as Compute Engine virtual machines),from on-premise services using VPN or Interconnect, and from Virtual Private Clouds (VPCs).

Regional endpoints guarantee data residency by ensuring that your object's data at rest and in transit doesn't get moved out of the location specified by the endpoint. This guarantee excludes resource metadata, such as object names and bucket IAM policies. For more information, see Note on Customer Data and Service data.

For information about the steps needed to run a build, see Running builds.

Configure the Google Cloud CLI for use with regional endpoints

To configure the gcloud CLI for use with regional endpoints, do the following:

  1. Make sure you're using the Google Cloud CLI 402.0.0 or newer.

  2. Set the api_endpoint_overrides/cloudbuild property to the regional endpoint that you want to use:

    gcloud config set api_endpoint_overrides/cloudbuild https://cloudbuild.LOCATION.rep.googleapis.com/

    Alternatively, you can set the CLOUDSDK_API_ENDPOINT_OVERRIDES_CLOUDBUILD environment variable to the endpoint:

    CLOUDSDK_API_ENDPOINT_OVERRIDES_CLOUDBUILD=https://cloudbuild.LOCATION.rep.googleapis.com/

Restricted regions for some projects

Depending on usage, certain projects may be restricted to only use Cloud Build in the following regions:

  • us-central1
  • us-west2
  • europe-west1
  • asia-east1
  • australia-southeast1
  • southamerica-east1