Global Accelerator (GA)

The Organizations service provides Service Control Policies 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 topic 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 (such as list, read, or write). This classification helps you understand the level of access that an action grants when you use it in an SCP 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 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 Global Accelerator, 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 Global Accelerator, see Conditions.

The following table lists the actions that you can define in SCP statements for Global Accelerator.

**Table 1** Actions supported by Global Accelerator
Action	Description	Access Level	*Resource Type (: Required)**	Condition Key
ga:accelerator:list	Grants permission to query global accelerators.	list	accelerator *	-
ga:accelerator:create	Grants permission to create a global accelerator.	write	accelerator *	g:EnterpriseProjectId
ga:accelerator:create	Grants permission to create a global accelerator.	write	-	g:RequestTag/<tag-key> g:TagKeys
ga:accelerator:get	Grants permission to query the details of a global accelerator.	read	accelerator *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
ga:accelerator:update	Grants permission to update a global accelerator.	write	accelerator *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
ga:accelerator:delete	Grants permission to delete a global accelerator.	write	accelerator *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
ga:listener:list	Grants permission to query listeners.	list	listener *	-
ga:listener:create	Grants permission to add a listener.	write	listener *	-
ga:listener:create	Grants permission to add a listener.	write	-	g:RequestTag/<tag-key> g:TagKeys
ga:listener:get	Grants permission to query the details of a listener.	read	listener *	g:ResourceTag/<tag-key>
ga:listener:update	Grants permission to modify a listener.	write	listener *	g:ResourceTag/<tag-key>
ga:listener:delete	Grants permission to delete a listener.	write	listener *	g:ResourceTag/<tag-key>
ga:endpointgroup:list	Grants permission to query endpoint groups.	list	endpointgroup *	-
ga:endpointgroup:create	Grants permission to add an endpoint group.	write	endpointgroup *	-
ga:endpointgroup:create	Grants permission to add an endpoint group.	write	-	ga:RequestRegionId
ga:endpointgroup:get	Grants permission to query the details of an endpoint group.	read	endpointgroup *	ga:RegionId
ga:endpointgroup:update	Grants permission to update an endpoint group.	write	endpointgroup *	ga:RegionId
ga:endpointgroup:delete	Grants permission to delete an endpoint group.	write	endpointgroup *	ga:RegionId
ga:endpoint:list	Grants permission to query endpoints.	list	endpoint *	-
ga:endpoint:create	Grants permission to add an endpoint.	write	endpoint *	-
ga:endpoint:create	Grants permission to add an endpoint.	write	-	ga:RequestResourceType ga:RequestResourceId ga:RequestIpAddress ga:RequestDomainName
ga:endpoint:get	Grants permission to query the details of an endpoint.	read	endpoint *	ga:ResourceType ga:ResourceId ga:IpAddress ga:DomainName
ga:endpoint:update	Grants permission to modify an endpoint.	write	endpoint *	ga:ResourceType ga:ResourceId ga:IpAddress ga:DomainName
ga:endpoint:delete	Grants permission to remove an endpoint.	write	endpoint *	ga:ResourceType ga:ResourceId ga:IpAddress ga:DomainName
ga:healthcheck:list	Grants permission to query health checks.	list	healthcheck *	-
ga:healthcheck:create	Grants permission to configure a health check.	write	healthcheck *	-
ga:healthcheck:get	Grants permission to query health check details.	read	healthcheck *	-
ga:healthcheck:update	Grants permission to modify a health check.	write	healthcheck *	-
ga:healthcheck:delete	Grants permission to delete a health check.	write	healthcheck *	-
ga:tag:create	Grants permission to add tags in batches.	tagging	accelerator	g:ResourceTag/<tag-key>
			listener	g:ResourceTag/<tag-key>
			-	g:RequestTag/<tag-key> g:TagKeys
