Help Center/
Data Lake Insight/
FAQs/
Flink Jobs/
Flink Job Consulting/
How Do I Authorize a Subuser to View Flink Jobs?
Updated on 2024-11-15 GMT+08:00
How Do I Authorize a Subuser to View Flink Jobs?
A sub-user can view queues but cannot view Flink jobs. You can authorize the sub-user using DLI or IAM.
- Authorization on DLI
- Log in to the DLI console using a tenant account, a job owner account, or an account with the DLI Service Administrator permission.
- Choose Job Management > Flink Jobs. On the displayed page, locate the target job.
- In the Operation column of the target job, choose More > Permissions.
Figure 1 Managing Flink job permissions
- On the displayed page, click Grant Permission. Enter the name of the user to be authorized and select the required permissions. Click OK. The authorized user can view the job and perform related operations.
Figure 2 Getting permissions
- Authorization on IAM
- Log in to the IAM console. In the navigation pane, choose Permissions > Policies/Roles. On the displayed page, click Create Custom Policy.
- Create a permission policy for the subuser to view DLI Flink jobs.
- Policy Name: Use the default name or customize a name.
- Scope: Select Project-level services.
- Policy View: Select Visual editor.
- Policy Content: Select Allow, Data Lake Insight, and dli:jobs:list_all in sequence.
Click OK to create the policy.
Figure 3 Creating a policy
- Go to the User Group page, locate the user group to which the subuser to be authorized belongs and click the user group name. On the displayed page, click Assign.
- Grant permissions to the user group.
- Select Region-specific projects for Scope.
- Select the permission policy created in 2 for Permissions.
You can also select DLI Service Administrator (with all DLI permissions) for the subuser to view Flink jobs.
Parent topic: Flink Job Consulting
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot