Updated on 2025-11-06 GMT+08:00

VPC Endpoint

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

  • The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
  • The Resource Type column indicates whether the action supports resource-level permissions.
    • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
    • If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
    • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

    For details about the resource types defined by VPCEP, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
    • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
    • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
    • If the Condition Key column is empty (-) for an action, the action does not support any condition keys.

    For details about the condition keys defined by VPCEP, see Conditions.

  • The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for VPCEP.

Table 1 Actions supported by VPCEP

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

vpcep:endpoints:create

Grants permission to create a VPC endpoint for a specified service.

Write

endpoints *

-

vpc *

-

routeTable

-

subnet

-

-

vpcep:endpoints:delete

Grants permission to delete a VPC endpoint.

Write

endpoints *

-

vpcep:endpoints:list

Grants permission to query VPC endpoints.

List

endpoints *

-

-

-

g:EnterpriseProjectId

vpcep:endpoints:get

Grants permission to query details of a VPC endpoint.

Read

endpoints *

g:ResourceTag/<tag-key>

-

vpcep:endpoints:update

Grants permission to update the Whitelist of a VPC endpoint.

Write

endpoints *

-

routeTable

-

subnet

-

vpcep:endpoints:upgrade

Upgrade endpoint to endpoint_pro.

Write

endpoints *

-

vpcep:endpoints:updateRouteTables

Grants permission to modify the routeTable associated with a VPC endpoint.

Write

endpoints *

g:ResourceTag/<tag-key>

vpcep:endpoints:update

routeTable *

-

vpcep:endpoints:updatePolicy

Grants permission to modify the policy of a gateway VPC endpoint.

Write

endpoints *

g:ResourceTag/<tag-key>

vpcep:endpoints:update

vpcep:endpoints:deletePolicy

Grants permission to delete the policy of a gateway VPC endpoint.

Write

endpoints *

g:ResourceTag/<tag-key>

vpcep:endpoints:delete

vpcep:endpointServices:create

Grants permission to create a VPC endpoint service.

Write

endpointServices *

vpcep:VpceServicePrivateDnsName

vpcep:epservices:create

vpc *

-

-

vpcep:endpointServices:list

Grants permission to query VPC endpoint services.

List

endpointServices *

-

vpcep:epservices:list

-

g:EnterpriseProjectId

vpcep:endpointServices:get

Grants permission to query details of a VPC endpoint service.

Read

endpointServices *

g:ResourceTag/<tag-key>

vpcep:epservices:get

vpcep:endpointServices:update

Grants permission to modify a VPC endpoint service.

Write

endpointServices *

g:ResourceTag/<tag-key>

vpcep:epservices:update

vpcep:endpointServices:delete

Grants permission to delete a VPC endpoint service.

Write

endpointServices *

g:ResourceTag/<tag-key>

vpcep:epservices:delete

vpcep:endpointServices:updateName

Grants permission to change the name of a VPC endpoint service.

Write

endpointServices *

-

vpcep:epservices:update

vpcep:endpointServices:describe

Grants permission to query description a VPC endpoint service.

Read

-

-

vpcep:epserviceDesc:get

vpcep:endpointServices:listPublic

Grants permission to query public endpoint services.

List

endpointServices *

-

vpcep:pubEpservices:list

vpcep:endpointServices:listPermissions

Grants permission to whitelist records of a VPC endpoint service.

List

endpointServices *

-

vpcep:permissions:list

vpcep:endpointServices:updatePermissions

Grants permission to batch adding or deleting whitelist records of a VPC Endpoint Service.

Permission_management

endpointServices *

-

vpcep:permissions:update

-

vpcep:endpointServices:createPermissions

Grants permission to batch adding whitelist records of a VPC Endpoint Service.

Permission_management

endpointServices *

-

vpcep:permissions:update

-

vpcep:endpointServices:deletePermissions

Grants permission to batch deleting whitelist records of a VPC Endpoint Service.

Permission_management

endpointServices *

-

vpcep:permissions:update

vpcep:endpointServices:updatePermissionsDescription

Grants permission to updating the description of a whitelist record of a VPC endpoint service.

Write

endpointServices *

-

vpcep:permissions:update

vpcep:endpointServices:listConnections

Grants permission to query connections of a VPC endpoint service.

List

endpointServices *

-

vpcep:connections:list

vpcep:endpointServices:updateConnections

Grants permission to accept or reject a VPC Endpoint.

Write

endpointServices *

-

vpcep:connections:update

vpcep:endpointServices:updateConnectionDescription

Grants permission to update the description of the VPC endpoint connection.

Write

endpointServices *

-

vpcep:connections:update

vpcep::listResourceTags

Grants permission to query resources by tag.

List

endpoints

-

vpcep:resource:list

endpointServices

-

vpcep::updateResourceTags

Grants permission to add or delete resource tags in batches.

Tagging

endpoints

-

vpcep:tags:update

endpointServices

-

vpcep::getProjectTags

Grants permission to query tags of tenant's resources.

