If you need to assign different permissions to employees in your enterprise to access My Account, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your Huawei Cloudcloud resources If your Huawei Cloud account does not require individual IAM users for permissions management, you can skip this section.
IAM is a free service. You only pay for the resources in your account.
With IAM, you can assign permissions to control their access to specific resources.
IAM supports role/policy-based authorization and identity policy-based authorization.
The following table describes the differences between the two authorization models.
Table 1 Differences between role/policy-based and identity policy-based authorization
|
Authorization Model |
Core Relationship |
Permissions |
Authorization Method |
Scenario |
|
Role/Policy |
User-permission-authorization scope |
- System-defined roles
- System-defined policies
- Custom policies
|
Assigning roles or policies to principals |
To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It provides a limited number of condition keys and cannot meet the requirements of fine-grained permissions control. This method is suitable for small- and medium-sized enterprises. |
|
Identity policy |
User-policy |
- System-defined identity policies
- Custom identity policies
|
- Assigning identity policies to principals
- Attaching identity policies to principals
|
You can authorize a user by attaching an identity policy to it. User-specific authorization and a variety of key conditions allow for more fine-grained permissions control. However, this model can be hard to set up. It requires a certain amount of expertise and is suitable for medium- and large-sized enterprises. |
Policies/identity policies and actions in the two authorization models are not interoperable. You are advised to use the identity policy-based authorization model. For details about system-defined permissions of the two models, see Role/Policy-based Authorization and Identity Policy-based Authorization. For more information about IAM, see IAM Service Overview.
Role/Policy-based Authorization
My Account supports role/policy-based authorization. New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and then attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
Table 2 lists all system-defined permissions for My Account. System-defined policies in role/policy-based authorization are not interoperable with those in identity policy-based authorization.
Table 2 System-defined permissions
|
Role/Policy Name |
Description |
Type |
Dependencies |
|
BSS Administrator |
Permissions to perform operations (except for real-name authentication and account deletion) in My Account.
This is generally granted to the administrator. |
System-defined role |
None |
|
BSS ReadonlyAccess |
Read-only permissions for My Account. |
System-defined policy |
None |
|
BSS FinanceAccess |
Financial administrator of My Account, who has full permissions for financial operations. |
System-defined policy |
None |
Table 3 lists the common operations supported by system-defined policies and roles for My Account.
Table 3 Common operations supported by system-defined permissions
|
Operation |
BSS Administrator |
BSS ReadonlyAccess |
BSS FinanceAccess |
|
Modifying account information |
Supported |
Not supported |
Not supported |
Identity Policy-based Authorization
My Account supports identity policy-based authorization. Table 4 lists all the system-defined identity policies for My Account. System-defined policies in identity policy-based authorization are not interoperable with those in role/policy-based authorization.
Table 4 System-defined identity policies for My Account
|
Identity Policy Name |
Description |
Type |
|
BillingFullAccessPolicy |
Permissions to perform operations in Billing Center, My Account (except for real-name authentication and account deletion), Cost Center, and Enterprise Center. This is generally granted to the administrator. |
System-defined identity policy |
|
BillingOperatorPolicy |
Permissions to view information in Billing Center, My Account, Cost Center, and Enterprise Center, for example, to view the change, management, and use of cloud services. This policy does not have financial permissions. This is generally granted to the technical personnel, such as R&D and O&M personnel. |
System-defined identity policy |
|
BillingFinancePolicy |
Permissions for financial operations, including payments, expenditures, invoicing, and costs. This policy does not have permissions to modify cloud services. This is generally granted to financial personnel. |
System-defined identity policy |
Table 5 lists the common operations supported by system-defined identity policies for My Account.
Table 5 Common operations supported by system-defined policies
|
Operation |
BillingFullAccessPolicy |
BillingOperatorPolicy |
BillingFinancePolicy |
|
Modifying account information |
Supported |
Supported |
Not supported |
|
Viewing the promotion data of Recommendations and Rebates by cloud promoters |
Supported |
Supported |
Supported |
|
Joining the program for getting rebates from recommendations |
Supported |
Supported |
Supported |
|
Viewing my privileges and prizes |
Supported |
Supported |
Supported |