ga:tag:delete	Grants permission to delete tags in batches.	tagging	accelerator *	g:ResourceTag/<tag-key>
			listener *	g:ResourceTag/<tag-key>
			-	g:TagKeys
ga:tag:get	Grants permission to query tags of a specific resource.	read	accelerator	g:ResourceTag/<tag-key>
ga:tag:get	Grants permission to query tags of a specific resource.	read	listener	g:ResourceTag/<tag-key>
ga:tag:list	Grants permission to query the tags.	list	-	-
ga::listResourcesByTag	Grants permission to query resources by tag.	list	-	g:TagKeys
ga:ipgroup:list	Grants permission to query IP address groups.	list	ipgroup *	-
ga:ipgroup:create	Grants permission to create an IP address group.	write	ipgroup *	-
ga:ipgroup:get	Grants permission to query the details of an IP address group.	read	ipgroup *	-
ga:ipgroup:update	Grants permission to modify an IP address group.	write	ipgroup *	-
ga:ipgroup:delete	Grants permission to delete an IP address group.	write	ipgroup *	-
ga:ipgroup:addIps	Grants permission to add IP addresses to an IP address group in batches.	write	ipgroup *	-
ga:ipgroup:removeIps	Grants permission to remove IP addresses from an IP address group in batches.	write	ipgroup *	-
ga:ipgroup:associateListener	Grants permission to associate an IP address group with a listener.	write	ipgroup *	-
ga:ipgroup:disassociateListener	Grant permission to disassociate an IP address group from a listener.	write	ipgroup *	-
ga::listByoipPools	Grants permission to query your own IP address pools.	list	-	-
ga:logtank:list	Grants permission to query logs.	list	logtank *	-
ga:logtank:create	Grants permission to create a log.	write	logtank *	-
ga:logtank:get	Grants permission to query the details of a log.	read	logtank *	-
ga:logtank:update	Grants permission to modify a log.	write	logtank *	-
ga:logtank:delete	Grants permission to delete a log.	write	logtank *	-

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

