Help Center/ Simple Message Notification/ API Reference/ Permissions Policies and Supported Actions/ Actions Supported by Identity Policy-based Authorization
Updated on 2026-09-18 GMT+08:00

Actions Supported by Identity Policy-based Authorization

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

Table 1 Actions supported by SMN

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

smn:topic:create

Grants permission to create topic.

Write

topic *

-

-

-

smn:topic:listTopic

Grants permission to query topic list.

List

topic *

-

smn:topic:list

-

g:EnterpriseProjectId

smn:topic:updateTopic

Grants permission to update topic.

Write

topic *

smn:topic:update

smn:topic:get

Grants permission to query topic detail.

Read

topic *

smn:topic:list

smn:topic:delete

Grants permission to delete topic.

Write

topic *

-

smn:topic:listAttributes

Grants permission to query topic policy.

List

topic *

smn:topic:list

smn:topic:deleteAttribute

Grants permission to delete topic policy.

Write

topic *

smn:topic:update

smn:topic:updateAttribute

Grants permission to update topic policy.

Write

topic *

smn:topic:update

-

smn:topic:subscribe

Grants permission to create subscription of topic.

Write

topic *

smn:topic:update

-

smn:topic:listSubscriptionsByTopic

Grants permission to list subscription of topic.

List

topic *

smn:topic:list

smn:topic:listSubscriptions

Grants permission to list subscription of all topic.

List

topic *

-

smn:topic:list

smn:topic:deleteSubscription

Grants permission to delete subscription of topic.

Write

topic *

smn:topic:update

smn:topic:updateSubscription

Grants permission to update subscription of topic.

Write

topic *

smn:topic:update

smn:topic:publish

Grants permission to publish message.

Write

topic *

-

-

smn:template:create

Grants permission to create template.

Write

template *

-

-

smn:template:listTemplates

Grants permission to list template.

List

template *

-

smn:template:list

smn:template:update

Grants permission to update template.

Write

template *

-

-

smn:template:get

Grants permission to query template detail.

Read

template *

-

smn:template:list

smn:template:delete

Grants permission to delete template.

Write

template *

-

-

smn:tag:create

Grants permission to create tag of topic.

Write

topic *

-

-

smn:tag:delete

Grants permission to delete tag of topic.

Write

topic *

smn:tag:update

-

smn:tag:batchModify

Grants permission to batch modify tags of topic.

Write

topic *

smn:tag:update

-

smn:tag:list

Grants permission to get tags of topic.

Read

topic *

g:ResourceTag/<tag-key>

-

smn:topic:createLogTank

Grants permission to bind logstream and loggroup of topic.

Write

topic *

-

smn:topic:listLogTank

Grants permission to get logstream and loggroup of topic.

List

topic *

smn:topic:list

smn:topic:updateLogTank

Grants permission to list logstream and loggroup of topic.

Write

topic *

smn:topic:update

smn:topic:deleteLogTank

Grants permission to delete logstream and loggroup of topic.

Write

topic *

smn:topic:update

smn:topic:createKmsKey

Grants permission to bind kms key of topic.

Write

topic *

-

smn:topic:getKmsKey

Grants permission to get kms key of topic.

List

topic *

-

smn:topic:updateKmsKey

Grants permission to update kms key of topic.

Write

topic *

-

smn:topic:deleteKmsKey

Grants permission to delete kms key of topic.

Write

topic *

-

smn:topic:createNotifyPolicy

Grants permission to create notify policy of topic

Write

topic *

-

-

smn:topic:updateNotifyPolicy

Grants permission to update notify policy of topic

Write

topic *

-

-

smn:topic:getNotifyPolicy

Grants permission to query notify policy of topic

Read

topic *

-

-

smn:topic:deleteNotifyPolicy

Grants permission to delete notify policy of topic

Write

topic *

-

-

smn:topic:listTopicsWithAssociatedResources

Grants permission to query the list of topics and associated resource information.

List

topic *

-

-

-

g:EnterpriseProjectId

