Cloud Build supports regional builds inprivate poolsanddefault pools.

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

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
• asia-southeast3
• 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

Important: Not all machine types are available in all regions for private pools.SeeMachine type availability by regionfor a list of supported regions for each machine type.

Select a region

To run regional builds, specify the region whenstarting a buildvia the command lineor whencreating a build trigger.

To select a region for your private pool, specify the region whencreatingthe private pool.Once you create a private pool within a region, you can't moveit to another region. When you create a private pool in a specific region, itis managed by Google to be redundantly available acrossall the zones within that region.

If thebuild config fileassociated with your trigger specifies a private pool, then the region youselect for your trigger must match the region of the private pool.

If you selectglobal as the region for the build trigger, thenCloud Build uses the region specified in the build config fileassociated with the trigger to run the build. This can either be the region ofthe private pool, if you specify a private pool in your build config file, orthe 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 yourworkloads in a manner that complies withdata residency and datasovereignty requirements, where your request traffic is routed directly to theregion specified in the endpoint.

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

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

Regional endpoints guarantee data residency by ensuring that yourobject's data at rest and in transit doesn't get moved out of the locationspecified by the endpoint. This guarantee excludes resource metadata, such asobject names and bucket IAM policies. For more information,seeNote on Customer Data and Service data.

Note: Regional endpoints support only HTTPS. HTTP isn't supported.

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

Configure the Google Cloud CLI for use with regional endpoints

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

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

2. Set theapi_endpoint_overrides/cloudbuild property to the regionalendpoint that you want to use:

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

   Alternatively, you can set theCLOUDSDK_API_ENDPOINT_OVERRIDES_CLOUDBUILD environment variable to theendpoint:

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