DataWorks:Retirement of the shared resource group for DataService Studio

Assess serverless resource group specifications

Before migrating, assess the resource consumption of your existing APIs. This assessment helps you determine the appropriate specifications for a serverless resource group that can handle your business workloads. Use the following table as a reference for your assessment:

Step 1: Purchase a serverless resource group

Purchase a serverless resource group based on your assessment and associate it with your workspace. Once associated, the resource group is available to all APIs within that workspace.

1. Purchase a serverless resource group with the specifications you determined. For more information, see Create a serverless resource group.

2. Associate the new serverless resource group with your workspace. This allows APIs within the workspace to use the resource group. For more information, see Associate a resource group with a workspace.

Step 2: Configure network settings

To ensure that your APIs can be called successfully, you must configure network settings so that the resource group can access your data sources. For more information, see Network connectivity solutions.

1. Log on to the DataWorks console. In the target region, click Resource Group in the left-side navigation pane to open the resource group list.

2. Find the target resource group and click Network Settings in the Actions column.

3. On the network settings page, find the DataService Studio section and click Add VPC Association to associate the resource group with the virtual private cloud (VPC) and vSwitch of your data source.

   Note

   • For high availability, we recommend associating the resource group with vSwitches in two different availability zones.

   • You can associate a serverless resource group with a VPC to access a data source or an address in a private network. However, a serverless resource group cannot access the internet by default. If your data source requires public internet access, you must configure an Internet NAT gateway and an elastic IP address (EIP) for the associated VPC. For more information, see Access a data source over the internet.

4. Click OK to add the VPC association.

Step 3: Manage the quota

To ensure that DataService Studio can schedule tasks properly, you must manage the CU quota for the serverless resource group.

1. Log on to the DataWorks console. In the target region, click Resource Group in the left-side navigation pane to open the resource group list.

2. Find the target resource group, click the icon in the Actions column, and select Quota Management.

3. In the Manage Quota dialog box, click the icon and configure the number of CUs for DataService Studio.

   1. For a pay-as-you-go resource group, configure the Occupied CUs.

   2. For a subscription resource group, configure the Minimum CUs.

4. Click OK to save the quota settings.

Step 4: Batch migrate APIs

1. Log on to the DataWorks console. In the target region, click Data Analysis and Service > DataService Studio in the left-side navigation pane. Select a workspace from the drop-down list and click Go to DataService Studio.

2. In the left-side navigation pane, click the icon to go to the Service Development page. Then, click the icon to open the Batch Operation page. Filter the APIs by selecting Shared Resource Group for DataService Studio from the Resource Group drop-down list, and then search for the relevant APIs.

3. Select the target APIs from the list and click Change Resource Group at the bottom of the page.

4. In the Change Resource Group dialog box, select your new serverless resource group from the Resource Group for DataService Studio drop-down list.

5. Click OK to complete the migration.

Step 5: Test, submit, and publish the APIs

After you change the resource group, the change does not take effect immediately for online API calls. You must submit and publish the APIs to activate the new configuration.

1. On the Batch Operation page, select the APIs that you just migrated. Click More > Test at the bottom of the page to initiate a batch test.

2. In the confirmation dialog box, click OK to start the test. Wait for the test to complete and review the results.

3. If the tests are successful, click Commit at the bottom of the Batch Operation page.

4. After the submission is complete, click Deploy to publish the updated APIs.

   After publishing, the new resource group takes effect for all subsequent online calls.