Updated on 2026-10-29 GMT+08:00

EventGrid

IAM provides system-defined identity policies to define typical cloud service permissions. 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 eg, 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 eg, 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 eg.

Table 1 Actions supported by eg

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

eg:subscriptions:createSubscription

Grants permission to create a subscription.

Write

subscriptions *

-

eg:subscriptions:create

-

eg:subscriptions:list

Grants permission to query subscription list.

List

subscriptions *

-

-

eg:subscriptions:updateSubscription

Grants permission to update subscription.

Write

subscriptions *

eg:subscriptions:update

eg:subscriptions:getSubscription

Grants permission to query subscription detail.

Read

subscriptions *

eg:subscriptions:get

eg:subscriptions:deleteSubscription

Grants permission to delete subscription.

Write

subscriptions *

eg:subscriptions:delete

eg:subscriptions:operate

Grants permission to operate subscription.

Write

subscriptions *

-

eg:channels:create

Grants permission to create channel.

Write

channels *

-

-

-

g:EnterpriseProjectId

eg:channels:list

Grants permission to query channel list.

List

channels *

-

-

eg:channels:update

Grants permission to update channel.

Write

channels *

-

eg:channels:getChannel

Grants permission to query channel detail.

Read

channels *

eg:channels:get

eg:channels:delete

Grants permission to delete channel.

Write

channels *

-

eg:event:getEventTrace

Grants permission to query event trace detail.

Read

-

-

eg:sources:get

eg:event:getEvent

Grants permission to query event detail.

Read

-

-

eg:sources:get

eg:event:list

Grants permission to query event list.

List

-

-

eg:sources:list

eg:channels:putEvents

Grants permission to put events.

Write

channels *

g:ResourceTag/<tag-key>

-

eg:event:check

Grants permission to check put events.

Write

-

-

eg:channels:get

eg:sources:create

Grants permission to create source.

Write

-

-

-

eg:sources:listSources

Grants permission to query source list.

List

sources *

-

eg:sources:list

eg:sources:update

Grants permission to update source.

Write

sources *

g:ResourceTag/<tag-key>

-

eg:sources:getSource

Grants permission to query source detail.

Read

sources *

g:ResourceTag/<tag-key>

eg:sources:get

eg:sources:delete

Grants permission to delete source.

Write

sources *

g:ResourceTag/<tag-key>

-

eg:targetCatalogs:list

Grants permission to query event target list.

List

-

-

-

eg:schemas:discover

Grants permission to discover event schema.

Write

-

-

-

eg:schemas:create

Grants permission to create event schema.

Write

-

-

-

eg:schemas:list

Grants permission to query event schema list.

List

-

-

-

eg:schemas:update

Grants permission to update event schema.

Write

-

-

-

eg:schemas:getSchema

Grants permission to query event schema detail.

Read

-

-

eg:schemas:get

eg:schemas:delete

Grants permission to delete event schema.

Write

-

-

-

eg:schemas:createVersion

Grants permission to create event schema version.

Write

-

-

-

eg:schemas:listVersions

Grants permission to query the list of event schema versions.

List

-

-

eg:schemas:get

eg:schemas:getVersion

Grants permission to query event schema version detail.

Read

-

-

-

eg:schemas:deleteVersion

Grants permission to delete event schema version.

Write

-

-

-

eg:connections:create

Grants permission to create connection.

Write

connections *

-

-

eg:connections:list

Grants permission to create connection list.

List

connections *

-

-

eg:connections:update

Grants permission to update connection.

Write

connections *

g:ResourceTag/<tag-key>

-

eg:connections:get

Grants permission to query connection detail.

Read

connections *

g:ResourceTag/<tag-key>

-

eg:connections:delete

Grants permission to delete connection.

Write

connections *

g:ResourceTag/<tag-key>

-

eg:quota:listQuotas

Grants permission to query quota list.

List

-

-

eg:quota:list

eg:apiVersion:list

Grants permission to query api version.

List

-

-

-

eg:endpoints:update

Grants permission to update endpoint.

Write

endpoints *

g:ResourceTag/<tag-key>

-

eg:endpoints:delete

Grants permission to delete endpoint.

Write

endpoints *

g:ResourceTag/<tag-key>

-

eg:endpoints:create

Grants permission to create endpoint.

Write

endpoints *

-

-

eg:endpoints:list

Grants permission to query endpoint list.

List

endpoints *

-

-

eg::replaceObsNotification

Grants permission to replace the FG notification of OBS with EG notification.

Write

-

-

eg:subscriptions:create

eg:pubMetrics:list

Grants permission to query channel monitoring metrics.

List

-

-

-

eg:subMetrics:list

Grants permission to query subscription monitoring metrics.

List

-

-

-

eg:samples:list

Grants permission to query event sample list.

List

-

-

-

eg:eventStreaming:create

Grants permission to create event streaming.

Write

-

-

eg:subscriptions:create

eg:eventStreaming:list

Grants permission to query event streaming list.

List

eventStreaming *

-

eg:sources:list

eg:eventStreaming:update

Grants permission to update event streaming.

Write

eventStreaming *

g:ResourceTag/<tag-key>

eg:subscriptions:update

eg:eventStreaming:get

Grants permission to query event streaming list.

Read

eventStreaming *

g:ResourceTag/<tag-key>

eg:subscriptions:get

eg:eventStreaming:delete

Grants permission to delete event streaming.

Write

eventStreaming *

g:ResourceTag/<tag-key>

eg:subscriptions:delete

eg:eventStreaming:operate

Grants permission to operate event streaming.

Write

eventStreaming *

g:ResourceTag/<tag-key>

eg:subscriptions:update

eg:feature:list

Grants permission to query the list of supported features.

List

-

-

eg:quota:list

eg:erjobs:create

Grants permission to create professional event stream job.

Write

erjobs *

-

-

eg:erjobs:list

Grants permission to query professional event stream job list.

List

erjobs *

-

-

eg:erjobs:delete

Grants permission to delete professional event stream job.

Write

erjobs *

-

-

eg:erjobs:getJob

Grants permission to query professional event stream job detail.

Read

erjobs *

-

eg:erjobs:get

eg:erjobs:update

Grants permission to update professional event stream job.

Write

erjobs *

-

-

eg:erjobs:operate

Grants permission to operate professional event stream job.

Write

erjobs *

-

-

eg:erjobs:validate

Grants permission to validate professional event stream job.

Write

erjobs *

-

-

eg:erjobs:getSyncDetail

Grants permission to query sync detail of professional event stream job.

Read

erjobs *

-

eg:erjobs:get

eg:erclusters:getAvailabilityZone

Grants permission to query availability zone.

Read

-

-

eg:erclusters:list

eg:erclusters:create

Grants permission to create professional event stream cluster.

Write

erclusters *

-

-

eg:erclusters:listClusters

Grants permission to query professional event stream cluster list.

List

erclusters *

-

eg:erclusters:list

eg:erclusters:delete

Grants permission to delete professional event stream cluster.

Write

erclusters *

-

-

eg:erclusters:get

Grants permission to query professional event stream cluster detail.

Read

erclusters *

-

-

eg:erclusters:update

Grants permission to update professional event stream cluster.

Write

erclusters *

-

-

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

Table 2 Actions and dependencies supported by eg APIs

API

Action

Dependencies

POST /v1/{project_id}/subscriptions

eg:subscriptions:createSubscription

-

GET /v1/{project_id}/subscriptions

eg:subscriptions:list

-

PUT /v1/{project_id}/subscriptions/{subscription_id}

eg:subscriptions:updateSubscription

-

GET /v1/{project_id}/subscriptions/{subscription_id}

eg:subscriptions:getSubscription

-

DELETE /v1/{project_id}/subscriptions/{subscription_id}

eg:subscriptions:deleteSubscription

-

PUT /v1/{project_id}/subscriptions/{subscription_id}/sources/{source_id}

eg:subscriptions:updateSubscription

-

POST /v1/{project_id}/subscriptions/{subscription_id}/targets

eg:subscriptions:updateSubscription

-

PUT /v1/{project_id}/subscriptions/{subscription_id}/targets/{target_id}

eg:subscriptions:updateSubscription

-

GET /v1/{project_id}/subscriptions/{subscription_id}/targets/{target_id}

eg:subscriptions:getSubscription

-

DELETE /v1/{project_id}/subscriptions/{subscription_id}/targets/{target_id}

eg:subscriptions:updateSubscription

-

POST /v1/{project_id}/subscriptions/operation

eg:subscriptions:operate

-

POST /v1/{project_id}/channels

eg:channels:create

-

GET /v1/{project_id}/channels

eg:channels:list

-

PUT /v1/{project_id}/channels/{channel_id}

eg:channels:update

-

GET /v1/{project_id}/channels/{channel_id}

eg:channels:getChannel

-

DELETE /v1/{project_id}/channels/{channel_id}

eg:channels:delete

-

GET /v1/{project_id}/events/trace/detail/{trace_id}

eg:event:getEventTrace

-

GET /v1/{project_id}/events/detail/{trace_id}

eg:event:getEvent

-

GET /v1/{project_id}/traced-events

eg:event:list

-

POST /v1/{project_id}/channels/{channel_id}/events

eg:channels:putEvents

-

POST /v1/{project_id}/events/check

eg:event:check

-

POST /v1/{project_id}/sources

eg:sources:create

-

GET /v1/{project_id}/sources

eg:sources:listSources

-

PUT /v1/{project_id}/sources/{source_id}

eg:sources:update

-

GET /v1/{project_id}/sources/{source_id}

eg:sources:getSource

-

DELETE /v1/{project_id}/sources/{source_id}

eg:sources:delete

-

GET /v1/{project_id}/target-catalogs

eg:targetCatalogs:list

-

POST /v1/{project_id}/schema-discover

eg:schemas:discover

-

POST /v1/{project_id}/schemas

eg:schemas:create

-

GET /v1/{project_id}/schemas

eg:schemas:list

-

PUT /v1/{project_id}/schemas/{schema_id}

eg:schemas:update

-

GET /v1/{project_id}/schemas/{schema_id}

eg:schemas:getSchema

-

DELETE /v1/{project_id}/schemas/{schema_id}

eg:schemas:delete

-

POST /v1/{project_id}/schemas/{schema_id}/versions

eg:schemas:createVersion

-

GET /v1/{project_id}/schemas/{schema_id}/versions

eg:schemas:listVersions

-

GET /v1/{project_id}/schemas/{schema_id}/versions/{version}

eg:schemas:getVersion

-

DELETE /v1/{project_id}/schemas/{schema_id}/versions/{version}

eg:schemas:deleteVersion

-

POST /v1/{project_id}/connections

eg:connections:create

-

GET /v1/{project_id}/connections

eg:connections:list

-

PUT /v1/{project_id}/connections/{connection_id}

eg:connections:update

-

GET /v1/{project_id}/connections/{connection_id}

eg:connections:get

-

DELETE /v1/{project_id}/connections/{connection_id}

eg:connections:delete

-

GET /v1/{project_id}/quotas

eg:quota:listQuotas

-

GET /

eg:apiVersion:list

-

GET /v1/{project_id}/subscription-triggers/{func_urn}

eg:subscriptions:list

-

GET /v1/{project_id}/subscription-triggers/workflow/{workflow_id}

eg:subscriptions:list

-

PUT /v1/{project_id}/endpoints/{endpoint_id}

eg:endpoints:update

-

