에이전트를 만들 때 리전을 에이전트의 위치로 지정해야 합니다.
에이전트로 전송된 요청은 이 리전의 Google 서비스로 처리되며 대화형 에이전트(Dialogflow CX)가 저장 데이터를 실제로 지리적인 리전 또는 위치 내에 유지합니다.
최상의 성능을 위해서는 서비스 및 최종 사용자와 가까운 리전을 선택해야 합니다.
에이전트를 만든 후에는 위치를 변경할 수 없습니다.
에이전트 위치를 변경하려면 다른 위치의 새 에이전트로 내보내기 및 복원해야 합니다.
각 위치에는 프로젝트 전체에 적용되는 관련 설정이 있습니다.
대부분의 경우 이러한 위치 설정을 수정할 필요가 없으며 기본 설정이 적합합니다.
시스템에 고객 관리 암호화 키(주로 정부 기관 또는 규제가 적용되는 업계에 필요)가 필요한 경우 위치 설정에 대해 자세히 알아보세요.
대화형 에이전트(Dialogflow CX)는 에이전트 위치에 대해 다음 리전을 지원합니다.
데이터 스토어 에이전트는 다음 표에 나열된 리전에서도 지원되지만 데이터 스토어에서 사용되는 리전 ID는 에이전트 리전과 약간 다릅니다 (표 참고).
데이터 스토어 리전 ID 열에 값이 입력된 모든 리전은 Vertex AI Conversation의 데이터 스토어 에이전트에서 지원됩니다.
시스템에 고객 관리 암호화 키(정부 기관 또는 규정이 적용되는 업계에 필요)가 필요한 경우 위치 설정을 사용하여 이 기능을 구성할 수 있습니다.
위치 설정은 프로젝트 전체에 공유되고 고유한 위치마다 고유한 위치 설정이 있습니다.
프로젝트에 특정 위치에 대한 설정을 구성한 후에는 변경 불가능한 dialogflow.googleapis.com/LocationSettings리소스가 생성되며 해당 위치의 설정을 변경할 수 없습니다. 이러한 설정을 변경하거나 리소스를 삭제해야 하는 경우 새 프로젝트를 만들어야 합니다.
[[["이해하기 쉬움","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-08-18(UTC)"],[[["\u003cp\u003eWhen creating an agent, you must specify a region, which determines where Google services handle requests and where data-at-rest is physically located, and this region cannot be changed after creation.\u003c/p\u003e\n"],["\u003cp\u003eChoosing a region that is geographically close to your services and end-users is recommended for optimal performance.\u003c/p\u003e\n"],["\u003cp\u003eLocation settings can be used to configure customer-managed encryption keys, but these settings are project-wide and immutable once set for a specific location.\u003c/p\u003e\n"],["\u003cp\u003eDifferent telephony integrations, languages, and the APIs Explorer may have varying levels of region support or may be limited to specific regions, such as the global region.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eglobal\u003c/code\u003e region is available but may have higher latency outside the US, thus a specific region is preferred; the AI/ML Data Location commitment is limited to the US and EU regions.\u003c/p\u003e\n"]]],[],null,["# Regionalization and location settings\n\nWhen you create an agent,\nyou must specify a\n\nregion\n\nas the agent's location.\nRequests sent to your agent are handled by Google services in this region and\nConversational Agents (Dialogflow CX) keeps [data-at-rest](https://en.wikipedia.org/wiki/Data_at_rest)\nphysically within the geographical [region or location](/about/locations).\nFor the best performance,\nyou should choose a region that is near your services and end-users.\n\nOnce an agent is created, its location cannot change.\nIn order to change an agent's location,\nyou must\n[export and restore](/dialogflow/cx/docs/concept/agent#export)\nto a new agent with a different location.\n\nEach location has associated settings that apply across your project.\nIn most cases, you do not need to edit these location settings,\nand the default settings will work well.\nIf your system requires\n[customer-managed encryption keys](/dialogflow/cx/docs/concept/cmek) (often required by government entities or regulated industries),\nread more about\n[location settings](/dialogflow/cx/docs/concept/region#location-settings).\n\nLimitations\n-----------\n\nThe following limitations apply:\n\n- Region support for different telephony integrations may vary. Check\n documentation for each integration.\n\n- System entity support differs for each\n [language](/dialogflow/cx/docs/reference/language).\n See the\n [system entity limitations](/dialogflow/cx/docs/reference/system-entities#limits)\n for details.\n\n- The\n [APIs Explorer](https://developers.google.com/explorer-help/),\n found on many\n [REST reference documents](/dialogflow/cx/docs/reference/rest),\n only supports the `global` region for API calls.\n\nAvailable regions\n-----------------\n\n| **Important:** The \"[AI/ML Data Location](/terms/data-residency)\" (Data Residency for ML Processing) commitment is only supported in the locations within the US and EU. ML Processing for generative models may occur within any location in the multi-regions when requests are made to regional APIs included within a multi-region. For more details, see the [Vertex AI documentation](/vertex-ai/generative-ai/docs/learn/locations).\n\nConversational Agents (Dialogflow CX) supports the following regions for agent location.\n[Data store agents](/dialogflow/cx/docs/concept/data-store-agent)\nare also supported in the regions listed in the following table, but the region\nIDs used by data stores differ slightly from the agent regions (as listed).\nAll regions with a value entered in the **Data store region ID** column\nare supported by data store agents in [Vertex AI Conversation](/generative-ai-app-builder/docs/agent-intro).\n\nYou can read more about regions used by Google Cloud at\n[Google Cloud regions](/about/locations)\nand\n[Google Cloud geography and regions](/docs/geography-and-regions).\n\nLocation settings\n-----------------\n\nIf your system requires\n[customer-managed encryption keys](/dialogflow/cx/docs/concept/cmek) (often required by government entities or regulated industries),\nyou can use location settings to configure this feature.\n\nLocation settings are shared across the project,\nand each unique location has its own location settings.\n\nOnce settings for a specific location are configured for a project, an immutable\n`dialogflow.googleapis.com/LocationSettings`\n[resource](/asset-inventory/docs/asset-names) is created, and the settings\ncannot change for that location. If you need to change these settings or to\ndelete the resource, you must create a new project.\n\nIf you need to allow your organization's developers to configure agents only in\nspecific locations, you can [set up an organization policy that includes a\nresource locations\nconstraint](/resource-manager/docs/organization-policy/defining-locations-supported-services#dialogflow).\n\nIf you create an agent without editing the location settings,\nthe default settings will be configured for that location,\nand they cannot be changed for the project.\nIn addition, once an agent is created, its location cannot change.\nIn order to change an agent's location,\nyou must\n[export and restore](/dialogflow/cx/docs/concept/agent#export)\nto a new agent with a different location.\n\nThe following location settings are available:\n\n- **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](/dialogflow/cx/docs/concept/cmek) feature to change this setting.\n\nYou can configure location settings in two ways:\n\n- Click **Location settings** from the [agent selector interface](/dialogflow/cx/docs/concept/console#agent).\n- Click the **Edit** button next to the **Location** drop down when [creating an agent](/dialogflow/cx/docs/concept/agent#create).\n\n| **Note:** Currently, you cannot update location settings with the API.\n\nSpecify a region with the API\n-----------------------------\n\nYou must specify a region for all API requests.\n\nFor REST calls, you must do both of the following:\n\n- Provide the region ID for the `location` URL path parameter.\n\n- For the `global` region, use `dialogflow.googleapis.com` for the\n hostname. For all other regions, use `[region-id]-dialogflow.googleapis.com`\n for the hostname.\n\nFor example:\n\n- `dialogflow.googleapis.com/projects/{PROJECT_ID}/locations/global/agents/{AGENT_ID}`\n\n- `us-central1-dialogflow.googleapis.com/projects/{PROJECT_ID}/locations/us-central1/agents/{AGENT_ID}`\n\nFor client libraries, see the\n[client library documentation](/dialogflow/cx/docs/reference/library/overview)\nfor a region configuration option.\n\nYou can find examples in the\n[API quickstart](/dialogflow/cx/docs/quick/api).\n| **Caution:** As described in the [setup documentation](/dialogflow/cx/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/cx/docs/concept/logging)\nto control the region in which logs are stored."]]
