Permissions Management

Updated on 2022-12-05 GMT+08:00

View PDF

If you need to assign different permissions to employees in your enterprise to access your DLF resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your HUAWEI CLOUD resources.

With IAM, you can use your HUAWEI CLOUD 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 DLF 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 DLF resources.

If your HUAWEI CLOUD account does not need individual IAM users for permissions management, you may skip over this chapter.

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.

DLF Permissions

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

DLF is a project-level service deployed in specific physical regions. Therefore, DLF permissions are assigned to users in specific regions (such as CN North-Beijing1) and only take effect for these regions. If you want the permissions to take effect for all regions, you need to assign the permissions to users in each region. When accessing DLF, the users need to switch to a region where they have been authorized to use cloud services.

Table 1 lists all the system-defined roles and permissions supported by DLF.

You can grant users permissions by using roles and policies.

Role: IAM initially provides a coarse-grained authorization mechanism to define permissions based on users' job responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. 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, a user group is not allowed to delete jobs but can only perform basic operations on jobs, such as creating jobs and querying the job list. For the API actions supported by DLF, see Permissions Policies and Supported Actions.

**Table 1** DLF system permissions
Role/Policy Name	Description	Type
DLF FullAccess	All permissions for DLF	System-defined policy
DLF Development	Developer permissions for DLF. Users granted these permissions can use DLF to develop scripts and orchestrate jobs, but cannot add, delete, or modify workspaces.	System-defined policy
DLFOperationAndMaintenanceAccess	O&M permissions for DLF. Users granted these permissions can perform O&M operations on DLF scripts and jobs, but cannot add, delete, or modify resources.	System-defined policy
DLF ReadOnlyAccess	Read-only permissions for DLF. Users granted these permissions can only view DLF resources.	System-defined policy
DLF Administrator	Administrator permissions for DLF.	System-defined role

Table 2 lists the common operations supported by each policy or role of DLF. Select the policies or roles as required.

**Table 2** Common operations supported by each policy or role
Operation	DLF FullAccesss	DLF Development	DLF OperationAndMaintenanceAccess	DLF ReadonlyAccess	DLF Administrator
Querying workspaces	√	√	√	√	√
Creating workspaces	√	x	x	x	√
Updating workspaces	√	x	x	x	√
Deleting workflows	√	x	x	x	√
Querying environment variables.	√	√	√	√	√
Updating environment variables	√	√	x	x	√
Importing environment variables	√	√	x	x	√
Exporting environment variables	√	√	x	x	√
Querying tables	√	√	√	√	√
Creating tables	√	√	x	x	√
Updating tables	√	√	x	x	√
Deleting tables	√	√	x	x	√
Querying databases	√	√	√	√	√
Creating databases	√	√	x	x	√
Updating databases	√	√	x	x	√
Deleting databases	√	√	x	x	√
Querying modes.	√	√	√	√	√
Creating modes	√	√	x	x	√
Updating modes	√	√	x	x	√
Deleting modes	√	√	x	x	√
Querying directories	√	√	√	√	√
Creating directories	√	√	x	x	√
Updating directories	√	√	x	x	√
Deleting directories	√	√	x	x	√
Querying solutions	√	√	√	√	√
Creating solutions	√	√	x	x	√
Updating solutions	√	√	x	x	√
Deleting solutions	√	√	x	x	√
Importing solutions	√	√	√	x	√
Exporting solutions	√	√	√	x	√
Starting solutions	√	√	√	x	√
Stopping solutions	√	√	√	x	√
Querying scripts	√	√	√	√	√
Creating scripts	√	√	x	x	√
Updating scripts	√	√	x	x	√
Deleting scripts	√	√	x	x	√
Checking script syntax	√	√	√	x	√
Executing scripts	√	√	√	x	√
Canceling script execution	√	√	√	x	√
Importing scripts	√	√	√	x	√
Exporting scripts or script execution results	√	√	√	x	√
Querying jobs	√	√	√	√	√
Creating jobs	√	√	x	x	√
Updating jobs	√	√	x	x	√
Deleting jobs	√	√	x	x	√
Renaming jobs	√	√	x	x	√
Importing jobs	√	√	√	x	√
Exporting jobs	√	√	√	x	√
Verifying validity of job definitions	√	√	√	x	√
Testing jobs	√	√	√	x	√
Starting jobs	√	√	√	x	√
Stopping jobs	√	√	√	x	√
Suspending jobs	√	√	√	x	√
Resuming jobs	√	√	√	x	√
Querying job instances	√	√	√	√	√
Rerunning job instances	√	√	√	x	√
Stopping job instances	√	√	√	x	√
Forcibly making jobs instances succeed	√	√	√	x	√
Continuing with job instances	√	√	√	x	√
Enabling job nodes	√	√	√	x	√
Disabling job nodes	√	√	√	x	√
Rerunning job nodes	√	√	√	x	√
Skipping job node execution	√	√	√	x	√
Suspending job nodes	√	√	√	x	√
Resuming job node execution	√	√	√	x	√
Forcibly making jobs nodes succeed	√	√	√	x	√
Querying data connections	√	√	√	√	√
Creating data connections	√	√	x	x	√
Updating data connections	√	√	x	x	√
Deleting data connections	√	√	x	x	√
Testing connectivity of data connections	√	√	x	x	√
Importing data connections	√	√	√	x	√
Exporting data connections	√	√	√	x	√
Querying resources	√	√	√	√	√
Creating resources	√	√	x	x	√
Updating resources	√	√	x	x	√
Deleting resources	√	√	x	x	√
Uploading resources	√	√	x	x	√
Exporting resources	√	√	√	x	√
Importing resources	√	√	√	x	√
Querying backup information	√	√	√	√	√
Starting backup	√	√	√	x	√
Stopping backup	√	√	√	x	√
Querying notifications	√	√	√	√	√
Creating notifications	√	√	x	x	√
Updating notifications	√	√	x	x	√
Deleting notifications	√	√	x	x	√
Querying PatchData	√	√	√	√	√
Creating PatchData tasks	√	√	x	x	√
Stopping PatchData tasks	√	√	√	x	√

Previous topic: Functions

Next topic: Related Services

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot