Distinguished DataWorks users:
DataWorks DataService Studio APIs can be run on the shared resource group for DataService Studio, exclusive resource groups for DataService Studio, or serverless resource groups. The shared resource group for DataService Studio is shared by all DataWorks tenants and can be used to access data sources that reside only on the Internet or in the classic network. For a long time, the shared resource group for DataService Studio is recommended only for temporary testing. To strengthen the resource isolation, network connectivity, disaster recovery capability, and availability of online services, Alibaba Cloud plans to discontinue the DataWorks shared resource group for DataService Studio.
From March 1, 2025, you can no longer configure the shared resource group for DataService Studio when you create DataService Studio APIs. DataService Studio APIs for which the shared resource group for DataService Studio is configured are not affected and can be used as expected.
From October 1, 2025, you can no longer modify DataService Studio APIs for which the shared resource group for DataService Studio is configured. To modify the APIs, you must configure serverless resource groups for the APIs.
From April 1, 2026, the shared resource group for DataService Studio stops providing services. DataService Studio APIs for which the shared resource group for DataService Studio is configured can no longer be called.
You can refer to the following steps to change the shared resource group for DataService Studio that is used by your DataService Studio APIs to a serverless resource group to obtain more stable, efficient, and secure services:
Billing
For information about the billing of the shared resource group for DataService Studio, see Billing of the shared resource group for DataService Studio.
For information about the billing of a serverless resource group, see Billing of serverless resource groups.
After you change the shared resource group for DataService Studio used by a DataService Studio API to a serverless resource group, the billable items may change. For more information, see Appendix: Comparison between billable items charged before and after resource group change.
Procedure
Evaluate the required specifications of the serverless resource group to purchase
Before you change the shared resource group for DataService Studio used by DataService Studio APIs, you must evaluate the resource consumption of the APIs to determine the specifications of the serverless resource group to purchase. This ensures that the serverless resource group can handle the workloads of related business. You can refer to the following table to perform the evaluation.
Resource group type | Resource group specifications | Maximum queries per second (QPS) |
Shared resource group for DataService Studio | - | 200 QPS |
Pay-as-you-go serverless resource group
| 1 CU | 125 QPS |
4 CUs | 500 QPS | |
6 CUs | 750 QPS | |
8 CUs | 1000 QPS | |
12 CUs | 1500 QPS | |
16 CUs | 2000 QPS | |
Subscription serverless resource group
| 4 CUs | 500 QPS |
8 CUs | 1000 QPS | |
16 CUs | 2000 QPS |
Step 1: Purchase a serverless resource group
You can purchase a serverless resource group based on the evaluation result and associate the serverless resource group with your workspace. After the association, you can select the serverless resource group when you configure DataService Studio APIs in the workspace.
Purchase a serverless resource group based on the determined specifications. For more information, see Step 1: Create a serverless resource group.
Associate the serverless resource group with the workspace to allow DataService Studio APIs in the workspace to use the resource group. For more information, see Step 2: Associate the resource group with a workspace.
Step 2: Configure network settings for the serverless resource group
After you purchase a serverless resource group, you must configure network settings for the resource group. This way, after you configure the serverless resource group for DataService Studio APIs, the resource group can access the related data sources, and you can call the APIs as expected. For more information, see Network connectivity solutions.
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, click Resource Group to go to the Resource Groups page.
On the Exclusive Resource Groups tab of the Resource Groups page, find the created serverless resource group and click Network Settings in the Actions column.
In the DataService Studio section of the page that appears, click Add VPC Association. In the Add VPC Association dialog box, select the virtual private cloud (VPC) and vSwitch of the data source that needs to be accessed by the serverless resource group.
NoteWe recommend that you associate the serverless resource group with two VPCs and two vSwitches.
You can associate a serverless resource group with a VPC to allow the resource group to access a data source or an address in a complex network environment over an internal network. By default, serverless resource groups cannot access the Internet. If you want to use a serverless resource group to access a data source or a network environment over the Internet, you must configure an Internet NAT gateway for the VPC with which the resource group is associated and associate the Internet NAT gateway with an elastic IP address (EIP). For more information, see Scenario 5: Establish a network connection between a resource group and a data source that is deployed on the Internet.
Click OK.
Step 3: Configure a CU quota for the serverless resource group
To ensure that the serverless resource group can be used in DataService Studio, you must configure a CU quota for the resource group for DataService Studio.
If you purchase a pay-as-you-go serverless resource group, you are charged for the serverless resource group after you configure a CU quota for the resource group for DataService Studio. You are not charged for the serverless resource group for DataService Studio only when no CU quota is configured for DataService Studio.
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, click Resource Group to go to the Resource Groups page.
On the Exclusive Resource Groups tab of the Resource Groups page, find the created serverless resource group, click the
icon in the Actions column, and then select Manage Quota.
In the Manage Quota dialog box, click the
icon in the Minimum CUs or Occupied CUs column of DataService Studio and configure a CU quota for DataService Studio.
If you use a pay-as-you-go serverless resource group, specify a value in the Occupied CUs column of the resource group.
If you use a subscription serverless resource group, specify a value in the Minimum CUs column of the resource group.
After the configuration is complete, click OK.
Step 4: Change the shared resource group for DataService Studio used by multiple DataService Studio APIs to the serverless resource group at a time
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose . On the page that appears, select the desired workspace from the drop-down list and click Go to DataService Studio.
In the left-side navigation pane of the DataService Studio page, click the
icon. In the Service Development pane, click the
icon to go to the Batch Operation tab. On the Batch Operation tab, select Shared Resource Group for DataService Studio from the Resource Group drop-down list and click Search to search for the DataService Studio APIs that use the shared resource group for DataService Studio.
Select the DataService Studio APIs and click Change Resource Group in the lower part of the tab.
In the Change Resource Group dialog box, select the created serverless resource group from the Resource Group for DataService Studio drop-down list.
Click OK. Then, the serverless resource group is used for the selected DataService Studio APIs.
Step 5: Test, submit, and publish the DataService Studio APIs
After you change resource groups for the DataService Studio APIs, the change does not immediately take effect for the APIs. You must submit and publish the DataService Studio APIs for the serverless resource group to take effect.
On the Batch Operation tab, select the DataService Studio APIs for which you want to change the shared resource group for DataService Studio to a serverless resource group at a time, click More in the lower part of the tab, and then select Test to test the APIs at a time.
In the Test dialog box, click OK. After the test is complete, view the result.
If the test result meets your expectations, click Submit in the lower part of the tab to submit the DataService Studio APIs.
After the DataService Studio APIs are submitted, click Publish in the lower part of the tab to publish the APIs.
After the DataService Studio APIs are published, the serverless resource group takes effect when you call the APIs.
Appendix: Comparison between billable items charged before and after resource group change
After you change the shared resource group for DataService Studio used by DataService Studio APIs to a serverless resource group, the billable items that are charged when you call the APIs change.
Resource group type | Billable item |
Shared resource group for DataService Studio (pay-as-you-go) | The number of times that a DataService Studio API is called. Unit: million times. |
The size of memory resources that are used in the execution duration of a DataService Studio API. Unit: GB*s. | |
The size of memory resources that are used in the accelerated execution duration of a DataService Studio API. Unit: GB*s. Only DataService Studio APIs for which acceleration items are used are charged. | |
(pay-as-you-go) | You are charged based on the following formula: |
(Subscription) | You are charged based on the number of CUs that are purchased. You can calculate the fee of a subscription resource group based on the following formula: Fee = Unit price per month × Number of months × Number of CUs purchased per month. |