Permissions Management

If you need to assign different permissions to employees in your enterprise to access your DLI resources, IAM is a good choice for fine-grained permissions 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.

If your account does not require individual IAM users for permissions management, you may skip over this section.

DLI Permissions

By default, new IAM users do not have permissions assigned. You need to add the users to one or more groups, and attach permissions policies or roles to these groups. The users then inherit permissions from the groups to which they are added. After authorization, the users can perform specified operations on DLI based on the permissions.

DLI is a project-level service deployed and accessed in specific physical regions. To assign ServiceStage permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing DLI, the users need to switch to a region where they have been authorized to use cloud services.

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. If one role has a dependency role required for accessing SA, assign both roles to the users. 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. For the actions supported by DLI APIs, see "Permissions Policies and Supported Actions" in the Data Lake Insight API Reference.

Table 1 DLI system permissions

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.

  • Creating a datasource connection: VPC ReadOnlyAccess

  • Creating a tag: TMS FullAccess and EPS EPS FullAccess

  • Using OBS for storage: OBS OperateAccess

  • Creating an agency: Security Administrator

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

  • Job execution permissions for DLI resources. After a database or a queue is created, the user can use the ACL to assign rights to other users.

  • Scope: project-level service

System-defined role

None

DLI Service Administrator

DLI administrator.

  • Job execution permissions for DLI resources. After a database or a queue is created, the user can use the ACL to assign rights to other users.

  • Scope: project-level service

System-defined role

None

Table 2 lists the common operations supported by each system policy. You can choose required system policies according to this table.

Table 2 Common operations supported by each system permission

Resource

Operation

Description

DLI FullAccess

DLI ReadOnlyAccess

Tenant Administrator

DLI Service Administrator

Queue

DROP_QUEUE

Deleting a Queue

Y

x

Y

Y

SUBMIT_JOB

Submitting a job

Y

x

Y

Y

CANCEL_JOB

Terminating a Job

Y

x

Y

Y

RESTART

Restarting a queue

Y

x

Y

Y

GRANT_PRIVILEGE

Granting permissions to a queue

Y

x

Y

Y

REVOKE_PRIVILEGE

Revoking permissions to a queue

Y

x

Y

Y

SHOW_PRIVILEGES

Viewing the queue permissions of other users

Y

x

Y

Y

Database

DROP_DATABASE

Deleting a database

Y

x

Y

Y

CREATE_TABLE

Creating a table

Y

x

Y

Y

CREATE_VIEW

Creating a view

Y

x

Y

Y

EXPLAIN

Explaining the SQL statement as an execution plan

Y

x

Y

Y

CREATE_ROLE

Creating a role

Y

x

Y

Y

DROP_ROLE

Deleting a role

Y

x

Y

Y

SHOW_ROLES

Displaying a role

Y

x

Y

Y

GRANT_ROLE

Binding a role

Y

x

Y

Y

REVOKE_ROLE

Unbinding a role

Y

x

Y

Y

SHOW_USERS

Displaying the binding relationships between all roles and users

Y

x

Y

Y

GRANT_PRIVILEGE

Granting permissions to the database

Y

x

Y

Y

REVOKE_PRIVILEGE

Revoking permissions to the database

Y

x

Y

Y

SHOW_PRIVILEGES

Viewing database permissions of other users

Y

x

Y

Y

DISPLAY_ALL_TABLES

Displaying tables in a database

Y

Y

Y

Y

DISPLAY_DATABASE

Displaying databases

Y

Y

Y

Y

CREATE_FUNCTION

Creating a function

Y

x

Y

Y

DROP_FUNCTION

Deleting a function

Y

x

Y

Y

SHOW_FUNCTIONS

Displaying all functions

Y

x

Y

Y

DESCRIBE_FUNCTION

Displaying function details

Y

x

Y

Y

Table

DROP_TABLE

Deleting tables

Y

x

Y

Y

SELECT

Querying tables

Y

x

Y

Y

INSERT_INTO_TABLE

Inserting table data

Y

x

Y

Y

ALTER_TABLE_ADD_COLUMNS

Adding a column

Y

x

Y

Y

INSERT_OVERWRITE_TABLE

Overwriting a table

Y

x

Y

Y

ALTER_TABLE_RENAME

Renaming a table

Y

x

Y

Y

ALTER_TABLE_ADD_PARTITION

Adding partitions to the partition table

Y

x

Y

Y

ALTER_TABLE_RENAME_PARTITION

Renaming a table partition

Y

x

Y

Y

ALTER_TABLE_DROP_PARTITION

Deleting partitions from a partition table

Y

x

Y

Y

SHOW_PARTITIONS

Displaying all partitions

Y

x

Y

Y

ALTER_TABLE_RECOVER_PARTITION

Restoring table partitions

Y

x

Y

Y

ALTER_TABLE_SET_LOCATION

Setting the partition path

Y

x

Y

Y

GRANT_PRIVILEGE

Granting permissions to the table

Y

x

Y

Y

REVOKE_PRIVILEGE

Revoking permissions to the table

Y

x

Y

Y

SHOW_PRIVILEGES

Viewing table permissions of other users

Y

x

Y

Y

DISPLAY_TABLE

Displaying a table

Y

Y

Y

Y

DESCRIBE_TABLE

Displaying table information

Y

x

Y

Y

Enhanced datasource connection

BIND_QUEUE

Binding an enhanced datasource connection to a queue

It is only used to grant permissions across projects.

x

x

x

x

last updated: 2024-12-10 15:25 UTC - commit: 9e0ebe18fe0b43010decd2c132af9f5362beb29e