Stay organized with collections
Save and categorize content based on your preferences.
Dataproc supports regional endpoints based on
Compute Engine regions.
You must specify a region, such as "us-east1" or "europe-west1",
when you create a Dataproc cluster. Dataproc
will isolate cluster resources, such as VM instances and Cloud Storage
and metadata storage, within a zone within the specified region.
You can optionally specify a zone within the specified cluster region, such as
"us-east1-a" or "europe-west1-b", when you create a cluster. If you do not
specify the zone, Dataproc Auto Zone Placement
will choose a zone within your specified cluster region to locate clusters
resources.
The regional namespace corresponds to the /regions/REGION
segment of Dataproc resource URIs (see, for example, the
cluster
networkUri).
Regional endpoint semantics
Regional endpoint names follow a standard naming convention based on
Compute Engine regions.
For example, the name for the Central US region is us-central1, and the name
of the Western Europe region is europe-west1. Run the gcloud compute regions list
command to see a listing of available regions.
Create a cluster
gcloud
When you create a cluster, specify a region using the required
--region flag.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eDataproc clusters must be created within a specified Compute Engine region, such as "us-east1" or "europe-west1," to isolate cluster resources within a zone of that region.\u003c/p\u003e\n"],["\u003cp\u003eYou can optionally specify a zone within the chosen region, or if not, Dataproc Auto Zone Placement will automatically select one.\u003c/p\u003e\n"],["\u003cp\u003eRegional endpoint names follow a standard convention based on Compute Engine regions, for example, "us-central1" for Central US and "europe-west1" for Western Europe.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a cluster via gcloud, REST API, gRPC, or the Google Cloud console, you must specify the desired region.\u003c/p\u003e\n"],["\u003cp\u003eRegional endpoints for gRPC clients can be specified with this pattern: \u003ccode\u003e<var translate="no">REGION</var>\u003c/code\u003e-dataproc.googleapis.com.\u003c/p\u003e\n"]]],[],null,["# Regional endpoints\n\nDataproc supports regional endpoints based on\n[Compute Engine regions](/compute/docs/regions-zones#available).\nYou must specify a region, such as \"us-east1\" or \"europe-west1\",\nwhen you create a Dataproc cluster. Dataproc\nwill isolate cluster resources, such as VM instances and Cloud Storage\nand metadata storage, within a zone within the specified region.\n\nYou can optionally specify a zone within the specified cluster region, such as\n\"us-east1-a\" or \"europe-west1-b\", when you create a cluster. If you do not\nspecify the zone, [Dataproc Auto Zone Placement](/dataproc/docs/concepts/auto-zone)\nwill choose a zone within your specified cluster region to locate clusters\nresources.\n\nThe regional namespace corresponds to the `/regions/`\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\nsegment of Dataproc resource URIs (see, for example, the\ncluster\n[`networkUri`](/dataproc/docs/reference/rest/v1/ClusterConfig#GceClusterConfig.FIELDS.network_uri)).\n\nRegional endpoint semantics\n---------------------------\n\nRegional endpoint names follow a standard naming convention based on\n[Compute Engine regions](/compute/docs/regions-zones/regions-zones#available).\nFor example, the name for the Central US region is `us-central1`, and the name\nof the Western Europe region is `europe-west1`. Run the `gcloud compute regions list`\ncommand to see a listing of available regions.\n| **Note:** When new regions are added to Compute Engine, they become available for use with Dataproc.\n\nCreate a cluster\n----------------\n\n### gcloud\n\nWhen you create a cluster, specify a region using the required\n`--region` flag. \n\n```\ngcloud dataproc clusters create CLUSTER_NAME \\\n --region=REGION \\\n other args ...\n```\n\n### REST API\n\nUse the `REGION` URL parameter in a\n[clusters.create](/dataproc/docs/reference/rest/v1/projects.regions.clusters/create)\nrequest to specify the cluster region.\n\n### gRPC\n\nSet the client transport address to the regional endpoint\nusing the following pattern:\n\n\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`-dataproc.googleapis.com`\n\n**Python ([google-cloud-python](https://github.com/googleapis/python-dataproc)) example:** \n\n```python\nfrom google.cloud import dataproc_v1\nfrom google.cloud.dataproc_v1.gapic.transports import cluster_controller_grpc_transport\n\ntransport = cluster_controller_grpc_transport.ClusterControllerGrpcTransport(\n address='us-central1-dataproc.googleapis.com:443')\nclient = dataproc_v1.ClusterControllerClient(transport)\n\nproject_id = 'my-project'\nregion = 'us-central1'\ncluster = {...}\n```\n\n**Java ([google-cloud-java](https://github.com/googleapis/google-cloud-java/tree/master/google-cloud-clients/google-cloud-dataproc)) example:** \n\n```verilog\nClusterControllerSettings settings =\n ClusterControllerSettings.newBuilder()\n .setEndpoint(\"us-central1-dataproc.googleapis.com:443\")\n .build();\n try (ClusterControllerClient clusterControllerClient = ClusterControllerClient.create(settings)) {\n String projectId = \"my-project\";\n String region = \"us-central1\";\n Cluster cluster = Cluster.newBuilder().build();\n Cluster response =\n clusterControllerClient.createClusterAsync(projectId, region, cluster).get();\n }\n```\n\n### Console\n\nSpecify a Dataproc region in the Location section of the\n**Set up cluster** panel on the Dataproc\n[**Create a cluster**](https://console.cloud.google.com/dataproc/clustersAdd) page\nin the Google Cloud console.\n\n\nWhat's next\n-----------\n\n- [Geography and Regions](/docs/geography-and-regions)\n- [Compute Engine Engine→Regions and Zones](/compute/docs/regions-zones/regions-zones)\n- [Compute Engine→Global, Regional, and Zonal Resources](/compute/docs/regions-zones/global-regional-zonal-resources)\n- [Dataproc Auto Zone Placement](/dataproc/docs/concepts/auto-zone)"]]