Creating an IAM User and Assigning DataArts Studio Permissions

Background

• Before assigning permissions to a user group, you need to understand the DataArts Studio permission system and select permissions as needed. For details about the permissions supported by DataArts Studio, see DataArts Studio Permissions Management.
  Figure 1 Permission system
  
• For details on the system policies of other services, see Permissions Policies.

Constraints

• The DAYU User role provides permissions related to instances, workspaces, and dependent services. Workspace roles provide service operation permissions in workspaces.

• IAM provides the following two authorization mechanisms: Note that DataArts Studio supports only the IAM role-based authorization and does not support the IAM policy-based authorization.

  • IAM Roles: 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. However, traditional IAM roles are not an ideal choice for fine-grained authorization and secure access control.
  • IAM Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access.

Procedure

Figure 2 Authorization process

1. Create a user group and assign a system role to the group.

   Log in to the IAM console using a Huawei account, create a user group and assign a DataArts Studio system role to the group. For example, the system role can be DAYU Administrator or DAYU User.

   For details, see Creating a User Group and Assigning Permissions.

   

   • When configuring DataArts Studio permissions for a user group, enter DAYU in the search box to search for the permissions and select the permissions to be granted to the user group, for example, DAYU User.
   • DataArts Studio is a project-level service deployed in specific physical regions. If you select All resources for Scope, the permission takes effect in all projects of all regions. If you select Region-specific projects for Scope, the permission takes effect only for a specified project. When accessing DataArts Studio, the IAM user must switch to the region where they have been assigned the required permissions.

2. Create a user and add it to the user group.

   Create users on the IAM console and add them to the group created in step 1.

   For details, see Creating an IAM User and Adding It to a User Group.

   

   An IAM user can pass the authentication and access DataArts Studio through an API or SDK only if Programmatic access is selected for Access Type during the creation of the IAM user.

3. Create a custom workspace role for DAYU User, add it as a workspace member, and assign a role to the member.

   DataArts Studio workspace roles determine the permissions of DAYU User in a workspace. There are five preset roles: admin, developer, deployer, operator, and viewer. For details about how to add a workspace member and assign a role to the member, see Adding a Member and Assigning a Role.

   For details about the permissions of the roles, see DataArts Studio Permissions.

4. Log in to the console and verify permissions.

   Log in to the console using the created user and verify permissions of the user.

   • Choose Service List > DataArts Studio. Locate a DataArts Studio instance and click Access. Check whether the workspace list is displayed.
   • Access a service module (for example, Management Center) to which your current user has been added and check whether you can perform the operations allowed for the workspace role assigned to you.

Follow-up Operations

• The preset DAYU User has excessive permissions of dependent services, which may cause security risks. You can manually remove unnecessary permissions to comply with the principle of least privilege (PoLP). For details, see Authorizing IAM Users to Use DataArts Studio by Complying with the Principle of Least Privilege.