DELETE /v1/{project_id}/endpoints/{endpoint_id}

eg:endpoints:delete

-

POST /v1/{project_id}/endpoints

eg:endpoints:create

-

GET /v1/{project_id}/endpoints

eg:endpoints:list

-

POST /v1/{project_id}/subscriptions/obsbuckets/{bucket_name}/refurbishobs

eg::replaceObsNotification

-

-

eg:pubMetrics:list

-

-

eg:subMetrics:list

-

GET /v1/{project_id}/samples

eg:samples:list

-

POST /v1/{project_id}/eventstreamings

eg:eventStreaming:create

-

GET /v1/{project_id}/eventstreamings

eg:eventStreaming:list

-

PUT /v1/{project_id}/eventstreamings/{eventstreaming_id}

eg:eventStreaming:update

-

GET /v1/{project_id}/eventstreamings/{eventstreaming_id}

eg:eventStreaming:get

-

DELETE /v1/{project_id}/eventstreamings/{eventstreaming_id}

eg:eventStreaming:delete

-

POST /v1/{project_id}/eventstreamings/operate/{eventstreaming_id}

eg:eventStreaming:operate

-

-

eg:feature:list

-

POST /v1/{project_id}/eventrouter/jobs

eg:erjobs:create

-

GET /v1/{project_id}/eventrouter/jobs

eg:erjobs:list

-

DELETE /v1/{project_id}/eventrouter/jobs/{job_id}

eg:erjobs:delete

-

GET /v1/{project_id}/eventrouter/jobs/{job_id}

eg:erjobs:getJob

-

PUT /v1/{project_id}/eventrouter/jobs/{job_id}

eg:erjobs:update

-

POST /v1/{project_id}/eventrouter/jobs/{job_id}/action

eg:erjobs:operate

-

POST /v1/{project_id}/eventrouter/jobs/validation

eg:erjobs:validate

-

POST /v1/{project_id}/eventrouter/jobs/{job_id}/syncDetail

eg:erjobs:getSyncDetail

-

GET /v1/{project_id}/eventrouter/clusters/availability-zone

eg:erclusters:getAvailabilityZone

-

POST /v1/{project_id}/eventrouter/clusters

eg:erclusters:create

-

GET /v1/{project_id}/eventrouter/clusters

eg:erclusters:listClusters

-

DELETE /v1/{project_id}/eventrouter/clusters/{cluster_id}

eg:erclusters:delete

-

GET /v1/{project_id}/eventrouter/clusters/{cluster_id}

eg:erclusters:get

-

PUT /v1/{project_id}/eventrouter/clusters/{cluster_id}

eg:erclusters:update

-

Resources

A resource type (Resource) defines the resources on which an identity policy takes effect. In Table 3, if a specific operation has an associated resource type, then in the identity policy statement containing that operation, the policy will only take effect on the specified resource when the corresponding resource URN is provided. If no resource URN is specified, the policy will apply to all resources under the designated resource type. If no resource type is defined, the default value of Resource is *, meaning the policy applies to all resources. In addition, you can set conditions in the identity policy to further refine and restrict the resource type.

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

Table 3 Resource types supported by eg

Resource Type

URN

sources

eg:<region>:<account-id>:sources:<source-id>

erclusters

eg:<region>:<account-id>:erclusters:<cluster-id>

connections

eg:<region>:<account-id>:connections:<connection-id>

eventStreaming

eg:<region>:<account-id>:eventStreaming:<eventStreaming-id>

endpoints

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

channels

eg:<region>:<account-id>:channels:<channel-id>

subscriptions

eg:<region>:<account-id>:subscriptions:<subscription-id>

erjobs

eg:<region>:<account-id>:erjobs:<job-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, eg) 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 eg

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

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

eg:SubscriptionTargetProviderType

string

Multivalued

Filters access based on subscription target provider.

eg:SubscriptionTargetName

string

Multivalued

Filters access based on subscription target name.