Read

endpoints

-

vpcep:tags:list

endpointServices

-

vpcep::listQuotas

Grants permission to query the quota of resources, including VPC endpoint services and VPC endpoints.

Read

-

-

vpcep:quotas:get

vpcep::listVersionDetails

Grants permission to query versions of VPCEP APIs.

List

-

-

-

vpcep::listSpecifiedVersion

Grants permission to query the version of a specified VPCEP API.

List

-

-

-

Each API of VPCEP usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by VPCEP APIs

API

Action

Dependencies

POST /v1/{project_id}/vpc-endpoints

vpcep:endpoints:create

-

DELETE /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}

vpcep:endpoints:delete

-

GET /v1/{project_id}/vpc-endpoints

vpcep:endpoints:list

-

GET /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}

vpcep:endpoints:get

-

PUT /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}

vpcep:endpoints:update

-

PUT /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}/routetables

vpcep:endpoints:updateRouteTables

-

PUT /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}/policy

vpcep:endpoints:updatePolicy

-

DELETE /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}/policy

vpcep:endpoints:deletePolicy

-

POST /v1/{project_id}/vpc-endpoint-services

vpcep:endpointServices:create

-

GET /v1/{project_id}/vpc-endpoint-services

vpcep:endpointServices:list

-

GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}

vpcep:endpointServices:get

-

PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}

vpcep:endpointServices:update

-

DELETE /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}

vpcep:endpointServices:delete

-

PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/name

vpcep:endpointServices:updateName

-

GET /v1/{project_id}/vpc-endpoint-services/describe

vpcep:endpointServices:describe

-

GET /v1/{project_id}/vpc-endpoint-services/public

vpcep:endpointServices:listPublic

-

GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions

vpcep:endpointServices:listPermissions

-

POST /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions/action

vpcep:endpointServices:updatePermissions

-

POST /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions/batch-create

vpcep:endpointServices:createPermissions

-

POST /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions/batch-delete

vpcep:endpointServices:deletePermissions

-

PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions/{permission_id}

vpcep:endpointServices:updatePermissionsDescription

-

GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/connections

vpcep:endpointServices:listConnections

-

POST /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/connections/action

vpcep:endpointServices:updateConnections

-

PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/connections/description

vpcep:endpointServices:updateConnectionDescription

-

POST /v1/{project_id}/{resource_type}/resource_instances/action

vpcep::listResourceTags

-

POST /v1/{project_id}/{resource_type}/{resource_id}/tags/action

vpcep::updateResourceTags

-

GET /v1/{project_id}/{resource_type}/tags

vpcep::getProjectTags

-

GET /v1/{project_id}/quotas

vpcep::listQuotas

-

GET /

vpcep::listVersionDetails

-

GET /{version}

vpcep::listSpecifiedVersion

-

POST /v2/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/add-server-resources

vpcep:endpointServices:update

-

POST /v2/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/remove-server-resources

vpcep:endpointServices:update

-

POST /v2/{project_id}/vpc-endpoints/{vpc_endpoint_id}/add-availability-zones

vpcep:endpointServices:updateConnections

-

POST /v2/{project_id}/vpc-endpoints/{vpc_endpoint_id}/remove-availability-zones

vpcep:endpointServices:updateConnections

-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for VPCEP.

Table 3 Resource types supported by VPCEP

Resource Type

URN

routeTable

vpc:<region>:<account-id>:routeTable:<route-table-id>

vpc

vpc:<region>:<account-id>:vpc:<vpc-id>

endpointServices

vpcep:<region>:<account-id>:endpointServices:<endpoint-service-id>

subnet

vpc:<region>:<account-id>:subnet:<subnet-id>

endpoints

vpcep:<region>:<account-id>:endpoints:<endpoint-id>

Conditions

Condition Key Overview

A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.

  • The condition key that you specify can be a global condition key or a service-specific condition key.
    • Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
    • Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, vpcep) apply only to operations of the xx service. For details, see Table 4.
    • The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
  • A condition operator, condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see operators.

Service-specific condition keys supported by VPCEP

The following table lists the condition keys that you can define in identity policies for VPCEP. You can include these condition keys to specify conditions for when your identity policy is in effect.

Table 4 Service-specific condition keys supported by VPCEP

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

vpcep:VpceServiceName

string

Single-valued

Filters access by the name of the VPC endpoint service.

vpcep:VpceServiceOwner

string

Single-valued

Filters access by the service owner of the VPC endpoint service (huawei, or an account ID).

vpcep:VpceServicePrivateDnsName

string

Single-valued

Filters access by the vpceServicePrivateDnsName that is passed in the request.

vpcep:VpceServiceOrgPath

string

Single-valued

Filters access by the organization path of the VPC endpoint service owner.

vpcep:VpceEndpointOrgPath

string

Multivalued

Filters access by the organization path of the VPC endpoint owner.

vpcep:VpceEndpointOwner

string

Multivalued

Filters access by the accountId of VPC endpoint owner.