Help Center> Identity and Access Management> Best Practices> Assigning Permissions to O&M Personnel
Updated on 2022-06-23 GMT+08:00
View PDF

Assigning Permissions to O&M Personnel

Assume that company A has purchased different resources on HUAWEI CLOUD, and has multiple functional teams that need to use one or more types of resources. Company A can use IAM to assign the permissions required for the O&M personnel to use resources.

Figure 1 Permissions management model
  • Resource O&M team
  • Accounting management team
  • Resource monitoring team
  • Computing O&M team
  • Network O&M team
  • Database O&M team
  • Security O&M team

Assign required permissions to different functional teams in the company according to Table 1. For details about permissions of all HUAWEI CLOUD services, see System Permissions.

Table 1 System permissions

Functional Team

Policy

Permissions Description

Resource O&M team

Tenant Administrator

Full permissions for all cloud services, including Billing Center, Resource Center, and My Account. The Tenant Administrator role includes the permissions for purchasing resources, managing renewals, and viewing bills. It does not include the permissions for the IAM service.

Accounting management team

BSS Administrator

Full permissions for Billing Center, Resource Center, and My Account. The BSS Administrator role includes the permissions for managing invoices, orders, contracts, and renewals, and viewing bills. Users assigned only this role cannot purchase resources unless you grant them the administrator permissions of the corresponding service.

Resource monitoring team

Tenant Guest

Read-only permissions for all cloud services except IAM.

Computing O&M team

ECS FullAccess

Full permissions for Elastic Cloud Server (ECS), including permissions for purchasing ECSs. Users assigned only the ECS FullAccess policy cannot view the usage of ECSs and other resources unless you assign them the BSS Administrator role.

CCE FullAccess

Full permissions for Cloud Container Engine (CCE), including permissions for purchasing CCE resources. Users assigned only the CCE FullAccess policy cannot view the usage of CCE resources and other resources unless you assign them the BSS Administrator role.

AutoScaling FullAccess

Full permissions for Auto Scaling (AS), including purchasing AS resources. Users assigned only the AutoScaling FullAccess policy cannot view the usage of AS resources and other resources unless you assign them the BSS Administrator role.

Network O&M team

VPC FullAccess

Full permissions for Virtual Private Cloud (VPC), including purchasing VPCs. Users assigned only the VPC FullAccess policy cannot view the usage of VPC resources and other resources unless you assign them the BSS Administrator role.

ELB FullAccess

Full permissions for Elastic Load Balance (ELB), including purchasing load balancers. Users assigned only the ELB FullAccess policy cannot view the usage of ELB resources and other resources unless you assign them the BSS Administrator role.

Database O&M team

RDS FullAccess

Full permissions for Relational Database Service (RDS), including purchasing RDS resources. Users assigned only the RDS FullAccess policy cannot view the usage of RDS resources and other resources unless you assign them the BSS Administrator role.

DDS FullAccess

Full permissions for Document Database Service (DDS), including purchasing DDS resources. Users assigned only the DDS FullAccess policy cannot view the usage of DDS resources and other resources unless you assign them the BSS Administrator role.

DDM FullAccess

Full permissions for Distributed Database Middleware (DDM).

Security O&M team

Anti-DDoS Administrator

Full permissions for Anti-DDoS.

CAD Administrator

Full permissions for Advanced Anti-DDoS (AAD).

KMS Administrator

Full permissions for Data Encryption Workshop (DEW), including purchasing DEW resources. Users assigned only the KMS Administrator role cannot view the usage of DEW resources and other resources unless you assign them the BSS Administrator role.

Assigning Permissions to O&M Personnel

The following is an example procedure for specifying an employee of company A as the network O&M owner in the CN-Hong Kong region. If you want to specify an employee as any other O&M owner, grant the required permissions to the employee according to Table 1.

Step 1: Create a User Group and Assign Permissions

  1. Log in to the HUAWEI CLOUD management console.
  2. On the management console, hover the mouse pointer over the username in the upper right corner and then choose Identity and Access Management.
  3. On the IAM console, choose User Groups in the navigation pane. Then click Create User Group.

    Figure 2 Creating a user group

  4. Enter the user group name Network_OM, and click OK.

  5. In the row containing the user group, click Authorize.

  6. Search for and select VPC FullAccess and ELB FullAccess, and click Next.
  7. Specify the authorization scope as Region-specific projects and select CN-Hong Kong.

    • If users in the group need to view resource usage, attach the BSS Administrator role to the group for the same project.
    • When specifying an employee as the security O&M owner according to Table 1, you must grant the employee other related permissions because the security services interwork with other cloud services. For more information, see Assigning Dependent Roles.

