Simple Message Notification (SMN)
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 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. 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 What Are the Differences in Access Control Between IAM and Organizations?
This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.
- For details about how to use these elements to create an IAM custom identity policy, see Creating a Custom Identity Policy.
- 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 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 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.
|
Action |
Description |
Access Level |
Resource Type (*: required) |
Condition Key |
Alias |
|---|---|---|---|---|---|
|
smn:topic:create |
Permissions to create a topic |
Write |
topic * |
- |
- |
|
- |
|||||
|
smn:topic:listTopic |
Permissions to query topics |
List |
topic * |
- |
smn:topic:list |
|
- |
|||||
|
smn:topic:updateTopic |
Permissions to update a topic |
Write |
topic * |
smn:topic:update |
|
|
smn:topic:get |
Permissions to query details of a topic |
Read |
topic * |
smn:topic:list |
|
|
smn:topic:delete |
Permissions to delete a topic |
Write |
topic * |
- |
|
|
smn:topic:listAttributes |
Permissions to query a topic policy |
List |
topic * |
smn:topic:list |
|
|
smn:topic:deleteAttribute |
Permissions to delete a topic policy |
Write |
topic * |
smn:topic:update |
|
|
smn:topic:updateAttribute |
Permissions to update a topic policy |
Write |
topic * |
smn:topic:update |
|
|
- |
|||||
|
smn:topic:subscribe |
Permissions to add a subscription to a topic |
Write |
topic * |
smn:topic:update |
|
|
- |
|||||
|
smn:topic:listSubscriptionsByTopic |
Permissions to query subscriptions of a topic |
List |
topic * |
smn:topic:list |
|
|
smn:topic:listSubscriptions |
Permissions to query subscriptions of all topics |
List |
topic * |
- |
smn:topic:list |
|
smn:topic:deleteSubscription |
Permissions to delete a subscription from a topic |
Write |
topic * |
smn:topic:update |
|
|
smn:topic:updateSubscription |
Permissions to update a subscription of a topic |
Write |
topic * |
smn:topic:update |
|
|
smn:topic:publish |
Permissions to publish a message |
Write |
topic * |
- |
|
|
smn:template:create |
Permissions to create a message template |
Write |
template * |
- |
- |
|
smn:template:listTemplates |
Permissions to query message templates |
List |
template * |
- |
smn:template:list |
|
smn:template:update |
Permissions to modify a message template |
Write |
template * |
- |
- |
|
smn:template:get |
Permissions to query details of a message template |
Read |
template * |
- |
smn:template:list |
|
smn:template:delete |
Permissions to delete a message template |
Write |
template * |
- |
- |
|
smn:tag:create |
Permissions to add a tag to a topic |
Write |
topic * |
- |
|
|
- |
|||||
|
smn:tag:delete |
Permissions to delete a tag of a topic |
Write |
topic * |
smn:tag:update |
|
|
- |
|||||
|
smn:tag:batchModify |
Permissions to batch modify tags of a topic |
Write |
topic * |
smn:tag:update |
|
|
- |
|||||
|
smn:tag:list |
Permissions to query tags of a topic |
Read |
topic * |
- |
|
|
smn:topic:createLogTank |
Permissions to associate a topic with a log stream |
Write |
topic * |
- |
|
|
smn:topic:listLogTank |
Permissions to query the log stream associated with a topic |
List |
topic * |
smn:topic:list |
|
|
smn:topic:updateLogTank |
Permissions to update the log stream associated with a topic |
Write |
topic * |
smn:topic:update |
|
|
smn:topic:deleteLogTank |
Permissions to disassociate a topic from a log stream |
Write |
topic * |
smn:topic:update |
|
|
smn:topic:createNotifyPolicy |
Permissions to create a notification policy |
Write |
topic * |
- |
- |
|
smn:topic:updateNotifyPolicy |
Permissions to modify a notification policy |
Write |
topic * |
- |
- |
|
smn:topic:getNotifyPolicy |
Permissions to query a notification policy |
Read |
topic * |
- |
- |
|
smn:topic:deleteNotifyPolicy |
Permissions to delete a notification policy |
Write |
topic * |
- |
- |
Each API of SMN usually supports one or more actions. Table 2 lists the supported actions and dependencies.
|
API |
Action |
Dependency |
|---|---|---|
|
POST /v2/{project_id}/notifications/topics |
smn:topic:create |
N/A |
|
GET /v2/{project_id}/notifications/topics |
smn:topic:listTopic |
N/A |
|
PUT /v2/{project_id}/notifications/topics/{topic_urn} |
smn:topic:updateTopic |
N/A |
|
GET /v2/{project_id}/notifications/topics/{topic_urn} |
smn:topic:get |
N/A |
|
DELETE /v2/{project_id}/notifications/topics/{topic_urn} |
smn:topic:delete |
N/A |
|
GET /v2/{project_id}/notifications/topics/{topic_urn}/attributes |
smn:topic:listAttributes |
N/A |
|
DELETE /v2/{project_id}/notifications/topics/{topic_urn}/attributes |
smn:topic:deleteAttribute |
N/A |
|
PUT /v2/{project_id}/notifications/topics/{topic_urn}/attributes/{name} |
smn:topic:updateAttribute |
N/A |
|
DELETE /v2/{project_id}/notifications/topics/{topic_urn}/attributes/{name} |
smn:topic:deleteAttribute |
N/A |
|
POST /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions |
smn:topic:subscribe |
N/A |
|
GET /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions |
smn:topic:listSubscriptionsByTopic |
N/A |
|
PUT /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions/{subscription_urn} |
smn:topic:updateSubscription |
N/A |
|
DELETE /v2/{project_id}/notifications/subscriptions/{subscription_urn} |
smn:topic:deleteSubscription |
N/A |
|
GET /v2/{project_id}/notifications/subscriptions |
smn:topic:listSubscriptions |
N/A |
|
POST /v2/{project_id}/notifications/topics/{topic_urn}/publish |
smn:topic:publish |
N/A |
|
POST /v2/{project_id}/notifications/message_template |
smn:template:create |
N/A |
|
GET /v2/{project_id}/notifications/message_template |
smn:template:listTemplates |
N/A |
|
PUT /v2/{project_id}/notifications/message_template/{message_template_id} |
smn:template:update |
N/A |
|
GET /v2/{project_id}/notifications/message_template/{message_template_id} |
smn:template:get |
N/A |
|
DELETE /v2/{project_id}/notifications/message_template/{message_template_id} |
smn:template:delete |
N/A |
|
POST /v2/{project_id}/{resource_type}/{resource_id}/tags |
smn:tag:create |
N/A |
|
GET /v2/{project_id}/{resource_type}/{resource_id}/tags |
smn:tag:list |
N/A |
|
POST /v2/{project_id}/{resource_type}/{resource_id}/tags/action |
smn:tag:batchModify |
|
|
DELETE /v2/{project_id}/{resource_type}/{resource_id}/tags/{key} |
smn:tag:delete |
N/A |
|
GET /v2/{project_id}/{resource_type}/tags |
smn:tag:list |
N/A |
|
POST /v2/{project_id}/{resource_type}/resource_instances/action |
smn:tag:list |
N/A |
|
GET /v2/{project_id}/notifications/topics/{topic_urn}/logtanks |
smn:topic:listLogTank |
N/A |
|
POST /v2/{project_id}/notifications/topics/{topic_urn}/logtanks |
smn:topic:createLogTank |
N/A |
|
PUT /v2/{project_id}/notifications/topics/{topic_urn}/logtanks/{logtank_id} |
smn:topic:updateLogTank |
N/A |
|
DELETE /v2/{project_id}/notifications/topics/{topic_urn}/logtanks/{logtank_id} |
smn:topic:deleteLogTank |
N/A |
|
POST /v2/{project_id}/notifications/subscriptions/filter_polices |
smn:topic:updateSubscription |
N/A |
|
PUT /v2/{project_id}/notifications/subscriptions/filter_polices |
smn:topic:updateSubscription |
N/A |
|
DELETE /v2/{project_id}/notifications/subscriptions/filter_polices |
smn:topic:updateSubscription |
N/A |
|
POST /v2/{project_id}/notifications/topics/{topic_urn}/subscriptions/from-subscription-users |
smn:topic:subscribe |
N/A |
|
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 |
N/A |
|
DELETE /v2/{project_id}/notifications/topics/{topic_urn}/notify-policy/{notify_policy_id} |
smn:topic:deleteNotifyPolicy |
N/A |
|
GET /v2/{project_id}/notifications/topics/{topic_urn}/statistics |
smn:topic:get |
N/A |
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, a resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to the resource. 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 SMN.
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 SMN 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 Condition operators.
Service-specific condition keys supported by SMN
The following table lists the condition keys that you can define in custom identity policies for SMN. You can include these condition keys to specify conditions for when your identity policy is in effect.
|
Service-specific Condition Key |
Type |
Single-valued/Multivalued |
Description |
|---|---|---|---|
|
smn:TargetOrgPath |
string |
Single-valued |
The organization path authorized in a topic policy. |
|
smn:TargetOrgId |
string |
Single-valued |
The organization ID authorized in a topic policy. |
|
smn:TargetAccountId |
string |
Single-valued |
The account ID authorized in a topic policy. |
|
smn:Protocol |
string |
Single-valued |
The subscription protocol. |
|
smn:Endpoint |
string |
Single-valued |
The subscription endpoint address |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot