Permissions Management¶
If you need to assign different permissions to personnel in your enterprise to access your VPN resources created on the cloud service platform, 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 securely manage access to your resources.
With IAM, you can use your account to create IAM users, and assign permissions to the users to control their access to specific cloud resources. For example, some software developers in your enterprise need to use VPN resources but should not be allowed to delete them or perform any high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using VPN resources.
If your account does not need individual IAM users for permissions management, skip this section, which has no impact on using functions of VPN.
IAM is a free service. You only pay for the resources in your account.
For more information about IAM, see IAM Service Overview.
VPN Permissions¶
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and 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.
VPN is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for VPN in the selected projects. If you set Scope to All resources, users have permissions for VPN in all region-specific projects. When accessing VPN, the users need to switch to the authorized region.
You can grant permissions by using roles or policies.
Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. There are only a limited number of roles for granting permissions to users. Some roles depend other roles to take effect. When you assign such roles to users, remember to assign the roles they depend on. 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, administrators can grant IAM users only permissions to manage VPN resources of a certain type.
Table 1 lists all system-defined permissions for VPN.
System Role/Policy Name | Description | Dependency |
|---|---|---|
VPN Administrator (not recommended) | Administrator permissions for VPN. Users with these permissions can perform all operations on VPN. Users with these permissions have the VPC Administrator and Tenant Guest permissions by default.
|
|
VPN FullAccess (recommended) | Full permissions for VPN. | The actions of global services and the region-level actions cannot be configured in the same policy. As such, the following global actions are added: "tms:predefineTags:list" "scm:cert:list" "scm:cert:get" "scm:cert:download" |
VPN ReadOnlyAccess | Read-only permissions on VPN resources. Users who have these permissions can only view information about VPN resources. | The actions of global services and the region-level actions cannot be configured in the same policy. As such, the following global actions are added: "tms:predefineTags:list" "scm:cert:list" "scm:cert:get" |
Table 2 lists the common operations supported by system-defined permissions for VPN.
Operation | VPN Administrator (Not Recommended) | VPN FullAccess (Recommended) | VPN ReadOnlyAccess |
|---|---|---|---|
Creating a VPN gateway | Y |
| x |
Viewing a VPN gateway | Y | Y | Y |
Querying the VPN gateway list | Y | Y | Y |
Updating a VPN gateway | Y |
| x |
Deleting a VPN gateway | Y |
| x |
Creating a VPN connection | Y |
| x |
Viewing a VPN connection | Y | Y | Y |
Querying the VPN connection list | Y | Y | Y |
Updating a VPN connection | Y |
| x |
Deleting a VPN connection | Y |
| x |
Creating a customer gateway | Y |
| x |
Viewing a customer gateway | Y |
| Y |
Querying the customer gateway list | Y |
| Y |
Updating a customer gateway | Y |
| x |
Deleting a customer gateway | Y |
| x |
Creating a VPN connection monitor | Y |
| x |
Querying a VPN connection monitor | Y |
| Y |
Querying the VPN connection monitor list | Y |
| Y |
Deleting a VPN connection monitor | Y |
| x |
Note
Classic VPN: For details about how to create a user and grant VPC permissions to the user, see Creating a User and Granting VPC Permissions.