如果您嘗試使用設定為僅將寫入作業傳送至叢集 (使用單叢集轉送) 的應用程式設定檔，或是傳送至與端點位於不同區域的叢集 (使用多叢集轉送)，系統會顯示先決條件失敗錯誤訊息 There are no clusters accessible through this app profile and the
REGION_NAME endpoint. 如要進一步瞭解叢集轉送，請參閱「轉送政策」。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-09 (世界標準時間)。"],[[["\u003cp\u003eBigtable locational endpoints ensure data is stored and processed within a specific geographic region for enhanced security and compliance, unlike the global endpoint which can store and route data to any region with a cluster.\u003c/p\u003e\n"],["\u003cp\u003eUsing locational endpoints requires creating an instance with at least one cluster in the desired region and configuring app profiles to route requests to a cluster within that specific region.\u003c/p\u003e\n"],["\u003cp\u003eLocational endpoints restrict requests to clusters within the specified region, impacting high availability as it prevents automatic failover to clusters outside the region, meaning it does not support the highest monthly uptime percentage offered by Bigtable.\u003c/p\u003e\n"],["\u003cp\u003eThe format for a Bigtable locational endpoint is \u003ccode\u003eREGION-bigtable.googleapis.com\u003c/code\u003e, and it can be configured via the Google Cloud CLI or the \u003ccode\u003ecbt\u003c/code\u003e CLI, while switching back to the global endpoint can also be done through these tools.\u003c/p\u003e\n"]]],[],null,["Locational endpoints\n\nThis page describes Bigtable locational endpoints, explains what you\nshould consider before using them, and shows how to set an endpoint using the\nGoogle Cloud CLI.\n\nYou can use either a global or locational service endpoint to send requests to\nBigtable. Locational endpoints for Bigtable ensure\nthat an instance's data is stored and processed in the [Bigtable\nregion](/bigtable/docs/locations) where the data resides. You might need to use\nlocational endpoints for Bigtable in a specific geographic region\nin support of your project's security and compliance needs.\n\nBefore you read this document, you should be familiar with [Instances, clusters,\nand nodes](/bigtable/docs/instances-clusters-nodes) and [App\nprofiles](/bigtable/docs/app-profiles).\n\nKey concepts include the following:\n\n- **Service endpoint:** A [*service\n endpoint*](/apis/design/glossary#api_service_endpoint) is a base URL that\n specifies the network address of an API service. Bigtable has\n both global and locational endpoints.\n\n- **Global endpoint:** A *global endpoint* lets Bigtable store\n and route the data in a Bigtable instance to any region that\n contains one of the instance's clusters. The global endpoint for the\n Cloud Bigtable API (Data API) is `bigtable.googleapis.com`. The default Data\n API endpoint accesses the global endpoint.\n\n- **Locational endpoint** A *locational endpoint* enforces locational\n restrictions, ensuring that data is stored and processed in a specified\n region.\n\nYou can use locational endpoints only with the Cloud Bigtable API (Data\nAPI). Locational endpoints are not supported for the Cloud Bigtable Admin API.\n\nWhen to use locational endpoints\n\nThe benefit of using a Bigtable locational endpoint over a global\nendpoint is that the locational endpoint provides locational isolation and\nprotection to meet security, compliance, and regulatory requirements.\n\nUse a locational endpoint if your data location must be restricted and\ncontrolled to comply with regulatory requirements.\n\nUse the global endpoint if you don't have strict locational restriction\nrequirements.\n\nConsiderations when using a locational endpoint\n\nConsider the following factors when you use a locational endpoint.\n\nCluster locations\n\nBefore you can use a locational endpoint, you must create an instance with at\nleast one cluster in the region where you want to isolate your data.\nBigtable locational endpoints are available in all\n[Bigtable locations](/bigtable/docs/locations).\n\nYou can only use a locational endpoint that belongs to the region where you want\nto isolate your data. For example, you can't use\n`us-west1-bigtable.googleapis.com` to serve requests if the cluster that you are\naccessing is in the `us-central1` region.\n\nIf you attempt to use a locational\nendpoint to access a cluster in a different region, the request is rejected with\na `FAILED_PRECONDITION` error with a message noting that no clusters are\naccessible using the specified cluster and endpoint. For example, a request sent\nto `us-west1-bigtable.googleapis.com` for clusters in `us-central1` fails with\n`FAILED_PRECONDITION`. For more information on `FAILED_PRECONDITION`, see\n[Bigtable status codes](/bigtable/docs/status-codes).\n\nApp profiles\n\nAfter you set a locational endpoint, you must use an app profile that is\nconfigured to route requests to a cluster in the endpoint's region.\n\nIf you attempt to use an app profile configured to send writes only to a\ncluster (using single-cluster routing) or clusters in a different region from\nthe endpoint (using multi-cluster routing), you receive the failed precondition\nerror message `There are no clusters accessible through this app profile and the\n`\u003cvar translate=\"no\"\u003eREGION_NAME\u003c/var\u003e` endpoint.` For more information on cluster\nrouting, see [Routing policy](/bigtable/docs/app-profiles#routing).\n\nIf you use an app profile that is configured to route to any cluster in an\ninstance for high availability (HA), and you also use a locational endpoint, the\nlocational endpoint ensures that all requests are routed only to clusters in its\nregion, even if the instance has clusters in other regions. [Automatic\nfailover](/bigtable/docs/failovers#automatic) is constrained, so requests\nare only served from clusters in the region of the endpoint.\n\nConsider an example where you are sending requests using an app profile\nconfigured for multi-cluster routing to instance that has clusters in\n`us-west1-a` (Oregon), `us-west1-b` (Oregon), and `us-central1-a` (Iowa). If you\nsend these requests to the `us-central1-bigtable.googleapis.com` locational\nendpoint, then all requests are served by `us-central1-a` even if you don't\nreconfigure the app profile. Requests that can't be served by `us-central1-a`\nfail.\n\nReplication\n\nLocational endpoints don't affect or prevent replication. If you configure a\nlocational endpoint in Region A, and then you add a cluster to your instance in\nRegion B, your data is replicated to Region B just like it is if you use the\nglobal endpoint.\n\nTo avoid replicating data to another region, create clusters only in\nthe intended region.\n\nTo prevent users in your organization from adding clusters\noutside the endpoint region, you can set an organization policy that uses\nlocation constraints. To learn more, see [Restricting resource\nlocations](/resource-manager/docs/organization-policy/defining-locations).\n\nAvailability\n\nWhen you use locational endpoints, you can't configure Bigtable to\nachieve a monthly uptime percentage of \\\u003e=99.999%. A monthly uptime of \\\u003e=99.999%\nrequires [automatic failover](/bigtable/docs/managing-failovers#automatic) of\nrequests over locational boundaries, which a locational endpoint prevents\nbecause it confines all requests to a single region. For more information on\nmonthly uptime percentages, see the [Bigtable service level agreement\n(SLA)](/bigtable/sla).\n\nLocational endpoint semantics\n\nThe first segment of a Bigtable locational endpoint name is the\nGoogle Cloud region name. A locational endpoint follows the format\n\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`-bigtable.googleapis.com`, where\n\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is a region name, such as\n`northamerica-northeast2`.\n\nFor example, if you want to isolate your data in the Iowa region, because the\nregion name for Iowa is `us-central1`, the locational endpoint URL for the Iowa\nregion is `us-central1-bigtable.googleapis.com`. For a list of available\nregions, see [Bigtable locations](/bigtable/docs/locations).\n\nSpecify a locational endpoint\n\nYou can specify a Bigtable locational endpoint using the\nGoogle Cloud CLI, the `cbt` CLI, or the [Cloud Bigtable client\nlibraries](/bigtable/docs/reference/libraries). \n\ngcloud\n\nTo specify a locational endpoint and override the global endpoint using the\ngcloud CLI, run the following command: \n\n gcloud config set api_endpoint_overrides/bigtable https://\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e-bigtable.googleapis.com/\n\nReplace \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region where you want to set a\nlocational endpoint, such as `us-central1` or `europe-west1`.\n\nFor example, to configure the locational endpoint as `us-central1`, run the\nfollowing command: \n\n gcloud config set api_endpoint_overrides/bigtable https://us-central1-bigtable.googleapis.com/\n\ncbt\n\nTo specify a locational endpoint and override the global endpoint using the `cbt` CLI,\nyou can use the `--data-endpoint` option in your request, or you can add the\nfollowing to your \\~/.cbtrc file. For additional information on creating a\n\\~/.cbtrc file, see the [cbt CLI reference](/bigtable/docs/cbt-reference). \n\n data-endpoint = https://\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e-bigtable.googleapis.com/\n\nReplace \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region where you want to set a\nlocational endpoint, such as `us-central1` or `europe-west1`.\n\nFor example, to configure the locational endpoint as `us-central1` add this to\nthe \\~/.cbtrc file: \n\n data-endpoint = https://us-central1-bigtable.googleapis.com/\n\nSpecify the global endpoint \n\ngcloud\n\nTo reconfigure a locational endpoint to the global endpoint, run this command: \n\n gcloud config unset api_endpoint_overrides/bigtable\n\ncbt\n\nTo specify the global sendpoint, send your request without using the\n`--data-endpoint` option. If you previously added a `data-endpoint` line\nto your \\~/.cbtrc file, delete it.\n\nRestrict global API endpoint usage\n\nTo help enforce the use of locational endpoints, use the\n`constraints/gcp.restrictEndpointUsage` organization policy constraint to block\nrequests to the global API endpoint. For more information, see\n[Restricting endpoint usage](/assured-workloads/docs/restrict-endpoint-usage).\n\nWhat's next\n\n- [Review access control with IAM.](/bigtable/docs/access-control)\n- [Learn how to create and manage tags.](/bigtable/docs/tags)\n- [View the regions where Bigtable supports regional\n endpoints.](/vpc/docs/about-accessing-regional-google-apis-endpoints#supported)"]]
