DataWorks:Associate a fully managed Flink computing resource

Prerequisites

• You have activated a Realtime Compute for Apache Flink cluster.

  Note

  We recommend that you purchase a Flink cluster in the same Region as the DataWorks workspace where the fully managed Flink computing resource is created. If the regions are different, you cannot bind the cluster as a computing resource for that workspace.

• You have created a workspace in DataWorks, and the RAM user performing this operation has been added to the workspace and assigned the Workspace Administrator role.

  Important

  Supported only for workspaces that Use Data Studio (New Version).

• You have created a Serverless resource group and associated it with the target workspace.

Limitations

• Region availability: This feature is available only in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Chengdu), China (Hong Kong), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Germany (Frankfurt), UK (London), US (Silicon Valley), and US (Virginia).

• Permissions:

  Operator	Required permissions
  Alibaba Cloud account	No additional permissions are required.
  RAM user or RAM role	DataWorks permissions: Only workspace members with the O&M or Workspace Administrator role, or members with the AliyunDataWorksFullAccess policy can create computing resources. For more information, see Grant a user the Workspace Administrator permissions. Flink service permissions: The AliyunStreamFullAccess policy is required to configure a fully managed Flink computing resource. You must have management permissions for the Flink project in the Realtime Compute for Apache Flink cluster. For more information, see Project authorization.

Go to the computing resource list page

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

2. In the navigation pane on the left, click Computing Resources to open the computing resource list page.

Associate the fully managed Flink computing resource

On the Computing Resource page, complete the following steps.

1. Select the computing resource type.

   1. Click Associate Computing Resources to go to the Associate Computing Resources page.

   2. On the Associate Computing Resources page, select Fully Managed Flink as the computing resource type to go to the Bind Fully-managed Flink Computing Resource configuration page.

2. Configure the fully managed Flink computing resource.

   On the Associate Realtime Compute for Apache Flink Computing Resource page, configure the following parameters.

   Parameter	Description
   Flink Workspace	Select an activated Realtime Compute for Apache Flink cluster. You can also click Create in the drop-down list to create a new cluster. For more information, see Activate a Realtime Compute for Apache Flink cluster. Note If you chose to isolate the development and production environments when you created the workspace, you must select a Flink workspace for each environment.
   Flink Namespace	Select the default Flink project that was automatically generated when you activated the Realtime Compute for Apache Flink cluster. You can also click Create in the drop-down list to create a new Flink project. For more information, see Manage projects.
   Default Resource Queue in Which Namespace is Deployed	Select the default resource queue that was automatically generated when you activated the cluster. You can also click Create to add a new resource queue. For more information, see Manage resource queues.
   Default Access Identity	Defaults to Executor.
   Computing Resource Instance Name	Specify a custom name for the computing resource. This name is used to select the computing resource for a task at runtime.

3. Click Confirm.

Next steps

After the association is complete, you can develop Flink tasks in Data Studio. For more information, see Flink SQL Streaming node and Flink SQL Batch node.