A dedicated VPC provides enhanced security and isolation for your Hologres instance. We recommend that you disable your existing VPC endpoint and switch the network type for your Hologres instance to a dedicated VPC. This topic explains how the network switch affects DataWorks features.
Impact on DataWorks features
After switching your Hologres instance to a dedicated VPC, note the following dependencies between DataWorks modules and exclusive resource groups:
Affected feature | Module | Exclusive resource group | Dependency |
Run ad hoc Hologres compute tasks | Data Studio | exclusive resource group for scheduling | Required: exclusive resource group for scheduling |
Run Hologres data integration tasks | Data Studio, Data Integration | exclusive resource group for scheduling, exclusive resource group for Data Integration |
|
Run scheduled Hologres compute tasks | Operation Center | exclusive resource group for scheduling | Required: exclusive resource group for scheduling |
Run scheduled Hologres data integration tasks | Operation Center | exclusive resource group for scheduling, exclusive resource group for Data Integration |
|
Run SQL query tasks | Data Analysis | exclusive resource group for scheduling | Required: exclusive resource group for scheduling |
Metadata collection | Data Map | exclusive resource group for scheduling | Required for regions other than China (Shanghai), China (Hangzhou), China (Shenzhen), China (Beijing), China (Chengdu), China (Zhangjiakou), US (Virginia), China East 2 Finance, China (Hong Kong), US (Silicon Valley), and Malaysia (Kuala Lumpur): exclusive resource group for scheduling and exclusive resource group for Data Integration. |
Debug Data Service APIs online | Data Service | exclusive resource group for Data Service | Recommended: exclusive resource group for Data Service |
Access online Data Service APIs | Data Service | exclusive resource group for Data Service | Recommended: exclusive resource group for Data Service |
We recommend that you refer to the preceding table to evaluate whether the DataWorks features you are using are affected, and then decide whether to purchase or use an exclusive resource group for scheduling, an exclusive resource group for Data Integration, or an exclusive resource group for Data Service as needed.
Step 1: Purchase and use DataWorks exclusive resource groups
If you already have DataWorks exclusive resource groups, you can reuse them.
DataWorks provides three types of exclusive resource groups: exclusive resource group for scheduling, exclusive resource group for Data Service, and exclusive resource group for Data Integration. Evaluate the necessity based on the preceding table before you decide whether to purchase and use them.
Use an exclusive resource group for scheduling
Go to DataWorks Exclusive Resources and purchase an exclusive resource group for scheduling as needed.
Associate the resource group with a workspace.
Associate a VPC.
Click Network Settings in the Actions column of the resource group. On the VPC Binding page, click Add Binding in the upper-left corner, and select the same VPC, vSwitch, and security group as those of the Hologres data source.
Add IP addresses to the allowlist.
Add the CIDR block of the associated vSwitch to the allowlist of the Hologres instance.

Test the network connectivity.
If your DataWorks workspace is in standard mode, you can test the network connectivity for the development environment and the production environment separately:
Development environment: In DataStudio, create a Hologres ad hoc query. Click Advanced Options and select the associated exclusive resource group to run the task. If the task runs successfully, the network is connected.
Production environment: In DataStudio, create a Hologres compute task and a data integration task for testing purposes. Submit and deploy both tasks to Operation and Maintenance Center. In Operation and Maintenance Center, filter out these tasks and run the Test operation during off-peak hours. If the tasks run successfully, the network is connected.
If your DataWorks workspace is in basic mode, you only need to follow the development environment testing procedure described above.
Switch to the exclusive resource group for scheduling.
If the connectivity test in the previous step is successful, you can switch all Hologres-related tasks to the exclusive resource group for scheduling. We recommend that you perform the switch in batches during off-peak hours. For more information, see Switch the resource group for tasks.
NoteFor more information about switching the resource group for SQL queries and metadata collection, see Switch the resource group for Data Analysis and Switch the resource group for metadata collection.
Use an exclusive resource group for Data Integration
Go to DataWorks Exclusive Resources and purchase an exclusive resource group for Data Integration as needed.
Associate the resource group with a workspace.
Associate a VPC.
Click Network Settings in the Actions column of the resource group. On the VPC Binding page, click Add Binding in the upper-left corner, and select the same VPC, vSwitch, and security group as those of the Hologres data source.
Add IP addresses to the allowlist.
Add the CIDR block of the associated vSwitch to the allowlist of the Hologres instance.

Test the network connectivity.
Before you run a synchronization task, you can test the connectivity when you configure the task.
Use an exclusive resource group for Data Service
Go to DataWorks Exclusive Resources and purchase an exclusive resource group for Data Service as needed.
Associate the resource group with a workspace.
View the IPv4 CIDR block of the vSwitch for the exclusive resource group for Data Service.
Go to the VPC console > vSwitch. Find the vSwitch that you selected when you purchased the exclusive resource group for Data Service, and view and copy the IPv4 CIDR block.
Add IP addresses to the allowlist.
Add the CIDR block of the vSwitch for the exclusive resource group for Data Service to the allowlist of the Hologres instance:
Switch the resource group and test the network connectivity.
Go to Data Services. Create an API or edit an existing API. In the right-side navigation pane of the API editing page, in the Resource Group for DataService Studio section, select Exclusive Resource Group for DataService Studio and the target resource group, and then click Test to test the API. To test the network connectivity of an online API, deploy the API first, and then call and debug the API by using the endpoint.
Step 2: Release or switch the existing VPC
Release or switch the existing VPC in Hologres. For more information, see Network configuration for Hologres.
Tasks that are running in DataWorks will fail during the Hologres network switch. We recommend that you perform the switch during off-peak hours.