Permissions Management
If you need to assign different permissions to employees in your enterprise to access your VPC resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you securely manage access to your HUAWEI CLOUD resources.
With IAM, you can use your HUAWEI CLOUD account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use VPC resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using VPC resources.
If your HUAWEI CLOUD account does not need individual IAM users for permissions management, you may skip over this section.
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see the IAM Service Overview.
VPC Permissions
By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.
VPC is a project-level service deployed and accessed in specific physical regions. To assign VPC permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing VPC, the users need to switch to a region where they have been authorized to use VPC.
You can grant users permissions by using roles and policies.
- Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant VPC users only the permissions for managing a certain type of resources. Most policies define permissions based on APIs. For the API actions supported by VPC, see Permissions Policies and Supported Actions.
Table 1 lists all the system-defined roles and policies supported by VPC.
|
Policy Name |
Description |
Policy Type |
Dependencies |
|---|---|---|---|
|
VPC FullAccess |
All operations on VPC. |
System-defined policy |
None |
|
VPC ReadOnlyAccess |
Read-only permissions on VPC. |
System-defined policy |
None |
|
VPC Administrator |
All operations on VPC. To be granted this permission, users must also have the Tenant Guest permission. |
System-defined role |
Dependent on the Tenant Guest policy. |
Table 2 lists the common operations supported by each system-defined policy or role of VPC. Select the policies or roles as required.
|
Operation |
VPC ReadOnlyAccess |
VPC Administrator |
VPC FullAccess |
|---|---|---|---|
|
Creating a VPC |
x |
√ |
√ |
|
Modifying a VPC |
x |
√ |
√ |
|
Deleting a VPC |
x |
√ |
√ |
|
Viewing VPC information |
√ |
√ |
√ |
|
Creating a subnet |
x |
√ |
√ |
|
Viewing subnet information |
√ |
√ |
√ |
|
Modifying a subnet |
x |
√ |
√ |
|
Deleting a subnet |
x |
√ |
√ |
|
Creating a security group |
x |
x |
√ |
|
Viewing security group information |
√ |
x |
√ |
|
Modifying a security group |
x |
x |
√ |
|
Deleting a security group |
x |
x |
√ |
|
Adding a security group rule |
x |
x |
√ |
|
Viewing a security group rule |
√ |
x |
√ |
|
Modifying a security group rule |
x |
x |
√ |
|
Deleting a security group rule |
x |
x |
√ |
|
Creating a network ACL |
x |
√ |
√ |
|
Viewing a network ACL |
√ |
√ |
√ |
|
Modifying a network ACL |
x |
√ |
√ |
|
Deleting a network ACL |
x |
√ |
√ |
|
Adding a network ACL rule |
x |
√ |
√ |
|
Modifying a network ACL rule |
x |
√ |
√ |
|
Deleting a network ACL rule |
x |
√ |
√ |
|
Creating a VPC peering connection |
x |
√ |
√ |
|
Modifying a VPC peering connection |
x |
√ |
√ |
|
Deleting a VPC peering connection |
x |
√ |
√ |
|
Creating a route table |
x |
√ |
√ |
|
Deleting a route table |
x |
√ |
√ |
|
Adding a route |
x |
√ |
√ |
|
Modifying a route |
x |
√ |
√ |
|
Deleting a route |
x |
√ |
√ |
Last Article: Billing
Next Article: Basic Concepts
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.