AAD

If you need to assign different permissions to personnel in your enterprise to access your AAD resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides functions such as identity authentication, permissions management, and access control. If your Huawei account works good for you and you do not need an IAM account to manage user permissions, then you may skip over this chapter.

IAM can be used free of charge. You pay only for the resources in your account.

With IAM, you can control the access to Huawei Cloud resources through authorization. For example, some software developers in your enterprise need to use AAD 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 AAD resources.

There are two types of IAM authorization: policy/role authorization and identity policy authorization.

The differences and relationships between the two authorization models are as follows:

**Table 1** Differences between role/policy-based authorization and identity policy-based authorization
Authorization Model	Authorization Using	Permission	Authorization Method	Scenario
Role/Policy-based Authorization	User-permission-authorization scope	System-defined roles System-defined policies Custom policies	Granting a role or policy to a subject	To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It is hard to provide fine-grained permissions control using authorization by user groups and a limited number of condition keys. This method is suitable for small- and medium-sized enterprises.
Identity Policy-based Authorization	User-policy	System-defined identity policies Custom identity policies	Granting an identity policy to a subject 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.

Assume that you want to grant IAM users the permissions needed to create ECSs in CN North-Beijing4 and OBS buckets in CN South-Guangzhou. With role/policy-based authorization, the administrator needs to create two custom policies and assign both to the IAM users. With identity policy-based authorization, the administrator only needs to create one custom identity policy and configure the condition key g:RequestedRegion for the policy, and then attach the policy to the principals or grant the principals the access permissions to the specified regions. Identity policy-based authorization is more flexible than role/policy-based authorization.

Policies/identity policies and actions in the two authorization scenarios are not interoperable. You are advised to use the identity policy-based authorization model. Role/Policy-based Permissions Management and Identity Policy-based Permissions Management describe the system permissions of the two models.

For details about IAM, see IAM Service Overview.

Role/Policy-based Permissions Management

AAD supports role/policy-based authorization. By default, new IAM users do not have any permissions. You need to add a user to one or more groups, and attach permission policies or roles to these groups. Users inherit permissions from their groups and can perform specified operations on cloud services based on the permissions.

AAD is a global service deployed and accessed without specifying any physical region. AAD permissions are assigned to users in the global project, and users do not need to switch regions when accessing AAD.

Table 1 lists all AAD system permissions. System-defined policies in role/policy-based authorization and identity policy-based authorization are not interoperable.

**Table 2** System-defined permissions for AAD
Role/Policy Name	Description	Type
CAD Administrator	Administrator permissions for AAD. This role has all permissions for AAD.	System-defined role
AAD FullAccess	All permissions for AAD	System-defined policy
AAD ReadOnlyAccess	Read-only permissions for AAD.	System-defined policy

Table 3 describes the common operations supported by each system-defined permission of AAD. Select the permissions as needed.

**Table 3** Common operations supported by system permissions of AAD
Operation	CAD Administrator	AAD ReadOnlyAccess	AAD FullAccess
Querying details of an instance	√	√	√
Querying the instance list	√	√	√
Creating an instance	√	×	√
Modifying an instance	√	×	√
Querying the certificate list	√	√	√
Uploading a certificate	√	×	√
Deleting a certificate	√	×	√
Obtaining domain name details	√	√	√
Obtaining the domain name list	√	√	√
Adding a domain name.	√	×	√
Editing a domain name	√	×	√
Deleting a domain name	√	×	√
Querying a protection policy	√	√	√
Querying the list of domain names with an enabled protection policy	√	√	√
Creating a protection policy	√	×	√
Updating a protection policy	√	×	√
Deleting a protection policy.	√	×	√
Creating a blacklist or whitelist rule	√	×	√
Deleting a blacklist or whitelist rule	√	×	√
Querying the blacklist and whitelist rule list	√	√	√
Querying quotas	√	√	√
Querying a forwarding rule	√	√	√
Exporting forwarding rules	√	×	√
Adding a forwarding rule	√	×	√
Modifying a forwarding rule	√	×	√
Deleting a forwarding rule	√	×	√
Viewing statistics reports	√	√	√
Querying an alarm notification	√	√	√
Creating an alarm notification	√	×	√

