Overview¶
DLI has a comprehensive permission control mechanism and supports fine-grained authentication through Identity and Access Management (IAM). You can create policies in IAM to manage DLI permissions. You can use both the DLI's permission control mechanism and the IAM service for permission management.
Application Scenarios of IAM Authentication¶
When using DLI on the cloud, enterprise users need to manage DLI resources (queues) used by employees in different departments, including creating, deleting, using, and isolating resources. In addition, data of different departments needs to be managed, including data isolation and sharing.
DLI uses IAM for refined enterprise-level multi-tenant management. IAM provides identity authentication, permissions management, and access control, helping you securely access to your cloud resources.
With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use DLI resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DLI resources.
Note
For a new user, you need to log in for the system to record the metadata before using DLI.
IAM is free to use, and you only need to pay for the resources in your account.
If your account does not need individual IAM users for permissions management, skip over this section.
DLI System Permissions¶
Table 1 lists all the system-defined roles and policies supported by DLI.
Type: There are roles and policies.
Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Only a limited number of service-level roles are available. When using roles to grant permissions, you also need to assign other roles on which the permissions depend. However, roles are not an ideal choice for fine-grained authorization and secure access control.
Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant DLI users only the permissions for managing a certain type of ECSs.
Role/Policy Name | Description | Category | Dependency |
|---|---|---|---|
DLI FullAccess | Full permissions for DLI. | System-defined policy | This role depends on other roles in the same project.
|
DLI ReadOnlyAccess | Read-only permissions for DLI. With read-only permissions, you can use DLI resources and perform operations that do not require fine-grained permissions. For example, create global variables, create packages and package groups, submit jobs to the default queue, create tables in the default database, create datasource connections, and delete datasource connections. | System-defined policy | None |
Tenant Administrator | Tenant administrator
| System-defined role | None |
DLI Service Administrator | DLI administrator.
| System-defined role | None |
For details, see Creating an IAM User and Granting Permissions.
DLI Permission Types¶
Table 2 lists the DLI service permissions. For details about the resources that can be controlled by DLI, see Table 4.
Permission Type | Subtype | Console Operations | SQL Syntax | API Definition |
|---|---|---|---|---|
Queue Permissions | Queue management permissions | For details, see Queue Permission Management. | None | For details, see "Granting Users with the Queue Usage Permission" in the Data Lake Insight API Reference. |
Queue usage permission | ||||
Data Permissions | Database permissions | For details, see Managing Database Permissions and Managing Table Permissions. | For details, see SQL Syntax of Batch Jobs > Data Permissions Management > Data Permissions List in the Data Lake Insight SQL Syntax Reference. | For details, see Permission-related APIs > Granting Users with the Data Usage Permission in the Data Lake Insight API Reference. |
Table permissions | ||||
Column permissions | ||||
Job Permissions | Flink job permissions | For details, see Managing Flink Job Permissions. | None | For details, see Permission-related APIs > Granting Users with the Data Usage Permission in the Data Lake Insight API Reference. |
Package Permissions | Package group permissions | For details, see Managing Permissions on Packages and Package Groups. | None | For details, see Permission-related APIs > Granting Users with the Data Usage Permission in the Data Lake Insight API Reference. |
Package permissions | ||||
Datasource Connection Permissions | Datasource connection permissions | For details, see Datasource Authentication Permission Management. | None | For details, see Permission-related APIs > Granting Users with the Data Usage Permission in the Data Lake Insight API Reference. |
Examples¶
An Internet company mainly provides game and music services. DLI is used to analyze user behaviors and assist decision making.
As shown in Figure 1, the Leader of the Basic Platform Team has applied for a Tenant Administrator account to manage and use cloud services. The Leader of the Basic Platform Team creates a subaccount with the DLI Service Administrator permission to manage and use DLI, as the Big Data Platform Team requires DLI for data analysis. The Leader of the Basic Platform Team creates a Queue A and assigns it to Data Engineer A to analyze the gaming data. A Queue B is also assigned to Data Engineer B to analyze the music data. Besides granting the queue usage permission, the Leader of the Basic Platform Team grants data (except the database) management and usage permissions to the two engineers.
Figure 1 Granting permissions¶
The Data Engineer A creates a table named gameTable for storing game prop data and a table named userTable for storing game user data. The music service is a new service. To explore potential music users among existing game users, the Data Engineer A assigns the query permission on the userTable to the Data Engineer B. In addition, Data Engineer B creates a table named musicTable for storing music copyrights information.
Table 3 describes the queue and data permissions of Data Engineer A and Data Engineer B.
User | Data Engineer A (game data analysis) | Data Engineer B (music data analysis) |
|---|---|---|
Queues | Queue A (queue usage permission) | Queue B (queue usage permission) |
Data (Table) | gameTable (table management and usage permission) | musicTable (table management and usage permission) |
userTable (table management and usage permission) | userTable (table query permission) |
Note
The queue usage permission includes job submitting and terminating permissions.