smn:application:create

Grants permission to create an application.

Write

application *

-

-

smn:application:delete

Grants permission to delete applications.

Write

application *

-

-

smn:application:list

Grants permission to query applications.

List

application *

-

-

smn:application:get

Grants permission to query application details.

Read

application *

-

-

smn:application:publish

Grants permission to publish messages in the application.

Write

application *

-

-

smn:application:createPlatform

Grants permission to create a platform.

Write

application *

-

-

smn:application:deletePlatform

Grants permission to delete the platform.

Write

application *

-

-

smn:application:updatePlatform

Grants permission to update the platform.

Write

application *

-

-

smn:application:listPlatform

Grants permission to query the platform list.

List

application *

-

-

smn:application:getPlatform

Grants permission to query platform details.

Read

application *

-

-

smn:subscriptionUser:create

Grants permission to create subscription user.

Write

subscription_user *

-

-

-

smn:subscriptionUser:delete

Grants permission to delete subscription user.

Write

subscription_user *

-

-

smn:subscriptionUser:update

Grants permission to update subscription user.

Write

subscription_user *

-

-

smn:subscriptionUser:list

Grants permission to query subscription user list.

List

subscription_user *

-

-

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

Table 2 Actions and dependencies supported by SMN APIs

API

Action

Dependencies

POST /v2/{project_id}/notifications/topics

smn:topic:create

-

GET /v2/{project_id}/notifications/topics

smn:topic:listTopic

-

PUT /v2/{project_id}/notifications/topics/{topic_urn}

smn:topic:updateTopic

-

GET /v2/{project_id}/notifications/topics/{topic_urn}

smn:topic:get

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}

smn:topic:delete

-

GET /v2/{project_id}/notifications/topics/{topic_urn}/attributes

smn:topic:listAttributes

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/attributes

smn:topic:deleteAttribute

-

PUT /v2/{project_id}/notifications/topics/{topic_urn}/attributes/{name}

smn:topic:updateAttribute

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/attributes/{name}

smn:topic:deleteAttribute

-

POST /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions

smn:topic:subscribe

-

GET /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions

smn:topic:listSubscriptionsByTopic

-

PUT /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions/{subscription_urn}

smn:topic:updateSubscription

-

DELETE /v2/{project_id}/notifications/subscriptions/{subscription_urn}

smn:topic:deleteSubscription

-

DELETE /v2/{project_id}/notifications/subscriptions

smn:topic:deleteSubscription

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions/{subscription_urn}

smn:topic:deleteSubscription

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions

smn:topic:deleteSubscription

-

GET /v2/{project_id}/notifications/subscriptions

smn:topic:listSubscriptions

-

POST /v2/{project_id}/notifications/topics/{topic_urn}/publish

smn:topic:publish

-

POST /v2/{project_id}/notifications/message_template

smn:template:create

-

GET /v2/{project_id}/notifications/message_template

smn:template:listTemplates

-

PUT /v2/{project_id}/notifications/message_template/{message_template_id}

smn:template:update

-

GET /v2/{project_id}/notifications/message_template/{message_template_id}

smn:template:get

-

DELETE /v2/{project_id}/notifications/message_template/{message_template_id}

smn:template:delete

-

POST /v2/{project_id}/{resource_type}/{resource_id}/tags

smn:tag:create

-

GET /v2/{project_id}/{resource_type}/{resource_id}/tags

smn:tag:list

-

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

smn:tag:batchModify

  • smn:tag:create
  • smn:tag:delete

DELETE /v2/{project_id}/{resource_type}/{resource_id}/tags/{key}

smn:tag:delete

-

GET /v2/{project_id}/{resource_type}/tags

smn:tag:list

-

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

smn:tag:list

-

GET /v2/{project_id}/notifications/topics/{topic_urn}/logtanks

smn:topic:listLogTank

-

POST /v2/{project_id}/notifications/topics/{topic_urn}/logtanks

smn:topic:createLogTank

-

PUT /v2/{project_id}/notifications/topics/{topic_urn}/logtanks/{logtank_id}

smn:topic:updateLogTank

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/logtanks/{logtank_id}

smn:topic:deleteLogTank

-

POST /v2/{project_id}/notifications/subscriptions/filter_polices

smn:topic:updateSubscription

-

PUT /v2/{project_id}/notifications/subscriptions/filter_polices

smn:topic:updateSubscription

-

DELETE /v2/{project_id}/notifications/subscriptions/filter_polices

smn:topic:updateSubscription

-

POST /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions/from-subscription-users

smn:topic:subscribe

-

POST /v2/{project_id}/notifications/topics/{topic_urn}/notify-policy

smn:topic:createNotifyPolicy

smn:topic:listSubscriptionsByTopic

PUT /v2/{project_id}/notifications/topics/{topic_urn}/notify-policy/{notify_policy_id}

smn:topic:updateNotifyPolicy

smn:topic:listSubscriptionsByTopic

GET /v2/{project_id}/notifications/topics/{topic_urn}/notify-policy

smn:topic:getNotifyPolicy

-

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/notify-policy/{notify_policy_id}

smn:topic:deleteNotifyPolicy

-

GET /v2/{project_id}/notifications/topics/{topic_urn}/statistics

smn:topic:get

-

POST /v2/{project_id}/notifications/topics/{topic_urn}/kms

smn:topic:createKmsKey

smn:topic:get

PUT /v2/{project_id}/notifications/topics/{topic_urn}/kms/{id}

smn:topic:updateKmsKey

  • smn:topic:get
  • smn:topic:getKmsKey

GET /v2/{project_id}/notifications/topics/{topic_urn}/kms

smn:topic:getKmsKey

smn:topic:get

DELETE /v2/{project_id}/notifications/topics/{topic_urn}/kms/{id}

smn:topic:deleteKmsKey

  • smn:topic:get
  • smn:topic:getKmsKey

GET /v2/{project_id}/notifications/topics-with-associated-resources

smn:topic:listTopicsWithAssociatedResources

-

-

smn:application:create

-

-

smn:application:delete

-

-

smn:application:list

-

-

smn:application:get

-

-

smn:application:publish

-

-

smn:application:createPlatform

-

-

smn:application:deletePlatform

-

-

smn:application:updatePlatform

-

-

smn:application:listPlatform

-

-

smn:application:getPlatform

-

POST /v2/{domain_id}/subscription-users

smn:subscriptionUser:create

-

DELETE /v2/{domain_id}/subscription-users/{id}

smn:subscriptionUser:delete

-

PUT /v2/{domain_id}/subscription-users/{id}

smn:subscriptionUser:update

-

GET /v2/{domain_id}/subscription-users

smn:subscriptionUser:list

-

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 SMN.

Table 3 Resource types supported by SMN

Resource Type

URN

application

smn::<account-id>:application:<application-id>

topic

smn:<region>:<account-id>:topic:<topic-id>

subscription_user

smn::<account-id>:subscription_user:<subscription-user-id>

template

smn:<region>:<account-id>:template:<template-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, smn) 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 SMN

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

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

smn:TargetOrgPath

string

Single-valued

Filters access based on the Organizations Path of the topic attributes.

smn:TargetOrgId

string

Single-valued

Filters access based on the Organizations Id of the topic attributes.

smn:TargetAccountId

string

Single-valued

Filters access based on the Account Id of the topic attributes.

smn:Protocol

string

Single-valued

Filters access subscription protocol.

smn:Endpoint

string

Single-valued

Filters access subscription endpoint.

smn:TopicOwnerOrgPath

string

Single-valued

Filters access based on the Organizations path of the user to which the topic belongs.

smn:TopicOwnerOrgId

string

Single-valued

Filters access based on the Organizations Id of the user to which the topic belongs.

smn:Protocol

string

Single-valued

Filters access subscription protocol.

smn:Endpoint

string

Single-valued

Filters access subscription endpoint.