Step 2: Create an IAM User

  1. In the navigation pane of the IAM console, choose Users. Then click Create User.
  2. Specify the user details and access type. To create more users, click Add User. A maximum of 10 users can be created at a time.

    Figure 3 Configuring user information
    • Users can log in to HUAWEI CLOUD using the username, email address, or mobile number.
    • If users forget their password, they can reset it through email address or mobile number verification. If no email addresses or mobile numbers have been bound to users, users need to contact the administrator to reset their passwords.
    Table 2 User information

    Parameter

    Description

    Username

    Username that will be used to log in to HUAWEI CLOUD, for example, James and Alice. This field is required.

    Email Address

    Email address of the IAM user that can be used as a login credential. IAM users can bind an email address after they are created. This field is required if you have specified Set by user as the access type.

    Mobile Number

    Mobile phone number of the IAM user that can be used as a login credential. IAM users can bind a mobile number after they are created. This field is optional.

    Description

    Additional information about the IAM user. This field is optional.
    Figure 4 Setting the access type
    • Programmatic access: Select this option to allow the user to access HUAWEI CLOUD services using development tools, such as APIs, CLI, and SDKs. You can generate an access key or set a password for the user.
    • Management console access: Select this option to allow the user to access HUAWEI CLOUD services using the management console. You can set or generate a password for the user or request the user to set a password at first login.
      • If the user accesses cloud services only by using the management console, select Management console access for Access Type and Password for Credential Type.
      • If the user accesses cloud services only through programmatic calls, select Programmatic access for Access Type and Access key for Credential Type
      • If the user needs to use a password as the credential for programmatic access to certain APIs, select Programmatic access for Access Type and Password for Credential Type
      • If the user needs to perform access key verification when using certain services in the console, select Programmatic access and Management console access for Access Type and Access key and Password for Credential Type. For example, the user needs to perform access key verification when creating a data migration job in the Cloud Data Migration (CDM) console.
      Table 3 Setting the credential type and login protection

      Credential Type and Login Protection

      Description

      Access key

      After users are created, you can download the access keys (AK/SK) generated for these users.

      Each user can have a maximum of two access keys.

      Password

      Set now

      Set a password for the user and determine whether to require the user to reset the password at first login.

      If you are the user, select this option and set a password for login. You do not need to select Require password reset at first login.

      Automatically generated

      The system automatically generates a login password for the user. After the user is created, download the EXCEL password file and provide the password to the user. The user can then use this password for login.

      This option is available only when you create a single user.

      Set by user

      A one-time login URL will be emailed to the user. The user can click the link to log in to the console and set a password.

      If you do not use the IAM user, select this option and enter the email address and mobile number of the IAM user. The user can then set a password by clicking on the one-time login URL sent over email. The login URL is valid for seven days.

      Login Protection

      Enable (Recommended)

      If login protection is enabled, the user will need to enter a verification code in addition to the username and password during login. Enable this function for account security.

      You can select SMS, email, or virtual MFA device for verification during login.

      Disable

      If login protection is disabled, you can enable it later by following the instructions provided in Modifying IAM User Information.

  3. (Optional) Click Next to add the users to user groups.

    • The user will inherit the permissions assigned to the user groups to which the user belongs.
    • You can also create new groups as required.
    • If the user will be an administrator, add the user to the default group admin.
    • Each user can be added to multiple user groups.

  4. Click Next. If you have specified the access type as Programmatic access in Step 2, download the access key on the Finish page.

    Figure 5 Users created successfully

Step 3: Log In as an IAM User and Verify Permissions

An IAM user can log in using different methods. The following describes how to log in through the login page. For more login methods, see Logging In to HUAWEI CLOUD.

  1. On the HUAWEI CLOUD login page, click IAM User.
  2. On the IAM User Login page, enter the account name, username, and password of the created user.

    • Account name: Name of the account used to create the IAM user
    • Username and password: The username and password specified for the IAM user.

  3. On the management console, switch to the CN-Hong Kong region.
  4. Choose Service List > Virtual Private Cloud, Elastic Load Balance, and Domain Name Service, and perform operations on each service console to verify that the permissions have been successfully assigned.
  5. Choose a service other than the preceding services from Service List to ensure that the service cannot be accessed.
  6. On the management console, switch to a region other than CN-Hong Kong and ensure that the VPC, ELB, and DNS consoles cannot be accessed.