All Products
Search
Document Center

DataWorks:Create and use exclusive resource groups for Data Integration

Last Updated:Jun 20, 2026

You can use an exclusive resource group for Data Integration in DataWorks to allocate dedicated computing resources for data synchronization tasks, which improves task efficiency and stability. After purchasing an exclusive resource group, you must configure its network binding and whitelist settings before use. This topic describes how to purchase and use an exclusive resource group for Data Integration.

Important

If you had not activated DataWorks in any region before June 10, 2024, you can only purchase and use serverless resource groups after activation. You cannot purchase or use legacy resource groups. Existing DataWorks users who need to switch to serverless resource groups can see Switch from legacy resource groups.

DataWorks no longer recommends exclusive resource groups for Data Integration

DataWorks no longer recommends exclusive resource groups for Data Integration. We recommend that you use serverless resource groups. A serverless resource group covers the core capabilities of legacy resource groups (exclusive resource groups for scheduling, exclusive resource groups for Data Integration, exclusive resource groups for Data Service, and shared resource groups). A single serverless resource group can handle data synchronization, task scheduling and execution, and API operation calls and management.

Prerequisites

Before you begin, understand the specifications, concurrency limits, and billing methods for exclusive resource groups for Data Integration. Plan the resource specifications and subscription duration based on your business requirements. For more information, see Billing for an exclusive resource group for Data Integration.

Notes

Exclusive resource groups for Data Integration support data synchronization in complex network environments. These environments include cross-cloud setups such as Finance Cloud and Gov Cloud, scenarios that involve multiple Alibaba Cloud accounts, and on-premises data centers. To run data synchronization tasks, you must make sure that the resource group can access the networks where your source and destination data sources reside without being blocked by a whitelist or other access controls. If network connectivity is not established, data synchronization tasks fail. For more information about network connectivity solutions and whitelist configurations between an exclusive resource group and data sources, see Billing for an exclusive resource group for Data Integration.

Note
  • If you do not need to connect to a database instance and your only goal is to reduce task latency caused by resource contention in a public resource group, you can skip the network configuration steps described in this topic. You can purchase an exclusive resource group for Data Integration in any zone and use it without configuring network settings.

  • By default, an exclusive resource group for Data Integration accesses the public internet over a shared bandwidth. This setup does not guarantee the quality of the public network connection. If your tasks require a stable internet connection, use a Serverless resource group.

Limitations

  • Only users with the AliyunBSSOrderAccess and AliyunDataWorksFullAccess permissions can purchase resource groups.

  • Only a workspace administrator can bind a resource group to a workspace or modify the binding.

  • For more information about the permissions on the resource group page, see Permission management for resource groups.

  • For more information about how to create a custom policy and grant permissions, see Create a custom policy (Optional).

  • A 4-core 8-GB exclusive resource group for Data Integration can be bound to a maximum of two VPCs. An exclusive resource group for Data Integration with other specifications can be bound to a maximum of three VPCs.

Step 1: Purchase a resource group

DataWorks provides exclusive resource groups as a subscription-based service that must be purchased separately. Follow these steps to purchase an exclusive resource group.

Note

Only users with the AliyunBSSOrderAccess and AliyunDataWorksFullAccess permissions can purchase resource groups.

  1. Log on to the DataWorks console.

  2. In the left-side navigation pane, click Resource Group. On the Resource Groups page, click the Exclusive Resource Group tab and then click Create Resource Group for Data Integration of Old Version. On the purchase page, configure the following key parameters based on your business needs.

    Parameter

    Description

    Region and zone

    Select the region where you want to use this exclusive resource group.

    Note

    An exclusive resource group for Data Integration cannot be used across regions. For example, an exclusive resource group in the China (Shanghai) region can be bound only to workspaces in the China (Shanghai) region.

    Exclusive Resource Group Type

    Select Exclusive Resources for Data Integration.

    Resource Name

    Set a name for the resource group. The name must be unique within the tenant to prevent naming conflicts.

    Note

    A tenant corresponds to a primary account. A primary account can have multiple RAM users.

    Resource notes

    Enter a brief description for the resource group.

    Billing cycle

    Exclusive resource groups are subscription-based. To ensure uninterrupted service, we recommend that you select Auto Renewal. After the resource group is created, you can also go to the Renewals page in the Alibaba Cloud console to enable or disable auto-renewal. For more information, see Billing termination.

    Configure other parameters based on your business plan.

  3. Click Buy Now and follow the on-screen instructions to complete the payment.

    After your purchase, DataWorks begins to initialize the exclusive resource group. When the status of the resource group changes to Running, it appears in the console.

    Note

    Initializing an exclusive resource group takes about 20 minutes. Wait for the status to change to Running.