Roles or Policies on Which AAD Console Functions Depend

**Table 4** Roles or policies required for AAD console operations
Console Function	Dependent Services	Policy/Role Required
Adding a domain name	Cloud Certificate Manager (CCM)	If the origin server uses the HTTPS forwarding protocol, pulling certificates requires the SCM ReadOnlyAccess permission.
Configuring AAD logs	Log Tank Service (LTS)	The LTS ReadOnlyAccess system policy is required to select log group and log stream names created in LTS.
Enabling alarm notifications	Simple Message Notification (SMN)	The SMN ReadOnlyAccess system policy is required to obtain SMN topic groups.
Configuring instance tags	Tag Management Service (TMS)	Tag keys can be created only after the TMS FullAccess system policy is added.
Purchasing an AAD instance	Enterprise Project Management Service (EPS)	You can select an enterprise project when purchasing an instance only after adding the EPS ReadOnlyAccess system policy.

Identity Policy-based Permissions Management

AAD supports identity policy-based authorization. Table 1 lists all the system-defined identity policies for AAD. System-defined identity policies and system-defined policies in the two authorization models are not interoperable.

**Table 5** System-defined identity policies of AAD
Policy Name	Description	Policy Type
AADReadOnlyAccessPolicy	All permissions for AAD	System-defined identity policies
AADFullAccessPolicy	Read-only permissions for AAD. Users granted these permissions can only view AAD information.	System-defined identity policies

Table 6 lists the common operations supported by system-defined identity policies of AAD.

**Table 6** Common operations supported by system-defined identity policies of AAD
Operation	AADReadOnlyAccessPolicy	AADFullAccessPolicy
Querying details of an instance	√	√
Querying the instance list	√	√
Creating an instance	×	√
Modifying an instance	×	√
Querying the certificate list	√	√
Uploading a certificate	×	√
Deleting a certificate	×	√
Obtaining domain name details	√	√
Obtaining the domain name list	√	√
Adding a domain name.	×	√
Editing a domain name	×	√
Deleting a domain name	×	√
Querying a protection policy	√	√
Querying the list of domain names with an enabled protection policy	√	√
Creating a protection policy	×	√
Updating a protection policy	×	√
Deleting a protection policy.	×	√
Creating a blacklist or whitelist rule	×	√
Deleting a blacklist or whitelist rule	×	√
Querying the blacklist and whitelist rule list	√	√
Querying quotas	√	√
Querying a forwarding rule	√	√
Exporting forwarding rules	×	√
Adding a forwarding rule	×	√
Modifying a forwarding rule	×	√
Deleting a forwarding rule	×	√
Viewing statistics reports	√	√
Querying an alarm notification	√	√
Creating an alarm notification	×	√

Identity Policies on Which Console Functions Depend

**Table 7** Identity policies of services on which AAD console functions depend
Console Function	Dependent Services	Policy/Role Required
Adding a domain name	Cloud Certificate Manager (CCM)	If the origin server uses the HTTPS forwarding protocol, pulling certificates requires the SCMReadOnlyPolicy permission.
Configuring AAD logs	Log Tank Service (LTS)	The log groups and log streams created in LTS can be selected only after the LTSReadOnlyAccessPolicy system identity policy is added.
Enabling alarm notifications	Simple Message Notification (SMN)	SMN topic groups can be obtained only after the SMNReadOnlyPolicy system identity policy is added.
Configuring instance tags	Tag Management Service (TMS)	Tag keys can be created only after the TMSReadOnlyPolicy system identity policy is added.
Purchasing an AAD instance	Enterprise Project Management Service (EPS)	Enterprise projects can be selected only after the EPSReadOnlyPolicy system identity policy is added.