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.
The following limitations apply:
- Region support for different telephony integrations may vary. Check documentation for each integration.
- The Allow ML to correct spelling setting
is currently available in the following regions:
- Some system entities are
currently available only in the following regions:
global. Consider creating custom entities or using
@sys.anywith form parameters.
Sentiment analysis is currently available in the following regions:
asia-southeast1(en, fr, it, de, es only)
europe-west1(en, fr, it, de, es only)
europe-west2(en, fr, it, de, es only)
europe-west3(en, fr, it, de, es only)
northamerica-northeast1(en, fr, it, de, es only)
Dialogflow CX supports the following regions for agent location:
|Country grouping||Geographical location||Region ID|
|Global||Global serving, data-at-rest in US||
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:
- Click Location settings from the agent selector interface.
- Click the Edit button next to the Location drop down when creating an agent.
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
locationURL path parameter.
[region-id]-dialogflow.googleapis.comfor the hostname.
For client libraries, see the client library documentation for a region configuration option.
You can find examples in the API quickstart.
See the Cloud logging guide to control the region in which logs are stored.