Permissions

If you need to assign different permissions to personnel in your enterprise to access your enterprise switches, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources. If your HUAWEI ID does not need individual IAM users, you may skip this chapter.

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

With IAM, you can create IAM users and assign permissions to control their access to specific resources. For example, if you want some software developers in your enterprise to use enterprise switches but do not want them to delete enterprise switches or perform any other high-risk operations, you can grant permissions to use enterprise switches but not permission to delete them.

IAM supports role/policy-based authorization and identity policy-based authorization.

The following table describes the differences between these two authorization models.

**Table 1** Differences between role/policy-based and identity policy-based authorization
Authorization Model	Authorization Using	Permissions	Authorization Method	Scenario
Role/Policy	User-permission-authorization scope	System-defined roles System-defined policies Custom policies	Granting 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 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	Policies	System-defined policies Custom identity policies	Granting 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.

Assume that you want to grant IAM users the permissions to create VPCs 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 attach both to the IAM users. With identity policy-based authorization, the administrator only needs to create one custom 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 models are not interoperable. You are advised to use the identity policy-based authorization model. For details about system-defined permissions, see Role/Policy-based Authorization and Identity Policy-based Authorization.

For more information about IAM, see IAM Service Overview.

Role/Policy-based Authorization

Enterprise Switch 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.

Enterprise Switch is a project-level service deployed and accessed in specific physical regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for enterprise switches in the selected projects. If you set Scope to All resources, the users have permissions for enterprise switches in all region-specific projects. You need to switch to the authorized region before accessing Enterprise Switch.

Enterprise Switch uses the same system permissions as VPC. Table 2 lists all system permissions for VPC. System-defined policies in role/policy-based authorization are not interoperable with those in identity policy-based authorization.

**Table 2** System-defined permissions for VPC
Role/Policy Name	Description	Type	Dependencies
VPCFullAccess	Full permissions for VPC.	System-defined policy	None
VPCReadOnlyAccess	Read-only permissions on VPC.	System-defined policy	None
VPC Administrator	Most permissions on VPC, excluding creating, modifying, deleting, and viewing security groups and security group rules. To be granted this permission, users must also have the Tenant Guest permission.	System-defined role	Tenant Guest policy, which must be attached in the same project as VPC Administrator.

Table 3 lists the common operations supported by system-defined permissions for Enterprise Switch.

**Table 3** Common operations supported by system-defined permissions
Operation	VPC ReadOnlyAccess	VPC Administrator	VPC FullAccess	Tenant Guest
Creating an enterprise switch	Not supported	Supported	Not supported	Not supported
Modifying an enterprise switch	Not supported	Supported	Not supported	Not supported
Deleting an enterprise switch	Not supported	Supported	Not supported	Not supported
Viewing an enterprise switch	Not supported	Supported	Not supported	Supported
Creating a Layer 2 connection	Not supported	Supported	Not supported	Not supported
Modifying a Layer 2 connection	Not supported	Supported	Not supported	Not supported
Deleting a Layer 2 connection	Not supported	Supported	Not supported	Not supported
Viewing a Layer 2 connection	Not supported	Supported	Not supported	Supported
Viewing specifications	Not supported	Supported	Not supported	Supported
Viewing quotas	Not supported	Supported	Not supported	Supported
Viewing the AZ	Not supported	Supported	Not supported	Supported
Binding a virtual IP address	Not supported	Supported	Not supported	Not supported
Unbinding a virtual IP address	Not supported	Supported	Not supported	Not supported

Identity Policy-based Authorization

Enterprise Switch supports identity policy-based authorization. Table 4 lists all the system-defined identity policies for Enterprise Switch. 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 Enterprise Switch
Identity Policy Name	Description	Type
ESWFullAccessPolicy	Full permissions for Enterprise Switch	System-defined identity policy
ESWReadOnlyPolicy	Read-only permissions for Enterprise Switch	System-defined identity policy

Table 5 lists the common operations supported by system-defined identity policies for Enterprise Switch.

**Table 5** Common operations supported by system-defined identity policies
Operation	ESWReadOnlyPolicy	ESWFullAccessPolicy
Creating an enterprise switch	Not supported	Supported
Modifying an enterprise switch	Not supported	Supported
Deleting an enterprise switch	Not supported	Supported
Viewing an enterprise switch	√	Supported
Creating a Layer 2 connection	Not supported	Supported
Modifying a Layer 2 connection	Not supported	Supported
Deleting a Layer 2 connection	Not supported	Supported
Viewing a Layer 2 connection	√	Supported
Viewing specifications	√	Supported
Viewing quotas	√	Supported
Viewing the AZ	√	Supported
Binding a virtual IP address	Not supported	Supported
Unbinding a virtual IP address	Not supported	Supported