After the exclusive resource group is added to the console, you must associate it with a workspace before you can select it in task configurations.

Step 2: Bind a workspace

You must bind an exclusive resource group for Data Integration to a workspace before you can select the resource group in that workspace. A single exclusive resource group can be bound to multiple workspaces, but it cannot be used across regions. For example, an exclusive resource group for Data Integration in the China (Shanghai) region can be bound only to workspaces in the China (Shanghai) region. Perform the following steps to bind a workspace:

Note

Only a workspace administrator can bind a resource group to a workspace or modify the binding.

  1. Log on to the DataWorks console.

  2. On the Resource Groups page, go to the Exclusive Resource Group tab and click Associate Workspace in the row of the target resource group.

  3. On the Associate Workspace page, find the target workspace and click Bind in its row to bind the resource group to that workspace.

Step 3: Network configuration

Bind a VPC

Exclusive resources are deployed in a DataWorks-managed VPC and are isolated from other networks. To use them, you must bind a VPC that has connectivity to your data source. This binding establishes network connectivity between the resource group and the data source. Perform the following steps to bind a VPC:

Important

A 4-core 8-GB exclusive resource group for Data Integration can be bound to a maximum of two VPCs. An exclusive resource group for Data Integration with other specifications can be bound to a maximum of three VPCs.

  1. Log on to the DataWorks console.

  2. On the Resource Groups page, go to the Exclusive Resource Group tab and click Network Settings for the target resource group.

    Before you bind a VPC, you must use a primary account to grant RAM authorization, which allows DataWorks to access your cloud resources. Only primary accounts can perform this operation. You can grant authorization on the Cloud Resource Access Authorization page or in the dialog box that appears the first time a primary account accesses the console. If a No Permission dialog box appears, it indicates that you have not authorized the default system role for DataWorks. You must use your primary account to log on to the RAM console to grant the authorization. After the authorization is complete, click Refresh and then Close. If the cloud resource access authorization page appears, select the AliyunDataWorksAccessingENIRole role and click Agree to Authorization to allow DataWorks to access your elastic network interface (ENI) resources.

  3. Bind a VPC.

    1. On the VPC Binding page, click Add Binding in the upper-left corner. In the Add VPC Binding dialog box, configure the parameters based on your network environment.

      Note

      For use cases that involve Alibaba Cloud instances or self-managed ECS instances, the network connectivity solution and configuration depend on whether the DataWorks workspace and the data source belong to the same primary account.

      Parameter

      Same account and region

      Different accounts or regions

      VPC

      If your data source and exclusive resource group are in the same Alibaba Cloud account, we recommend that you select the VPC where the data source resides.

      If they are not in the same Alibaba Cloud account, follow the instructions for the scenario where they are in different regions.

      If your data source and exclusive resource group are in different regions or under different primary accounts, select a VPC in the current account that is connected to the data source network. For example, if the data source is not in an Alibaba Cloud VPC, you can click Create VPC to create a VPC for the exclusive resource group. After the VPC is created, select the new VPC or a VPC that is already connected to the target database network.

      Note

      If the DataWorks workspace and the data source are in different regions or under different primary accounts, you must also use a service such as VPN Gateway or Express Connect to connect the VPC that is bound to the exclusive resource group to the VPC where the data source is located. You must also manually add a route that points to the target database IP address to ensure connectivity between the networks. For more information, see Network connectivity solutions.

      Zone

      Select the zone where the database is located.

      Select a zone that is already connected to the target database network.

      vSwitch

      If you select the VPC where the data source resides, we recommend that you select the vSwitch that is associated with the data source.

      Note

      After you bind any vSwitch in the data source's VPC, a route is automatically added to the entire VPC CIDR block to ensure network connectivity for the exclusive resource group for Data Integration within that VPC.

      Select a vSwitch that is already connected to the target database network. If no vSwitch is available, click Create VSwitch to create one for the exclusive resource group. After the vSwitch is created, select it here.

    2. Click Determine to complete the VPC binding.

    Note

    If the data source and the exclusive resource group are in different regions or under different primary accounts, you must bind a VPC and then add a route rule that points to the target database IP address.

  4. Optional: Configure a hostname-to-IP mapping.

    If your data source is accessed using a hostname instead of an IP address, you must configure a hostname-to-IP mapping. Otherwise, connectivity tests that use the hostname fail when you add the data source.

    1. Click Hostname-to-IP Mapping. On the page, click Add in the upper-left corner. In the Create Hostname-to-IP Mapping dialog box, configure the following parameters.

      Parameter

      Description

      IP Address

      Enter the actual IP address of the data source.

      Hostname

      Enter the host domain that the data source uses for external access. If there are multiple host domains, enter each one on a new line.

    2. To add multiple mappings, click Add again.

      Note
      • The IP address and host domains in a new mapping must not duplicate any IP address or host domain in existing mappings.

      • A single mapping supports a one-to-many relationship between an IP address and host domains. An IP address can be mapped to multiple host domains, but a host domain can be mapped to only one IP address.

