Help Center/ VPC Endpoint/ API Reference/ Permissions Policies and Supported Actions/ Introduction
Updated on 2025-05-15 GMT+08:00
View PDF
Share

Introduction

This section describes fine-grained permissions management for your VPC Endpoint resources. If your Huawei account does not need individual IAM users, you can skip this section.

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. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

You can grant users permissions using roles and policies. Roles are provided by IAM to define service-based permissions that match user's job responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

If you want to allow or deny the access to an API, use policy-based authorization.

An account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user wants to query VPC endpoint services using an API, the user must have been granted permissions that allow the vpcep:epservices:list action.

Supported Actions

VPC Endpoint provides system-defined policies that can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

  • Permissions: statements in a policy that allow or deny certain operations.
  • APIs: REST APIs that can be called in a custom policy.
  • Actions: specific operations that are allowed or denied in a custom policy.
  • IAM projects/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. For details about the differences between IAM projects and enterprise projects, see Differences Between IAM and Enterprise Management.

VPC Endpoint supports the following actions that can be defined in custom policies:

  • VPC Endpoint Services: contains actions supported by all VPC endpoint service APIs, such as the API for creating a VPC endpoint service.
  • VPC Endpoints: contains actions supported by all VPC endpoint APIs, such as the API for creating a VPC endpoint.
  • Resource Quotas: contains actions for querying quotas of VPC Endpoint resources.
  • Tags: contains actions supported by all tag management APIs, such as the API for querying a resource tag.
Parent Topic: Permissions Policies and Supported Actions