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 and Dialogflow keeps data-at-rest physically within the geographical region or location. 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 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 global region. Support for other regions will be added soon.
  • The Allow ML to correct spelling setting is currently available in the following regions: us-central1, us-east1, us-west1, global.
  • Some system entities are currently available only in the following regions: us-central1, us-east1, us-west1, global. Consider creating custom entities or using @sys.any with form parameters.

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
Americas Oregon us-west1
Europe Belgium europe-west1
Europe London europe-west2
Asia Pacific Sydney australia-southeast1
Asia Pacific Tokyo asia-northeast1
Asia Pacific Mumbai asia-south1
Global Global serving, data-at-rest in US global (preferred), us, or no region (default)

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 customer-managed encryption keys (often required by government entities or regulated industries), you can use location settings to configure this feature.

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.

You can configure location settings in two ways:

Specify a region with the API

You must specify a region for all API requests.

For REST calls, you must do both of the following:

  • Provide the region ID for the location URL path parameter.

  • 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.