[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eDialogflow offers data residency, allowing you to keep your data-at-rest physically within a specified geographical region, and it does not get replicated outside of it.\u003c/p\u003e\n"],["\u003cp\u003eSpecifying a region can be essential to fulfill regulatory or policy requirements and may improve network latency for your customers.\u003c/p\u003e\n"],["\u003cp\u003eData-at-rest encompasses various types of data such as agent resources, settings, query history, and task results, whereas data-in-use and data-in-transit are not subjected to regionalization and data residency.\u003c/p\u003e\n"],["\u003cp\u003eDialogflow supports multiple regions including Europe, Asia Pacific, and a global region, each with its own unique region ID that must be specified when using the API.\u003c/p\u003e\n"],["\u003cp\u003eWhen using the console or API to access or create agents, you have to specify the desired region as each agent has an immutable region that is set upon creation, with one agent per region allowed for each Google Cloud project.\u003c/p\u003e\n"]]],[],null,["# Regionalization and data residency\n\nDialogflow provides\n[data residency](https://cloud.google.com/blog/products/identity-security/meet-data-residency-requirements-with-google-cloud)\nto keep your\n[data-at-rest](#data-at-rest)\nphysically within a geographical\n[region or location](/about/locations).\nWhen a region is specified,\nyour data-at-rest is not replicated outside the region.\nPricing is the same for all regions.\n\nRegions are used for the following reasons:\n\n- Your system may have regulatory or policy requirements that govern where your data must reside.\n- Your network latencies may be improved when the data is in the same region as your customers. For example, If UK customers use `europe-west2`, they can expect better latency.\n\n| **Note:** Dialogflow regionalization and data residency does not apply to [data-in-use](https://en.wikipedia.org/wiki/Data_in_use) or [data-in-transit](https://en.wikipedia.org/wiki/Data_in_transit).\n\nData-at-rest\n------------\n\nAll Dialogflow developer user and end-user data is included in\n[data-at-rest](https://en.wikipedia.org/wiki/Data_at_rest).\nFor example:\n\n- All agent resources set with console or API (intents, entities, etc.)\n- All agent settings set with console or API\n- Query history\n- Validation results\n- Model creation tasks\n- Training tasks\n- Long-running operation tasks\n\nAvailable regions\n-----------------\n\nDialogflow provides the following regions:\n\nSelect a region with the console\n--------------------------------\n\nThe top left area of the [Dialogflow ES console](https://dialogflow.cloud.google.com)\nhas a drop-down for region selection.\nEvery agent has an immutable region that is specified upon creation.\nWhen you select a region from the console,\nyou can only list or create agents for the selected region.\nThe default region is `global`.\n| **Note:** You can create one agent per region for a Google Cloud project.\n\nSelect a region with the API\n----------------------------\n\nIf your agent was created in a non-default region,\nyou must specify that region when calling the API\nfor either design-time or runtime requests.\n\nTo provide a region, you supply a `location` parameter to API requests.\nFor REST calls, do both of the following:\n\n- Provide the `location` URL path parameter. For the `global` region, use `global`.\n- For the `global` region, use `dialogflow.googleapis.com` for the hostname. For all other regions, use `[REGION_ID]-dialogflow.googleapis.com` for the hostname.\n\nExamples:\n\n- `https://dialogflow.googleapis.com/v2/projects/PROJECT/locations/global/agents/`\n- `https://asia-northeast1-dialogflow.googleapis.com/v2/projects/PROJECT/locations/asia-northeast1/agents/`\n\nFor client libraries, see the\n[client library documentation](/dialogflow/docs/reference/libraries/overview).\nYou need to do the following:\n\n- Set the Dialogflow service endpoint to one of the following:\n\n ```\n dialogflow.googleapis.com:443\n REGION_ID-dialogflow.googleapis.com:443\n ```\n- Set the session name to:\n\n ```\n projects/PROJECT_ID/locations/REGION_ID/agent/sessions/SESSION_ID\n ```\n\n| **Caution:** As described in the [setup documentation](/dialogflow/es/docs/quick/setup#auth-env), you should use the `GOOGLE_APPLICATION_CREDENTIALS` environment variable to provide your client libraries with credentials. However, if you need to manually provide a credentials file in your code, you need to take one additional step when calling a regionalized endpoint. Set the scope to `https://www.googleapis.com/auth/cloud-platform` when generating your authentication credentials. For example, this is accomplished in Java when creating a `GoogleCredentials` object: \n|\n| ```\n| GoogleCredentials.fromStream(new FileInputStream(\"credential_file\"))\n| .createScoped(\"https://www.googleapis.com/auth/cloud-platform\")\n| \n| ```\n\nCloud logging\n-------------\n\nSee the\n[Cloud logging guide](/dialogflow/es/docs/logging)\nto control the region in which logs are stored.\n\nLimitations\n-----------\n\nWhen a non-default region is selected in the Dialogflow Console,\nthe following features are not available:\n\n- [Integrations](/dialogflow/es/docs/integrations)\n- [Knowledge Connectors](/dialogflow/es/docs/knowledge-connectors)\n- [Prebuilt Agents](/dialogflow/es/docs/agents-prebuilt)\n- [Small Talk](/dialogflow/es/docs/agents-small-talk)\n- [Training tool](/dialogflow/es/docs/training#tool)\n\nThe\n[APIs Explorer](https://developers.google.com/explorer-help/),\nfound on many\n[REST reference documents](/dialogflow/es/docs/reference/rest),\nonly supports the `global` region for API calls."]]
