Permissions

If you need to assign different permissions to employees in your enterprise to access your VPC Endpoint resources, you can use Identity and Access Management (IAM) to manage fine-grained permissions. IAM provides identity authentication, permissions management, and access control, helping you to securely access your Huawei Cloud resources. If your HUAWEI ID does not require IAM 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 control access to specific Huawei Cloud resources. For example, if you want some software developers in your enterprise to use VPC Endpoint resources but do not want them to delete the resources or perform any other high-risk operations, you can grant permissions to use the resources but not permissions 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
Name	Authorization Using	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 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 identity policies Custom 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.

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 attach 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 users or grant the users 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, see IAM Service Overview.

Role/Policy-based Authorization

VPC Endpoint 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 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.

VPC Endpoint is a project-level service deployed for specific 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 VPC Endpoint resources in the selected projects. If you set Scope to All resources, the users have permissions for VPC Endpoint resources in all region-specific projects. When accessing VPC Endpoint, users need to switch to a region where they have been authorized to use this service.

Table 2 lists all the system-defined permissions for VPC Endpoint. System-defined policies and system-defined identity policies in the two authorization models are not interoperable.

**Table 2** VPC Endpoint system-defined permissions
Role/Policy Name	Description	Type	Dependency
VPCEndpoint Administrator	Full permissions for VPC Endpoint NOTE: If your account has applied for fine-grained permissions, configure fine-grained policies for VPC Endpoint system permissions, instead of the VPCEndpoint Administrator policy.	System-defined role	This role depends on Server Administrator, VPC Administrator, and DNS Administrator roles in the same project.
VPCEndpoint FullAccess	Full permissions for VPC Endpoint	System-defined policy	None
VPCEndpoint ReadOnlyAccess	Read-only permissions for VPC Endpoint. Users with these permissions can only view VPC Endpoint resources.	System-defined policy	None

Table 3 lists common operations supported by VPC Endpoint system-defined permissions.

**Table 3** Common operations supported by each system-defined policy
Operation	VPCEndpointFullAccess	VPCEndpointReadOnlyAccess	VPCEP Administrator
Creating a VPC endpoint service	√	x	√
Deleting a VPC endpoint service	√	x	√
Querying a VPC endpoint service	√	√	√
Modifying a VPC endpoint service	√	x	√
Accepting or rejecting a VPC endpoint for a VPC endpoint service	√	x	√
Adding or removing a whitelist record	√	x	√
Creating a VPC endpoint	√	x	√
Deleting a VPC endpoint	√	x	√
Modifying a VPC endpoint	√	x	√
Querying a VPC endpoint	√	√	√
Configuring access control for a VPC endpoint	√	x	√
Adding or deleting a resource tag	√	x	√
Querying resource tags	√	√	√

Identity Policy-based Authorization

VPC Endpoint supports authorization with identity policies. Table 4 lists all the system-defined identity policies for VPC Endpoint. System-defined identity policies and system-defined policies in the two authorization models are not interoperable.

**Table 4** System-defined identity policies for VPC Endpoint
Policy Name	Description	Type
VPCEPFullAccessPolicy	Full permissions for VPC Endpoint	System-defined identity policies
VPCEPReadOnlyPolicy	Read-only permissions for VPC Endpoint	System-defined identity policies

Table 5 lists the common operations supported by system-defined identity policies for VPC Endpoint.

**Table 5** Common operations supported by system-defined identity policies of VPC Endpoint
Operation	VPCEPFullAccessPolicy	VPCEPReadOnlyPolicy
Creating a VPC endpoint service	√	x
Deleting a VPC endpoint service	√	x
Querying a VPC endpoint service	√	√
Modifying a VPC endpoint service	√	x
Accepting or rejecting a VPC endpoint for a VPC endpoint service	√	x
Adding or removing a whitelist record	√	x
Creating a VPC endpoint	√	x
Deleting a VPC endpoint	√	x
Modifying a VPC endpoint	√	x
Querying a VPC endpoint	√	√
Configuring access control for a VPC endpoint	√	x
Adding or deleting a resource tag	√	x
Querying resource tags	√	√