**Table 2** Actions and dependencies supported by Global Accelerator APIs
API	Action	Dependencies
GET /v1/accelerators	ga:accelerator:list	-
POST /v1/accelerators	ga:accelerator:create	-
GET /v1/accelerators/{accelerator_id}	ga:accelerator:get	-
PUT /v1/accelerators/{accelerator_id}	ga:accelerator:update	-
DELETE /v1/accelerators/{accelerator_id}	ga:accelerator:delete	-
GET /v1/listeners	ga:listener:list	-
POST /v1/listeners	ga:listener:create	-
GET /v1/listeners/{listener_id}	ga:listener:get	-
PUT /v1/listeners/{listener_id}	ga:listener:update	-
DELETE /v1/listeners/{listener_id}	ga:listener:delete	-
GET /v1/endpoint-groups	ga:endpointgroup:list	-
POST /v1/endpoint-groups	ga:endpointgroup:create	-
GET /v1/endpoint-groups/{endpoint_group_id}	ga:endpointgroup:get	-
PUT /v1/endpoint-groups/{endpoint_group_id}	ga:endpointgroup:update	-
DELETE /v1/endpoint-groups/{endpoint_group_id}	ga:endpointgroup:delete	-
GET /v1/endpoint-groups/{endpoint_group_id}/endpoints	ga:endpoint:list	-
POST /v1/endpoint-groups/{endpoint_group_id}/endpoints	ga:endpoint:create	-
GET /v1/endpoint-groups/{endpoint_group_id}/endpoints/{endpoint_id}	ga:endpoint:get	-
PUT /v1/endpoint-groups/{endpoint_group_id}/endpoints/{endpoint_id}	ga:endpoint:update	-
DELETE /v1/endpoint-groups/{endpoint_group_id}/endpoints/{endpoint_id}	ga:endpoint:delete	-
GET /v1/health-checks	ga:healthcheck:list	-
POST /v1/health-checks	ga:healthcheck:create	-
GET /v1/health-checks/{health_check_id}	ga:healthcheck:get	-
PUT /v1/health-checks/{health_check_id}	ga:healthcheck:update	-
DELETE /v1/health-checks/{health_check_id}	ga:healthcheck:delete	-
POST /v1/{resource_type}/{resource_id}/tags/create	ga:tag:create	-
DELETE /v1/{resource_type}/{resource_id}/tags/delete	ga:tag:delete	-
GET /v1/{resource_type}/{resource_id}/tags	ga:tag:get	-
POST /v1/{resource_type}/resource-instances/filter	ga::listResourcesByTag	-
POST /v1/{resource_type}/resource-instances/count	ga::listResourcesByTag	-
GET /v1/{resource_type}/tags	ga:tag:list	-
GET /v1/ip-groups	ga:ipgroup:list	-
POST /v1/ip-groups	ga:ipgroup:create	-
GET /v1/ip-groups/{ip_group_id}	ga:ipgroup:get	-
PUT /v1/ip-groups/{ip_group_id}	ga:ipgroup:update	-
DELETE /v1/ip-groups/{ip_group_id}	ga:ipgroup:delete	-
POST /v1/ip-groups/{ip_group_id}/add-ips	ga:ipgroup:addIps	-
POST /v1/ip-groups/{ip_group_id}/remove-ips	ga:ipgroup:removeIps	-
POST /v1/ip-groups/{ip_group_id}/associate-listener	ga:ipgroup:associateListener	-
POST /v1/ip-groups/{ip_group_id}/disassociate-listener	ga:ipgroup:disassociateListener	-
GET /v1/byoip-pools	ga::listByoipPools	-
GET /v1/logtanks	ga:logtank:list	-
POST /v1/logtanks	ga:logtank:create	-
GET /v1/logtanks/{logtank_id}	ga:logtank:get	-
PUT /v1/logtanks/{logtank_id}	ga:logtank:update	-
DELETE /v1/logtanks/{logtank_id}	ga:logtank:delete	-

Resources

A resource type indicates the resources that an SCP is applied. If you specify a resource type for any action in Table 3, the resource URN must be specified in the SCP statements using that action, and the SCP only applies 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 policy to define resource types.

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

**Table 3** Resource types supported by Global Accelerator
Resource Type	URN
ipgroup	ga::<account-id>:ipgroup:<ipgroup-id>
endpoint	ga::<account-id>:endpoint:<endpoint-id>
accelerator	ga::<account-id>:accelerator:<accelerator-id>
logtank	ga::<account-id>:logtank:<logtank-id>
listener	ga::<account-id>:listener:<listener-id>
healthcheck	ga::<account-id>:healthcheck:<healthcheck-id>
endpointgroup	ga::<account-id>:endpointgroup:<endpointgroup-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, 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, ga:) only apply to operations of Global Accelerator. 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 Global Accelerator. You can include these condition keys to specify conditions for when your SCP is in effect.

**Table 4** Service-specific condition keys supported by Global Accelerator
Service-specific Condition Key	Type	Single-valued/Multivalued	Description
ga:RequestRegionId	string	Single-valued	Filters access by region ID passed in the request.
ga:RequestResourceType	string	Single-valued	Filters access by resource type passed in the request.
ga:RequestResourceId	string	Single-valued	Filters access by resource ID passed in the request.
ga:RequestIpAddress	string	Single-valued	Filters access by IP address passed in the request.
ga:RequestDomainName	string	Single-valued	Filters access by domain name passed in the request.
ga:RegionId	string	Single-valued	Filters access by region of the endpoint group.
ga:ResourceType	string	Single-valued	Filters access by resource type of the endpoint group.
ga:ResourceId	string	Single-valued	Filters access by resource ID of the endpoint group.
ga:IpAddress	string	Single-valued	Filters access by IP address of the endpoint group.
ga:DomainName	string	Single-valued	Filters access by domain name of the endpoint group.