To use DataWorks to develop and manage OpenSearch tasks, you must first bind your OpenSearch instance as a computing resource in DataWorks. After the instance is bound, you can use the computing resource for data synchronization and development operations.
Prerequisites
You have purchased an OpenSearch Vector Search Edition instance.
NoteWhen you purchase an OpenSearch Vector Search Edition instance, make sure to select the same Region as your DataWorks workspace. You cannot bind the instance to the workspace if their regions are different.
You have created a workspace in DataWorks. The RAM user who performs the operation must be added to the workspace and assigned the Workspace Administrator role.
ImportantThis feature is supported only in workspaces that are in the Public Preview of the New DataStudio.
You have attached a resource group to the workspace and ensured network connectivity.
If you use a Serverless resource group, ensure that the Serverless resource group can connect to the OpenSearch instance.
If you use a legacy exclusive resource group, ensure that the exclusive resource group for scheduling can connect to the OpenSearch instance.
Limits
Supported products: You can bind only OpenSearch Vector Search Edition instances as OpenSearch computing resources.
Supported regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Hong Kong), Singapore, and Germany (Frankfurt).
Permissions:
Operator
Required permissions
Alibaba Cloud account
No additional permissions are required.
RAM user or RAM role
Only workspace members who have the O&M and Workspace Administrator roles, or workspace members who have the
AliyunDataWorksFullAccess
permission can create computing resources. For more information, see Grant a user the permissions of a workspace administrator.
Go to the computing resource list page
Log on to the DataWorks console. Switch to the destination region. In the navigation pane on the left, choose . From the drop-down list, select your workspace and click Go To Management Center.
In the navigation pane on the left, click Computing Resources.
Bind an OpenSearch computing resource
On the computing resource list page, configure the required parameters to bind an OpenSearch computing resource.
Select a computing resource type.
Click Bind Computing Resource to open the Bind Computing Resource page.
On the Bind Computing Resource page, set the computing resource type to OpenSearch. This opens the Bind OpenSearch Computing Resource configuration page.
Configure the OpenSearch computing resource.
On the Bind OpenSearch Computing Resource page, use the following table to configure the parameters.
Parameter
Description
OpenSearch Instance
Select an OpenSearch instance that you purchased. You can also click Create in the drop-down list to go to the OpenSearch purchase page and purchase an OpenSearch Vector Search Edition instance.
NoteIf you chose to isolate the production and development environments when you created the workspace, select separate OpenSearch instances for each environment.
Username
Enter the username that you configured when you created the OpenSearch instance. To view the username, go to the OpenSearch Instance Management page.
Password
Enter the password that you configured when you created the OpenSearch instance.
Computing Resource Instance Name
Enter a custom name for the computing resource. At runtime, this name is used to select the computing resource for a task.
Test the network connection.
In the connection configuration section, select the resource group that DataWorks uses to run offline OpenSearch sync tasks. Click Test Connectivity to verify that the resource group can access your OpenSearch instance. For more information, see Network connectivity solutions.
Click Confirm.
When you bind an OpenSearch computing resource, the system automatically creates an OpenSearch data source with the same name in the Data Source section of the current workspace.
What to do next
After you configure the OpenSearch computing resource, you can use it to develop offline sync tasks in a Offline synchronization nodes.
node in Data Development. For more information, see