Regionalization and location settings

When you create an agent, you must specify a region as the agent's location. Requests sent to your agent are handled by Google services in this region. For the best performance, you should choose a region that is near your services and end-users.

Once an agent is created, its location cannot change. In order to change an agent's location, you must export and restore to a new agent with a different location.

Each location has associated settings that apply across your project. In most cases, you do not need to edit these location settings, and the default settings will work well. If your system requires data residency guarantees or customer-managed encryption keys (often required by government entities or regulated industries), read more about location settings.

Limitations

The following limitations apply:

  • Telephony integrations currently only support the deprecated global region. Support for other regions will be added soon.

Available regions

Dialogflow CX supports the following regions for agent location:

Country grouping Geographical location Region ID
Americas Iowa us-central1
Americas Montréal northamerica-northeast1
Americas South Carolina us-east1
Europe Belgium europe-west1
Europe London europe-west2
Asia Pacific Sydney australia-southeast1
Asia Pacific Tokyo asia-northeast1

You can read more about regions used by Google Cloud at Google Cloud regions and Google Cloud geography and regions.

Location settings

If your system requires data residency guarantees or customer-managed encryption keys (often required by government entities or regulated industries), you can use location settings to configure these features.

Location settings are shared across the project, and each unique location has its own location settings. Once settings for a specific location are configured for a project, the settings cannot change for that location. If you need to change these settings, you must create a new project.

If you create an agent without editing the location settings, the default settings will be configured for that location, and they cannot be changed for the project. In addition, once an agent is created, its location cannot change. In order to change an agent's location, you must export and restore to a new agent with a different location.

The following location settings are available:

  • Encryption: This setting controls whether Google-managed or customer-managed encryption keys are used to protect data. The default is Google-managed. You must request access (by contacting your Google representative) to the customer-managed encryption keys feature to change this setting.
  • Data residency compliant: This controls whether data residency guarantees are required for the location. For U.S. regions, this setting defaults to false, and can be changed to true. For other regions, the setting is set to true, and it cannot be changed. There are some features that are not implemented yet with a data residency guarantee, so these features are unavailable if you enable this setting. Disabling data residency compliance enables these features. The Dialogflow team is working on adding data residency support for all features, so this setting will be removed in the future.

You can configure location settings in two ways:

Data residency guarantees

All Dialogflow CX agent data-at-rest and data-in-use is guaranteed to reside only in the specified region, with the following exceptions:

Data type Data-at-rest residency guaranteed Data-in-use residency guaranteed
Resource identifiers (Agent.name, Flow.name, Page.name, etc.) No No
Resource display names (Agent.display_name, Flow.display_name, Page.display_name, etc.) No No
Resource descriptions (Agent.description, Flow.description, etc.) No No
Voice session audio data Yes No
Advanced NLU requests Yes Yes for us-central1, us-east1 and europe-west1. No for other regions.
Sentiment requests Sentiment is only available for us-central1 or us-east1 customers who disable Data residency compliant Sentiment is only available for us-central1 or us-east1 customers who disable Data residency compliant
Spelling correction Spelling correction is only available for us-central1 or us-east1 customers who disable Data residency compliant Spelling correction is only available for us-central1 or us-east1 customers who disable Data residency compliant
System entities Some system entities are unavailable when Data residency compliant is enabled. See the reference. Some system entities are unavailable when Data residency compliant is enabled. See the reference.

In addition, if you take any of the following actions, data may cross regions:

  • Accessing the Dialogflow Console or the API from a geographical location outside of the specified region.
  • Providing data in a Cloud storage bucket that has a different region than your agent.
  • Providing a webhook service that has a geographical location outside of the specified region.

Specify a region with the API

You must specify a region for all API requests.

For REST calls, provide the region ID for the location URL path parameter, and use [region-id]-dialogflow.googleapis.com for the hostname. For example: us-central1-dialogflow.googleapis.com/projects/{PROJECT_ID}/locations/us-central1/agents/{AGENT_ID}.

For client libraries, see the client library documentation for a region configuration option.

You can find examples in the API quickstart.

Cloud logging

See the Cloud logging guide to control the region in which logs are stored.