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

Global accelerator

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 GA, 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 GA, 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 GA.

Table 1 Actions supported by GA

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

ga:accelerator:list

Grants permission to list accelerators.

List

accelerator *

-

-

ga:accelerator:create

Grants permission to create an accelerator.

Write

accelerator *

g:EnterpriseProjectId

-

-

ga:accelerator:get

Grants permission to get an accelerator.

Read

accelerator *

-

ga:accelerator:update

Grants permission to update an accelerator.

Write

accelerator *

-

ga:accelerator:delete

Grants permission to delete an accelerator.

Write

accelerator *

-

ga:listener:list

Grants permission to list listeners.

List

listener *

-

-

ga:listener:create

Grants permission to create a listener.

Write

listener *

-

-

-

ga:listener:get

Grants permission to get a listener.

Read

listener *

g:ResourceTag/<tag-key>

-

ga:listener:update

Grants permission to update 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 list endpoint groups.

List

endpointgroup *

-

-

ga:endpointgroup:create

Grants permission to create an endpoint group.

Write

endpointgroup *

-

-

-

ga:RequestRegionId

ga:endpointgroup:get

Grants permission to get 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 list endpoints.

List

endpoint *

-

-

ga:endpoint:create

Grants permission to create an endpoint.

Write

endpoint *

-

-

-

ga:endpoint:get

Grants permission to get an endpoint.

Read

endpoint *

-

ga:endpoint:update

Grants permission to update an endpoint.

Write

endpoint *

-

ga:endpoint:delete

Grants permission to delete an endpoint.

Write

endpoint *

-

ga:healthcheck:list

Grants permission to list health checks.

List

healthcheck *

-

-

ga:healthcheck:create

Grants permission to create a healthcheck.

Write

healthcheck *

-

-

ga:healthcheck:get

Grants permission to get a healthcheck.

Read

healthcheck *

-

-

ga:healthcheck:update

Grants permission to update a healthcheck.

Write

healthcheck *

-

-

ga:healthcheck:delete

Grants permission to delete a healthcheck.

Write

healthcheck *

-

-

ga:tag:create

Grants permission to create tags for a resource.

Tagging

accelerator

g:ResourceTag/<tag-key>

-

listener

g:ResourceTag/<tag-key>

-

ga:tag:delete

Grants permission to delete tags of a specified resource.

Tagging

accelerator *

g:ResourceTag/<tag-key>

-

listener *

g:ResourceTag/<tag-key>

-

g:TagKeys

ga:tag:get

Grants permission to query tags of resource.

Read

accelerator

g:ResourceTag/<tag-key>

-

listener

g:ResourceTag/<tag-key>

ga:tag:list

Grants permission to list tags.

List

-

-

-

ga::listResourcesByTag

Grants permission to list resource instances by tag.

List

-

g:TagKeys

ga:tag:listResourcesByTag

ga:ipgroup:list

Grants permission to list ip groups.

List

ipgroup *

-

-

ga:ipgroup:create

Grants permission to create an ip group.

Write

ipgroup *

-

-

ga:ipgroup:get

Grants permission to get an ip group.

Read

ipgroup *

-

-

ga:ipgroup:update

Grants permission to update an ip group.

Write

ipgroup *

-

-

ga:ipgroup:delete

Grants permission to delete an ip group.

Write

ipgroup *

-

-

ga:ipgroup:addIps

Grants permission to add ips of a specified ip group.

Write

ipgroup *

-

-

ga:ipgroup:removeIps

Grants permission to remove ips of a specified ip group.

Write

ipgroup *

-

-

ga:ipgroup:associateListener

Grants permission to associate listener of a specified ip group.

Write

ipgroup *

-

-

ga:ipgroup:disassociateListener

Grants permission to disassociate listener of a specified ip group.

Write

ipgroup *

-

-

ga::listByoipPools

Grants permission to list byoip pools.

List

-

-

ga:byoippool:list

ga:logtank:list

Grants permission to list logtanks.

List

logtank *

-

-

ga:logtank:create

Grants permission to create logtank.

Write

logtank *

-

-

ga:logtank:get

Grants permission to get logtank info.

Read

logtank *

-

-

ga:logtank:update

Grants permission to modify logtank.

Write

logtank *

-

-

ga:logtank:delete

Grants permission to delete logtank.

Write

logtank *

-

-

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

Table 2 Actions and dependencies supported by GA 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 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 GA.

Table 3 Resource types supported by GA

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

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, ga) 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 GA

The following table lists the condition keys that you can define in identity policies for GA. 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 GA

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

ga:RequestRegionId

string

Single-valued

Filters access by the region id that is passed in the request.

ga:RequestResourceType

string

Single-valued

Filters access by the resource type that is passed in the request.

ga:RequestResourceId

string

Single-valued

Filters access by the resource id that is passed in the request.

ga:RequestIpAddress

string

Single-valued

Filters access by the ip address that is passed in the request.

ga:RequestDomainName

string

Single-valued

Filters access by the domain name that is passed in the request.

ga:RegionId

string

Single-valued

Filters access by endpoint-group region id.

ga:ResourceType

string

Single-valued

Filters access by endpoint resource type.

ga:ResourceId

string

Single-valued

Filters access by endpoint resource id.

ga:IpAddress

string

Single-valued

Filters access by endpoint ip address.

ga:DomainName

string

Single-valued

Filters access by endpoint domain name.