VPC Endpoint (VPCEP)

The Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

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

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

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 SCP.
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 SCP statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your 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 VPC Endpoint, see Resources.
The Condition Key column contains keys that you can specify in the Condition element of an SCP 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 VPC Endpoint, see Conditions.

The following table lists the actions that you can define in SCP statements for VPC Endpoint.

**Table 1** Actions Supported by VPC Endpoint
Action	Description	Access Level	Resource Type (*: required)	Condition Key
vpcep:endpoints:create	Grants permission to create a VPC endpoint for a specified service.	write	endpoints *	vpcep:VpceServiceName vpcep:VpceServiceOrgPath vpcep:VpceServiceOwner
			vpc *	-
			routeTable	-
			subnet	-
			-	g:RequestTag/<tag-key> g:TagKeys g:EnterpriseProjectId
vpcep:endpoints:delete	Grants permission to delete a VPC endpoint.	write	endpoints *	g:ResourceTag/<tag-key> vpcep:VpceServiceName
vpcep:endpoints:list	Grants permission to query VPC endpoints.	list	endpoints *	-
vpcep:endpoints:list	Grants permission to query VPC endpoints.	list	-	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 *	vpcep:VpceServiceName vpcep:VpceServiceOrgPath vpcep:VpceServiceOwner g:ResourceTag/<tag-key>
			routeTable	-
			subnet	-
vpcep:endpoints:updateRouteTables	Grants permission to modify route tables of a VPC endpoint.	write	endpoints *	g:ResourceTag/<tag-key>
vpcep:endpoints:updateRouteTables	Grants permission to modify route tables of a VPC endpoint.	write	routeTable *	-
vpcep:endpoints:updatePolicy	Grants permission to modify a VPC endpoint policy.	write	endpoints *	g:ResourceTag/<tag-key>
vpcep:endpoints:deletePolicy	Grants permission to delete a VPC endpoint policy.	write	endpoints *	g:ResourceTag/<tag-key>
vpcep:endpointServices:create	Grants permission to create a VPC endpoint service.	write	endpointServices *	vpcep:VpceServicePrivateDnsName
			vpc *	-
			-	g:RequestTag/<tag-key> g:TagKeys g:EnterpriseProjectId
vpcep:endpointServices:list	Grants permission to query VPC endpoint services.	list	endpointServices *	-
vpcep:endpointServices:list	Grants permission to query VPC endpoint services.	list	-	g:EnterpriseProjectId
vpcep:endpointServices:get	Grants permission to query details of a VPC endpoint service.	read	endpointServices *	g:ResourceTag/<tag-key>
vpcep:endpointServices:update	Grants permission to modify a VPC endpoint service.	write	endpointServices *	g:ResourceTag/<tag-key>
vpcep:endpointServices:delete	Grants permission to delete a VPC endpoint service.	write	endpointServices *	g:ResourceTag/<tag-key>
vpcep:endpointServices:updateName	Grants permission to change the name of a VPC endpoint service.	write	endpointServices *	-
vpcep:endpointServices:describe	Grants permission to query basic information about a VPC endpoint service.	read	-	-
vpcep:endpointServices:listPublic	Grants permission to query public VPC endpoint services.	list	endpointServices *	-
vpcep:endpointServices:listPermissions	Grants permission to query whitelist records of a VPC endpoint service.	list	endpointServices *	-
vpcep:endpointServices:updatePermissions	Grants permission to batch add or delete whitelist records of a VPC endpoint service.	permission_management	endpointServices *	-
vpcep:endpointServices:updatePermissions		permission_management	-	vpcep:VpceEndpointOrgPath vpcep:VpceEndpointOwner
vpcep:endpointServices:createPermissions	Grants permission to batch add whitelist records of a VPC endpoint service.	permission_management	endpointServices *	-
vpcep:endpointServices:createPermissions		permission_management	-	vpcep:VpceEndpointOrgPath vpcep:VpceEndpointOwner
vpcep:endpointServices:deletePermissions	Grants permission to batch delete whitelist records of a VPC endpoint service.	permission_management	endpointServices *	-
vpcep:endpointServices:updatePermissionsDescription	Grants permission to update the whitelist description of a VPC endpoint service.	write	endpointServices *	-
vpcep:endpointServices:listConnections	Grants permission to query connections of a VPC endpoint service.	list	endpointServices *	-
vpcep:endpointServices:updateConnections	Grants permission to accept or reject a VPC endpoint.	write	endpointServices *	-
vpcep:endpointServices:updateConnectionDescription	Grants permission to update the description of a VPC endpoint connection.	write	endpointServices *	-
vpcep::listResourceTags	Grants permission to query resources by tag.	list	endpoints	-
vpcep::listResourceTags	Grants permission to query resources by tag.	list	endpointServices	-
vpcep::updateResourceTags	Grants permission to batch add tags to or delete tags from a VPC endpoint service or VPC endpoint.	tagging	endpoints	-
vpcep::updateResourceTags		tagging	endpointServices	-
vpcep::getProjectTags	Grants permission to query resource tags of a tenant.	read	endpoints	-
vpcep::getProjectTags	Grants permission to query resource tags of a tenant.	read	endpointServices	-
vpcep::listQuotas	Grants permission to query the quotas of your resources, including the quota of VPC endpoint services and the quota of VPC endpoints.	read	-	-
vpcep::listVersionDetails	Grants permission to query versions of VPC Endpoint APIs.	list	-	-
vpcep::listSpecifiedVersion	Grants permission to query information about a VPC Endpoint API version.	list	-	-

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

**Table 2** Actions and dependencies supported by VPC Endpoint 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	-

Resources

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

The following table lists the resource types that you can define in SCP statements for VPC Endpoint.

**Table 3** Resource types supported by VPC Endpoint
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

A Condition element lets you specify conditions for when an SCP 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, IAM 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 VPC Endpoint. 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 SCP can be applied only when its request conditions are met. For supported condition operators, see Condition operators.

The following table lists the condition keys that you can define in SCPs for VPC Endpoint. You can include these condition keys to specify conditions for when your SCP is in effect.

**Table 4** Service-specific condition keys supported by VPC Endpoint
Service-specific Condition Key	Type	Single-valued/Multivalued	Description
vpcep:VpceServiceName	string	Single-valued	Filters access by VPC endpoint service name.
vpcep:VpceServiceOwner	string	Single-valued	Filters access by VPC endpoint service owner.
vpcep:VpceServicePrivateDnsName	string	Single-valued	Filters access by the value of 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	Single-valued	Filters access by the organization path of the VPC endpoint owner.
vpcep:VpceEndpointOwner	string	Single-valued	Filters access by the value of accountId of the VPC endpoint owner.
vpcep:VpcId	string	Multivalued	Filters accesses by VPC ID.