Add to whitelist

If the exclusive resource group and the data source are in the same zone but network connectivity fails after you configure the VPC and vSwitch, the data source's whitelist may be blocking the connection. Add the following CIDR block or IP address to the data source's whitelist.

  • For connections over an internal network: Add the CIDR block of the vSwitch that is bound to the exclusive resource group to the data source's whitelist.

    After you bind the resource group to a VPC, go to the Resource Groups tab of the Exclusive Resource Group page and click Network Settings for the target resource group. On the VPC Binding tab, you can view the vSwitch CIDR Block.

  • For connections over the public internet: Add the EIP Address of the exclusive resource group to the data source's whitelist. If you transfer data over the public internet, you must find the EIP address on the Basic Information page of the exclusive resource group and configure the data source to allow access from it.

Step 4: Test network connectivity

After completing the network configuration, test the connectivity between the resource group and the data source.

    1. Log on to the DataWorks console. In the target region, click More > Management Center in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Management Center.

    2. On the Workspace Management page, click Data Sources in the left-side navigation pane to open the data source page.

  1. Click Edit in the Operation column for the target data source.

  2. On the Data Integration tab, click Test Connectivity next to the resource group name. A status of Connectable indicates a successful connection.

    Note

    If the connection fails, click Self-service troubleshooting to use the diagnostic tool to diagnose the network connectivity issue. For more information about network connectivity between data sources and exclusive resource groups in different network environments, see Network connectivity solutions.

  3. Click Complete.

More operations

Resource group usage and monitoring

You can view the usage and queuing status of resource groups in the DataWorks console. You can also use the intelligent monitoring feature in Operation Center to monitor the usage rate of resource groups and the number of instances that are waiting for resources. For details about how to view the usage rate, see View the Usage Rate of an Exclusive Resource Group. For details about resource group monitoring, see Create a Custom Rule.

Change resource group zone

To change the zone of a resource group, follow these steps:

  1. Log on to the DataWorks console.

  2. In the left-side navigation pane, click Resource Group. On the Resource Groups page, go to the Exclusive Resource Group tab and find the resource group for which the Purpose is set to Data Integration.

  3. Click the image icon in the Operation column of the resource group and select Change Zone to open the Change Zone for Resource Group dialog box.

  4. In the Change Zone for Resource Group dialog box, select the Current Zone and the Machines to be replaced. Then, select the New Zone and the Number of Machines to Use.

  5. Click OK to complete the zone change.

Changing the zone for resources in a resource group can affect network configurations in the following ways:

  • Resource group CIDR block: A zone replacement can change the resource group's CIDR blocks. Each zone uses an independent CIDR block, so if a replacement operation changes the set of zones used by the resource group, the associated CIDR blocks will also change.

  • Resource group primary ENI IP address: The primary ENI IP address of the replaced ECS instance always changes. A new IP address is allocated from the CIDR block of the target zone.

  • Elastic network interface bound to the resource group: If the whitelist is configured with the vSwitch CIDR block, it is not affected. However, if the whitelist is configured with the IP address of the elastic network interface that is bound to the resource group, you must update the whitelist configuration to ensure continued access.

Appendix: Switching Data Integration resource groups

After you create and configure an exclusive resource group for Data Integration, you can use the following methods to switch the resource group used by tasks.

Environment

Operation

Entry point

Switching the resource group for the production environment

Batch switch

Go to the Operation Center > Auto Triggered Task page.

Select the tasks that you want to modify. In the bottom toolbar, click Operation > Change Resource Group for Data Integration. In the dialog box that appears, read the warning "Please ensure that the data sources are accessible from the selected resource group. Otherwise, the Data Integration tasks may fail." From the Select Resource Group drop-down list, select the target resource group, and then click OK.

Switching the resource group for the development environment

  • Switch for a single task

  • Batch switch

Go to the DataStudio page.

  • Switch for a single task

    Go to the edit page of the target node. On the Configure Network Connections and Resource Groups page, click More under My Resource Group to change the resource group.

  • Batch switch

    Click the 批量操作 icon. Select the tasks for which you want to modify the resource group. In the bottom menu bar, click Modify Data Synchronization Task to perform a batch modification.

Note

If you cannot find the option to modify the resource group for Data Integration, filter by the offline synchronization node type first.