Message
diff --git a/docs/smn/umn/en-us_topic_0044170758.html b/docs/smn/umn/en-us_topic_0044170758.html
index 26081b518..573eebba7 100644
--- a/docs/smn/umn/en-us_topic_0044170758.html
+++ b/docs/smn/umn/en-us_topic_0044170758.html
@@ -5,7 +5,7 @@
After you publish a message to a topic, SMN will deliver the message to all confirmed subscription endpoints in the topic.
For SMS endpoints, if an SMS message is oversized, the system divides it into multiple parts when sending it to subscribers. However, you must note that SMN only sends the first two parts of the SMS message and does not send any additional parts. You are charged based on the actual number of messages sent to the subscribers.
-You must ensure that firewall policies of the HTTP or HTTPS endpoints allow SMN to send messages over the Internet. An SMN HTTP or HTTPS message consists of a message header and body. For details, see HTTP or HTTPS Message Format..
+You must ensure that firewall policies of the HTTP or HTTPS endpoints allow SMN to send messages over the Internet. An SMN HTTP or HTTPS message consists of a message header and body. For details, see HTTP or HTTPS Message Format.
If FunctionGraph (function) is used to receive messages, the message contains message attributes, subject, content, and topic URN. For details, see Messages Using Different Protocols.
diff --git a/docs/smn/umn/en-us_topic_0044170767.html b/docs/smn/umn/en-us_topic_0044170767.html
index 9c0e54f3b..6af7aad30 100644
--- a/docs/smn/umn/en-us_topic_0044170767.html
+++ b/docs/smn/umn/en-us_topic_0044170767.html
@@ -5,8 +5,8 @@
PrerequisitesSubscribers in the topic must have confirmed the subscription, or they will not be able to receive any messages.
Procedure- Log in to the management console.
- In the upper left corner of the page, click
 and select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
+Procedure- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
- In the topic list, locate the topic that you need to publish a message to and click Publish Message in the Operation column.
Alternatively, locate the topic and click its name. In the upper right corner of the displayed topic details page, click Publish Message.
- Configure parameters by referring to Table 1.
Table 1 Parameters required for publishing a messageParameter
diff --git a/docs/smn/umn/en-us_topic_0044170770.html b/docs/smn/umn/en-us_topic_0044170770.html
index 404a099ee..e6dc07220 100644
--- a/docs/smn/umn/en-us_topic_0044170770.html
+++ b/docs/smn/umn/en-us_topic_0044170770.html
@@ -3,26 +3,26 @@
Publishing a Template Message
ScenariosMessage templates contain fixed message content. If you need to send the same or similar messages multiple times, you can create a message template for quick message sending.
You can create different templates for different protocols using the same template name so that each type of subscribers can receive customized messages. Templates contain variables as the placeholders to represent changeable content that you can replace with your own message content. Note that you must create a template whose Protocol is Default, or the system will prevent you from publishing messages using this template name.
- When you are creating messages using a template, select a template name. The system will list all variables in the following protocol sequence: Default, SMS, Email, FunctionGraph (function), HTTP, and HTTPS. The same variables are listed only once even if they are used in multiple protocols, and the protocols they support are listed after each variable. Specify content for each variable in the message template, and SMN replaces them with the content you entered. If you do not enter any content for a variable, the system will treat it as empty when sending messages. SMN tries to match different types of subscribers to the template protocols. If there is no template for a specified protocol, SMN will use the default template to send messages to subscribers of that protocol.
+ When you are creating messages using a template, select a template name. The system will list all variables in the following protocol sequence: Default, SMS, , Email, FunctionGraph (function), HTTP, HTTPS. The same variables are listed only once even if they are used in multiple protocols, and the protocols they support are listed after each variable. Specify content for each variable in the message template, and SMN replaces them with the content you entered. If you do not enter any content for a variable, the system will treat it as empty when sending messages. SMN tries to match different types of subscribers to the template protocols. If there is no template for a specified protocol, SMN will use the default template to send messages to subscribers of that protocol.
This section describes how to publish messages using a template. For more details about message templates, see Message Template Management.
PrerequisitesSubscribers in the topic must have confirmed the subscription, or they will not be able to receive any messages.
- Creating a Message Template- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane on the left, choose Message Templates.
The Topics page is displayed.
- - In the upper right corner, click Create Message Template. For details, see Creating a Message Template in Message Template Management.
For example, the template information is as follows: - Template Name: tem_001
- Protocol: Default
- Content: The Arts and Crafts Exposition will be held from {startdate} through {enddate}. We sincerely invite you to join us.
+ Creating a Message Template- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane on the left, choose Message Templates.
The Message Templates tab page is displayed.
+ - In the upper right corner, click Create Message Template. For details, see Creating a Message Template in Message Template Management.
For example, the template information is as follows: - Template Name: tem_001
- Protocol: Default
- Content: The Arts and Crafts Exposition will be held from {startdate} through {enddate}. We sincerely invite you to join us.
- Click OK.
Figure 1 Create Message Template
- Publishing a Template Message- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Under Application, select Simple Message Notification.
The SMN console is displayed.
+Publishing a Template Message- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Under Application, select Simple Message Notification.
The SMN console is displayed.
- In the navigation pane, choose Topics.
The Topics page is displayed.
- In the topic list, locate the topic that you need to publish a message to and click Publish Message in the Operation column.
Alternatively, locate the topic and click its name. In the upper right corner of the displayed topic details page, click Publish Message.
- Configure the required parameters. (The topic name is provided by default and cannot be changed. Subject is optional.)
Select Template for Message Format. Then, manually type the template content in the Message box or click Generate Template Message to generate it automatically. The message content cannot be left blank and its size cannot exceed 256 KB.
- If you choose to manually type the template message, see Template Message Format for detailed requirements.
- If you choose to automatically generate the template message, proceed with 7 through 10.
- Click Generate Template Message.
- Select a template name, for example, tem_001. Enter values for the variables.
The system replaces the variables with the message content you specified. The protocols configured in the template are displayed after each variable. Only the Default protocol is specified in tem_001, as shown in Figure 2. Therefore, all confirmed subscribers in the topic will receive the message content in the default template. Figure 2 Generate Template Message
- Click the Preview tab and click Message Preview to preview the message.
In this example, the message generated is The Arts and Crafts Exposition will be held from February 10 through February 21. We sincerely invite you to join us.. Figure 3 Previewing the template message
+ - Click the Preview tab and click Message Preview to preview the message.
In this example, the message generated is The Arts and Crafts Exposition will be held from February 10 through February 21. We sincerely invite you to join us.. Figure 3 Previewing the template message
- Click OK.
The message that is generated contains the template name and variables. Figure 4 Template message example
- What Are the Requirements for an SMN Topic Name?
- - What Are Most Frequently Asked Questions About Creating, Subscribing to, and Publishing a Topic in SMN?
+ - What Are Most Frequently Asked Questions About Creating, Publishing, and Subscribing to a Topic in SMN?
- Does SMN Ensure That Messages Are Received by Subscription Endpoints?
diff --git a/docs/smn/umn/smn_faq_0006.html b/docs/smn/umn/smn_faq_0006.html
index de70ff265..4dc1fa435 100644
--- a/docs/smn/umn/smn_faq_0006.html
+++ b/docs/smn/umn/smn_faq_0006.html
@@ -1,6 +1,6 @@
- What Are Most Frequently Asked Questions About Creating, Subscribing to, and Publishing a Topic in SMN?
+ What Are Most Frequently Asked Questions About Creating, Publishing, and Subscribing to a Topic in SMN?
How Many Topics Can I Create?By default, you can create 3,000 topics.
How Many Subscriptions Can Be Added to a Topic?By default, 10,000 subscriptions can be added to a topic.
diff --git a/docs/smn/umn/smn_faq_0021.html b/docs/smn/umn/smn_faq_0021.html
index 89b7c1509..9f3025021 100644
--- a/docs/smn/umn/smn_faq_0021.html
+++ b/docs/smn/umn/smn_faq_0021.html
@@ -2,7 +2,8 @@
How Do I Obtain My Account ID?
- - Log in to the management console.
- Point to the username on the upper right and click My Credentials.
- Obtain the user's account ID.
+ - Log in to the management console.
- Point to the username on the upper right and click My Credentials.
- Obtain the user's account ID.
+
diff --git a/docs/smn/umn/smn_pd_20000.html b/docs/smn/umn/smn_pd_20000.html
index bfb0bb4c0..12f471cc3 100644
--- a/docs/smn/umn/smn_pd_20000.html
+++ b/docs/smn/umn/smn_pd_20000.html
@@ -12,7 +12,7 @@
- Accessing and Using SMN
- - Permissions
+ - Permissions
- SMN and Other Services
diff --git a/docs/smn/umn/smn_pd_22000.html b/docs/smn/umn/smn_pd_22000.html
index 6f8ec7774..24ce068d1 100644
--- a/docs/smn/umn/smn_pd_22000.html
+++ b/docs/smn/umn/smn_pd_22000.html
@@ -2,7 +2,6 @@
Application Scenarios
- System notifications
After events or alarms are triggered, SMN can send notifications to specified users by email, SMS message, FunctionGraph (function), or HTTP/HTTPS message. For example, Cloud Trace Service (CTS) detects key cloud service operations and uses SMN to notify you and other users.
- - Integrating with cloud services
SMN can function as a message middleware to directly connect cloud services, improving service efficiency. For example, Cloud Eye does not have to be integrated with Object Storage Service (OBS) to interact with each other. Instead, they can be connected by SMN, so faults in one service will not affect the other.
- Off-peak traffic control
If there is a discrepancy between processing capabilities of the upstream and downstream systems, SMN can cache data to reduce downstream pressure to reduce breakdowns, enhance availability, and mitigate complexity in the system.
diff --git a/docs/smn/umn/smn_pd_23000.html b/docs/smn/umn/smn_pd_23000.html
index 49bbc7d32..46cb7194d 100644
--- a/docs/smn/umn/smn_pd_23000.html
+++ b/docs/smn/umn/smn_pd_23000.html
@@ -1,7 +1,7 @@
Service Advantages
- SMN has the following advantages over any traditional messaging systems.
+ SMN has the following advantages over other traditional messaging systems.
Table 1 SMN advantagesItem
|
@@ -13,14 +13,14 @@
|---|
Simplicity
|
-SMN provides three basic APIs to create topics, add subscriptions, and publish messages. SMN can be quickly integrated with your services. It enables you to send messages in substantial quantity and do not require highly skilled development.
+ | SMN provides three basic APIs to create topics, add subscriptions, and publish messages. SMN can be quickly integrated with your services. It enables you to send messages in substantial quantity and does not require highly skilled development.
|
-A self-developed messaging system is expensive and takes long time to be integrated with your services. Its APIs are complex and hard to use.
+ | A self-developed messaging system is expensive and takes a long time to integrate with your services. Its APIs are complex and hard to use.
|
Stability and reliability
|
-SMN stores messages in multiple data centers and supports transparent topic migration. Once a message fails to deliver, SMN saves it in a message queue and tries to deliver it again. If one service node is faulty, your requests are automatically processed by another available node.
+ | SMN is deployed across multiple data centers to ensure redundancy and high availability. If one service node is faulty, your requests are automatically processed by another available node.
|
A traditional messaging system cannot achieve the stability and reliability required by critical services and does not provide measures to ensure service continuity.
|
diff --git a/docs/smn/umn/smn_pd_24000.html b/docs/smn/umn/smn_pd_24000.html
index 322c0f162..82a4c151c 100644
--- a/docs/smn/umn/smn_pd_24000.html
+++ b/docs/smn/umn/smn_pd_24000.html
@@ -4,9 +4,9 @@
SMN can be interconnected with other cloud services to provide them with messaging capabilities so that these services can send notifications to tenants or their message processing systems. For details about how to use SMN in other cloud services, see user guides of the related services.
The following are examples of some services using SMN.
- Cloud Eye
After an alarm rule is configured, Cloud Eye can use SMN to send alarm notifications to specific users.
- - Anti-DDoS
Anti-DDoS uses SMN to notify users by email or SMS message once a DDoS attack occurs.
- - CTS
CTS can be integrated with SMN to notify users of key events. SMN also uses CTS to record service resource operations.
- - OBS
OBS uses SMN to send OBS bucket events to applications for processing.
+ - Anti-DDoS
Anti-DDoS uses SMN to notify users by email or SMS message once a DDoS attack occurs.
+ - Cloud Trace Service (CTS)
CTS can be integrated with SMN to notify users of key events. SMN also uses CTS to record service resource operations.
+ - Object Storage Service (OBS)
OBS uses SMN to send OBS bucket events to applications for processing.
diff --git a/docs/smn/umn/smn_qs_30010.html b/docs/smn/umn/smn_qs_30010.html
index 0a34051ba..15b287eab 100644
--- a/docs/smn/umn/smn_qs_30010.html
+++ b/docs/smn/umn/smn_qs_30010.html
@@ -6,8 +6,8 @@
ScenariosTo send similar messages repeatedly, create a message template which contains fixed and changeable content. Every time you send messages using the template, you only have to replace changeable content. For example, your organization holds expositions regularly and needs to notify relevant people of the time, you can create a message template containing date variables and other fixed content.
Step 1. Create a Topic- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
+Step 1. Create a Topic- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
- In the upper right corner, click Create Topic.
Figure 2 Create Topic
- Enter a topic name and display name.
Table 1 Parameter descriptionsParameter
@@ -24,8 +24,8 @@
|
|---|
Display Name
|
-Message sender name, which can contain up to 192 bytes
- NOTE: After you specify a display name, the sender in email messages will be presented as Display name<noreply@otc.t-systems.com>. Otherwise, the sender will be noreply@otc.t-systems.com.
+ Message sender name, which can contain up to 192 characters
+ NOTE: After you specify a display name, the sender in email messages will be presented as Display name<noreply@otc.t-systems.com>. Otherwise, the sender will be noreply@otc.t-systems.com.
|
|
@@ -42,7 +42,7 @@
To search for a topic, filter topics by project or enter the topic name in the upper right corner of the topic list. Then click  or press Enter. Alternatively, click Search by Tag above the upper right corner of the topic list and search for a topic by tag key and value.
- Click the name of the topic to view its details, including the topic URN, display name, tags, and subscriptions.
-Step 2. Add a Subscription- Log in to the management console.
- In the upper left corner of the page, click
 and select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
+Step 2. Add a Subscription- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- In the navigation pane on the left, choose Subscriptions.
- In the upper right corner, click Add Subscription.
The Add Subscription dialog box is displayed.
Figure 3 Add Subscription
- Specify the required subscription information.
- Beside Topic Name, click Select Topic.
- Specify the subscription protocol and endpoints.
@@ -59,7 +59,7 @@
Protocol
|
-Specifies the protocol over which messages are sent. Possible values are SMS, HTTP, HTTPS, FunctionGraph (function), and Email.
+ | Specifies the protocol over which messages are sent. Possible values are SMS, FunctionGraph (function), Email, HTTP, and HTTPS.
|
Endpoint
@@ -85,7 +85,7 @@
|
This parameter is only available if HTTP or HTTPS is selected for Protocol. It indicates whether to configure the request header now. If you select Configure now, specify Key and Value. You can add up to 10 request headers.
The value of Key must:
-- be case insensitive and unique.
- start with x- but cannot start with x-smn.
- contain only digits, letters, and hyphens (-), but not end with a hyphen nor contain consecutive hyphens.
+- Be case insensitive and unique.
- Start with x- but cannot start with x-smn.
- Contain only digits, letters, and hyphens (-), but not end with a hyphen nor contain consecutive hyphens.
|
Version
@@ -95,7 +95,7 @@
|
Description
|
-Specifies the remarks of the subscription.
+ | Enter the remarks for the subscription. The remarks can contain a maximum of 128 characters.
|
@@ -108,7 +108,7 @@
Step 3. Create a Message Template- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
+Step 3. Create a Message Template- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- In the navigation pane on the left, choose Message Templates.
- In the upper right corner, click Create Message Template.
The Create Message Template dialog box is displayed.
Figure 4 Create Message Template
- Specify the template name, protocol, and content.
@@ -149,14 +149,14 @@
To search for a template, enter the template name in the upper right corner of the message template list and click  or press Enter.
Step 4. Publish a Template Message- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Under Application, select Simple Message Notification.
The SMN console is displayed.
+Step 4. Publish a Template Message- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Under Application, select Simple Message Notification.
The SMN console is displayed.
- In the navigation pane, choose Topics.
The Topics page is displayed.
- In the topic list, locate the topic that you need to publish a message to and click Publish Message in the Operation column.
Alternatively, locate the topic and click its name. In the upper right corner of the displayed topic details page, click Publish Message.
- Configure the required parameters. (The topic name is provided by default and cannot be changed. Subject is optional.)
Select Template for Message Format. Then, manually type the template content in the Message box or click Generate Template Message to generate it automatically. The message content cannot be left blank and its size cannot exceed 256 KB.
- If you choose to manually type the template message, see Template Message Format for detailed requirements.
- If you choose to automatically generate the template message, proceed with 7 through 10.
- Click Generate Template Message.
- Select a template name, for example, tem_001. Enter values for the variables.
The system replaces the variables with the message content you specified. The protocols configured in the template are displayed after each variable. Only the Default protocol is specified in tem_001, as shown in Figure 5. Therefore, all confirmed subscribers in the topic will receive the message content in the default template. Figure 5 Generate Template Message
- Click the Preview tab and click Message Preview to preview the message.
In this example, the message generated is The Arts and Crafts Exposition will be held from February 10 through February 21. We sincerely invite you to join us.. Figure 6 Previewing the template message
+ - Click the Preview tab and click Message Preview to preview the message.
In this example, the message generated is The Arts and Crafts Exposition will be held from February 10 through February 21. We sincerely invite you to join us.. Figure 6 Previewing the template message
- Click OK.
The message that is generated contains the template name and variables. Figure 7 Template message example
ScenariosTags consist of keys and values. They identify cloud resources so that you can easily categorize and search for your resources. - A tag key can have multiple values.
- Tag keys for the same resource must be unique.
- Adding Tags to a Topic- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
+Adding Tags to a Topic- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
- Click the topic name.
The Topic Details page is displayed.
- Click the Tags tab.
- Click Add Tag and specify tag keys and values.
Figure 1 Add Tag
 - A key can contain up to 36 characters. A value can contain up to 43 characters. Both Key and Value can contain only digits, letters, hyphens (-), at signs (@), and underscores (_).
- You can add up to 20 tags for each topic.
@@ -13,16 +13,16 @@
- Click OK.
The tags you added are displayed in the list.
- Modifying a Topic Tag- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
+Modifying a Topic Tag- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
- Click the topic name.
The Topic Details page is displayed.
- Click the Tags tab.
- Click Edit under Operation to modify the tag value.
Figure 2 Edit Tag
- Click OK.
Deleting a Topic Tag- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
+Deleting a Topic Tag- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
- Click the topic name.
The Topic Details page is displayed.
- - Click the Tags tab.
- Click Delete in the Operation column and click OK in the confirmation dialog box.
Figure 3 Delete Tag
+ - Click the Tags tab.
- Click Delete in the Operation column and click OK in the confirmation dialog box.
Figure 3 Delete Tag
ScenariosTo enable an endpoint to receive messages published to a topic, you must subscribe the endpoint to the topic. The endpoint can be a phone number, email address, function, or an HTTP/HTTPS URL. After you subscribe an endpoint to a topic and the subscription is confirmed, the endpoint can receive messages published to the topic.
You can add multiple subscriptions to a topic. This section describes how to add a subscription to a topic you created or a topic that you have permissions for.
- Adding a Subscription- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Simple Message Notification under Application.
The SMN console is displayed.
+Adding a Subscription- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- In the navigation pane on the left, choose Subscriptions.
- In the upper right corner, click Add Subscription.
The Add Subscription dialog box is displayed.
Figure 1 Add Subscription
- Specify the required subscription information.
- Beside Topic Name, click Select Topic.
- Specify the subscription protocol and endpoints.
@@ -21,7 +21,7 @@
Protocol
|
-Specifies the protocol over which messages are sent. Possible values are SMS, HTTP, HTTPS, FunctionGraph (function), and Email.
+ | Specifies the protocol over which messages are sent. Possible values are SMS, FunctionGraph (function), Email, HTTP, and HTTPS.
|
Endpoint
@@ -47,7 +47,7 @@
|
This parameter is only available if HTTP or HTTPS is selected for Protocol. It indicates whether to configure the request header now. If you select Configure now, specify Key and Value. You can add up to 10 request headers.
The value of Key must:
-- be case insensitive and unique.
- start with x- but cannot start with x-smn.
- contain only digits, letters, and hyphens (-), but not end with a hyphen nor contain consecutive hyphens.
+- Be case insensitive and unique.
- Start with x- but cannot start with x-smn.
- Contain only digits, letters, and hyphens (-), but not end with a hyphen nor contain consecutive hyphens.
|
Version
@@ -57,7 +57,7 @@
|
Description
|
-Specifies the remarks of the subscription.
+ | Enter the remarks for the subscription. The remarks can contain a maximum of 128 characters.
|
diff --git a/docs/smn/umn/smn_ug_0009.html b/docs/smn/umn/smn_ug_0009.html
index 79a8eceab..ecb4949ab 100644
--- a/docs/smn/umn/smn_ug_0009.html
+++ b/docs/smn/umn/smn_ug_0009.html
@@ -3,7 +3,7 @@
Requesting Subscription Confirmation
ScenariosIf a subscriber does not receive the confirmation message, request confirmation again. You can send a subscription confirmation message to one or more subscription endpoints at a time. For details, see Traffic Control over Subscription Confirmation.
- Requesting Subscription Confirmation- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
+Requesting Subscription Confirmation- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- In the navigation pane on the left, choose Subscriptions.
- In the subscription list, select one or more subscriptions whose status is Unconfirmed.
- Click Request Confirmation above the subscription list and SMN will send confirmation requests.
Alternatively, click Request Confirmation in the Operation column, and SMN will send the confirmation request.
- The subscribers confirm their subscriptions.
- To prevent malicious users from attacking subscription endpoints, SMN limits the number of confirmation messages that can be sent to an endpoint within a specified period. For details, see Traffic Control over Subscription Confirmation.
- SMN does not check whether subscription endpoints exist when you add subscriptions. However, subscribers will not receive notification messages until they confirm their subscriptions.
- After you add a subscription and request subscription confirmation, SMN sends a message that contains a link for confirming the subscription to the subscription endpoint. The subscription confirmation link is valid within 48 hours. Confirm the subscription on your mobile phone, mailbox, or other endpoints in time.
- Subscription confirmation messages will be counted as messages sent and will be billed.
diff --git a/docs/smn/umn/smn_ug_0011.html b/docs/smn/umn/smn_ug_0011.html
index 436a47709..3c74be7f1 100644
--- a/docs/smn/umn/smn_ug_0011.html
+++ b/docs/smn/umn/smn_ug_0011.html
@@ -3,15 +3,15 @@
Deleting a Subscription
ScenariosIf one or multiple subscription endpoints do not need to receive messages published to a topic, you can delete them.
- Deleting a Subscription on the Topic Details Page- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
+Deleting a Subscription on the Topic Details Page- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
- Click the topic name.
The Topic Details page is displayed.
- In the Subscriptions area, view the subscriptions to the topic.
- Select one or more subscriptions and click Delete at the top left of the list.
Alternatively, locate the subscription to be deleted and click Delete in the Operation column.
- - In the displayed Delete Subscription dialog box, click OK.
+ - In the displayed dialog box, click OK.
Deleting a Subscription on the Subscription Page- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
+Deleting a Subscription on the Subscription Page- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- In the navigation pane on the left, choose Subscriptions.
- In the subscription list, select one or more subscriptions and click Delete above the subscription list.
Alternatively, locate the subscription to be deleted and click Delete in the Operation column.
- - In the displayed Delete Subscription dialog box, click OK.
+ - In the displayed dialog box, click OK.
diff --git a/docs/smn/umn/smn_ug_0012.html b/docs/smn/umn/smn_ug_0012.html
deleted file mode 100644
index 6c0b59f9b..000000000
--- a/docs/smn/umn/smn_ug_0012.html
+++ /dev/null
@@ -1,102 +0,0 @@
-
-
- SMN Operations Audited by CTS
- After you enable CTS, whenever an SMN API is called, the operation may be recorded in a log file, which is then dumped to a specified OBS bucket for storage based on time and data changes.
- However, if someone calls the SMN API to cancel a subscription without login, CTS will not record the operation. For example, if a subscriber clicks the link in an email to cancel the subscription, the API for unsubscribing is called, but CTS does not record the operation.
- Table 1 lists the SMN operations that will be recorded by CTS.
-
- Table 1 SMN operations recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a topic
- |
-topic
- |
-createTopic
- |
-
-Deleting a topic
- |
-topic
- |
-deleteTopic
- |
-
-Updating a topic
- |
-topic
- |
-updateTopic
- |
-
-Updating a topic policy
- |
-topic
- |
-updateTopicAttribute
- |
-
-Adding a subscription
- |
-subscription
- |
-subscribe
- |
-
-Deleting a subscription
- |
-subscription
- |
-delsubscribe
- |
-
-Creating a message template
- |
-message_template
- |
-createMessageTemplate
- |
-
-Modifying a message template
- |
-message_template
- |
-updateMessageTemplate
- |
-
-Deleting a message template
- |
-message_template
- |
-deleteMessageTemplate
- |
-
-Batch adding tags
- |
-tag
- |
-batchCreateTag
- |
-
-Deleting a tag
- |
-tag
- |
-deleteTag
- |
-
-
-
-
-
-
-
diff --git a/docs/smn/umn/smn_ug_0013.html b/docs/smn/umn/smn_ug_0013.html
deleted file mode 100644
index 12df987dd..000000000
--- a/docs/smn/umn/smn_ug_0013.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
- Querying SMN Real-Time Traces
- ScenariosAfter you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.
-
- Viewing Real-Time Traces in the Trace List- Log in to the management console.
- Click
 in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed. - Choose Trace List in the navigation pane on the left.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
Figure 1 Filters
-- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- If you select Resource ID for Search By, specify a resource ID.
- If you select Trace name for Search By, specify a trace name.
- If you select Resource name for Search By, specify a resource name.
- - Operator: Select a user.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
- - Click Query.
- On the Trace List page, you can also export and refresh the trace list.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.
- Click
 to view the latest information about traces.
- - Click
 on the left of a trace to expand its details.
-
-
-
-
- - Click View Trace in the Operation column. The trace details are displayed.
- - For details about key fields in the trace structure, see Trace Structure and Example Traces in the CTS User Guide.
-
-
-
-
diff --git a/docs/smn/umn/smn_ug_0034.html b/docs/smn/umn/smn_ug_0034.html
deleted file mode 100644
index 32bf37bf8..000000000
--- a/docs/smn/umn/smn_ug_0034.html
+++ /dev/null
@@ -1,329 +0,0 @@
-
-
- Permissions
- You can use Identity and Access Management (IAM) to manage SMN permissions and control access to your resources. IAM provides identity authentication, permissions management, and access control.
- You can create IAM users for your employees and assign permissions to these users on a principle of least privilege (PoLP) basis to control their access to specific resource types. For example, you can create IAM users for software developers and assign specific permissions to allow them to use SMN resources but prevent them from being able to delete resources or perform any high-risk operations.
- If your account does not require individual IAM users for permissions management, skip this section.
- IAM can be used free of charge. You pay only for the resources in your account.
- For more information about IAM, see IAM Service Overview.
- SMN PermissionsBy default, new IAM users do not have any permissions assigned. To assign permissions to these new users, add them to one or more groups and attach permissions policies or roles to these groups.
- SMN is a project-level service deployed and accessed in specific physical regions. When assigning SMN permissions to a user group, specify region-specific projects where the permissions will take effect. If you select All projects, the permissions will be granted for all region-specific projects. When accessing SMN, the users need to switch to a region where they have been authorized to use this service.
- You can grant users permissions by using roles and policies.
- - Roles: a type of coarse-grained authorization mechanism that provides only a limited number of service-level roles When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: a type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions This mechanism allows for more flexible policy-based authorization for secure access control. For example, you can grant SMN users only the permissions for managing a certain type of SMN resources. Most policies define permissions based on APIs. For the API actions supported by SMN, see section "Permissions Policies and Supported Actions" in the Simple Message Notification API Reference.
- Table 1 lists all system-defined policies supported by SMN.
- Table 1 System-defined policies supported by SMNRole/Policy Name
- |
-Description
- |
-Type
- |
-Dependency
- |
-
|---|
-
-SMN Administrator
- |
-Has all permissions for SMN resources.
- |
-System-defined role
- |
-The Tenant Guest and SMN Administrator roles need to be assigned in the same project.
- |
-
-SMN FullAccess
- |
-Administrator permissions for SMN. Users granted these permissions can perform all operations on SMN resources.
- |
-System-defined policy
- |
-None
- |
-
-SMN ReadOnlyAccess
- |
-Read-only permissions for SMN.
-Users granted these permissions can only view SMN data.
- |
-System-defined policy
- |
-None
- |
-
-
-
-
-
- Table 2 lists the common operations supported by each SMN system policy or role. Select the policies or roles as needed.
-
- Table 2 Common operations supported by each system-defined policy or role of SMNOperation
- |
-Fine-Grained Action
- |
-SMN Administrator
- |
-SMN FullAccess
- |
-SMN ReadOnlyAccess
- |
-Dependency
- |
-
|---|
-
-Creating a topic
- |
-smn:topic:create
- |
-√
- |
-√
- |
-×
- |
-None
- |
-
-Updating a topic
- |
-smn:topic:update
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Deleting a topic
- |
-smn:topic:delete
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Querying topics
- |
-smn:topic:list
- |
-√
- |
-√
- |
-√
- |
-None
- |
-
-Adding a subscription to a topic
- |
-smn:topic:update
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Configuring topic policies
- |
-smn:topic:update
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Publishing a message
- |
-smn:topic:publish
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Adding a subscription
- |
-smn:topic:update
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Requesting subscription confirmation
- |
-smn:topic:update
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Deleting a subscription
- |
-smn:topic:update
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Querying subscriptions
- |
-smn:topic:list
- |
-√
- |
-√
- |
-√
- |
-None
- |
-
-Creating a message template
- |
-smn:template:create
- |
-√
- |
-√
- |
-×
- |
-None
- |
-
-Modifying a message template
- |
-smn:template:update
- |
-√
- |
-√
- |
-×
- |
-smn:template:list
- |
-
-Deleting a message template
- |
-smn:template:delete
- |
-√
- |
-√
- |
-×
- |
-smn:template:list
- |
-
-Querying a message template
- |
-smn:template:list
- |
-√
- |
-√
- |
-√
- |
-None
- |
-
-Adding a tag
- |
-smn:tag:create
- |
-√
- |
-√
- |
-×
- |
-smn:topic:list
- |
-
-Updating a tag
- |
-smn:tag:update
- |
-√
- |
-√
- |
-×
- |
-- smn:topic:list
- smn:tag:list
- |
-
-Deleting a tag
- |
-smn:tag:delete
- |
-√
- |
-√
- |
-×
- |
-- smn:topic:list
- smn:tag:list
- |
-
-Querying tags
- |
-smn:tag:list
- |
-√
- |
-√
- |
-√
- |
-smn:topic:list
- |
-
-
-
-
-
-
-
-
diff --git a/docs/smn/umn/smn_ug_0034_1.html b/docs/smn/umn/smn_ug_0034_1.html
new file mode 100644
index 000000000..b71ed8bba
--- /dev/null
+++ b/docs/smn/umn/smn_ug_0034_1.html
@@ -0,0 +1,329 @@
+
+
+ Permissions
+ You can use Identity and Access Management (IAM) to manage SMN permissions and control access to your resources. IAM provides identity authentication, permissions management, and access control.
+ You can create IAM users for your employees and assign permissions to these users on a principle of least privilege (PoLP) basis to control their access to specific resource types. For example, you can create IAM users for software developers and assign specific permissions to allow them to use SMN resources but prevent them from being able to delete resources or perform any high-risk operations.
+ If your account does not require individual IAM users for permissions management, skip this section.
+ IAM can be used free of charge. You pay only for the resources in your account.
+ For more information about IAM, see IAM Service Overview.
+ SMN PermissionsBy default, new IAM users do not have any permissions assigned. To assign permissions to these new users, add them to one or more groups and attach permissions policies or roles to these groups.
+ SMN is a project-level service deployed and accessed in specific physical regions. When assigning SMN permissions to a user group, specify region-specific projects where the permissions will take effect. If you select All projects, the permissions will be granted for all region-specific projects. When accessing SMN, the users need to switch to a region where they have been authorized to use this service.
+ You can grant users permissions by using roles and policies.
+ - Roles: a type of coarse-grained authorization that provides only a limited number of service-level roles Services depend on each other. When granting permissions using roles, assign other dependent roles to users. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: a type of fine-grained authorization that defines permissions required to perform operations on specific cloud resources under certain conditions This authorization allows for more flexible policy-based authorization for secure access control. For example, you can grant SMN users only the permissions for managing a certain type of SMN resources. Most policies define permissions based on APIs. For the API actions supported by SMN, see section "Permissions Policies and Supported Actions" in the Simple Message Notification API Reference.
+ Table 1 lists all system-defined policies supported by SMN.
+ Table 1 System-defined policies supported by SMNRole/Policy Name
+ |
+Description
+ |
+Type
+ |
+Dependency
+ |
+
|---|
+
+SMN Administrator
+ |
+Has all permissions for SMN resources.
+ |
+System-defined role
+ |
+The Tenant Guest and SMN Administrator roles need to be assigned in the same project.
+ |
+
+SMN FullAccess
+ |
+Administrator permissions for SMN. Users granted these permissions can perform all operations on SMN resources.
+ |
+System-defined policy
+ |
+None
+ |
+
+SMN ReadOnlyAccess
+ |
+Read-only permissions for SMN.
+Users granted these permissions can only view SMN data.
+ |
+System-defined policy
+ |
+None
+ |
+
+
+
+
+
+ Table 2 lists the common operations supported by each SMN system policy or role. Select the policies or roles as needed.
+
+ Table 2 Common operations supported by each system-defined policy or role of SMNOperation
+ |
+Fine-Grained Action
+ |
+SMN Administrator
+ |
+SMN FullAccess
+ |
+SMN ReadOnlyAccess
+ |
+Dependency
+ |
+
|---|
+
+Creating a topic
+ |
+smn:topic:create
+ |
+√
+ |
+√
+ |
+×
+ |
+None
+ |
+
+Updating a topic
+ |
+smn:topic:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Deleting a topic
+ |
+smn:topic:delete
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Querying topics
+ |
+smn:topic:list
+ |
+√
+ |
+√
+ |
+√
+ |
+None
+ |
+
+Adding a subscription to a topic
+ |
+smn:topic:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Configuring topic policies
+ |
+smn:topic:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Publishing a message
+ |
+smn:topic:publish
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Adding a subscription
+ |
+smn:topic:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Requesting subscription confirmation
+ |
+smn:topic:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Deleting a subscription
+ |
+smn:topic:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Querying subscriptions
+ |
+smn:topic:list
+ |
+√
+ |
+√
+ |
+√
+ |
+None
+ |
+
+Creating a message template
+ |
+smn:template:create
+ |
+√
+ |
+√
+ |
+×
+ |
+None
+ |
+
+Modifying a message template
+ |
+smn:template:update
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:template:list
+ |
+
+Deleting a message template
+ |
+smn:template:delete
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:template:list
+ |
+
+Querying a message template
+ |
+smn:template:list
+ |
+√
+ |
+√
+ |
+√
+ |
+None
+ |
+
+Adding a tag
+ |
+smn:tag:create
+ |
+√
+ |
+√
+ |
+×
+ |
+smn:topic:list
+ |
+
+Updating a tag
+ |
+smn:tag:update
+ |
+√
+ |
+√
+ |
+×
+ |
+- smn:topic:list
- smn:tag:list
+ |
+
+Deleting a tag
+ |
+smn:tag:delete
+ |
+√
+ |
+√
+ |
+×
+ |
+- smn:topic:list
- smn:tag:list
+ |
+
+Querying tags
+ |
+smn:tag:list
+ |
+√
+ |
+√
+ |
+√
+ |
+smn:topic:list
+ |
+
+
+
+
+
+
+
+
diff --git a/docs/smn/umn/smn_ug_0035.html b/docs/smn/umn/smn_ug_0035.html
index 61129bc0c..e4b36f4b7 100644
--- a/docs/smn/umn/smn_ug_0035.html
+++ b/docs/smn/umn/smn_ug_0035.html
@@ -4,9 +4,9 @@
diff --git a/docs/smn/umn/smn_ug_0037.html b/docs/smn/umn/smn_ug_0037.html
deleted file mode 100644
index 538f34c75..000000000
--- a/docs/smn/umn/smn_ug_0037.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
- Creating a User and Granting SMN Permissions
- Use IAM to implement fine-grained permissions control over your SMN resources. With IAM, you can:
- - Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing SMN resources.
- Grant only the permissions required for users to perform a specific task.
- Entrust an account or cloud service to perform efficient O&M on your SMN resources.
- If your account does not require individual IAM users, skip this chapter.
- This section describes the procedure for granting permissions (see Figure 1).
- PrerequisitesLearn about the system permissions (see Permissions) supported by SMN and choose policies or roles according to your requirements. For system permissions of other cloud services, see Permissions.
-
- Process FlowThe following describes how to grant the SMN ReadOnlyAccess permissions.
- Figure 1 Process for granting the SMN ReadOnlyAccess permissions
- - Create a user group and assign permissions
Create a user group on the IAM console and assign the SMN ReadOnlyAccess permissions to the group.
- - Create a user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
- - Log in as the created user and verify the SMN ReadOnlyAccess permissions.
Log in to the SMN console by using the created user and verify that the user only has the SMN ReadOnlyAccess permissions.
-- Choose Service List > Simple Message Notification. On the SMN Topics page, click Create Topic in the upper right corner. If the topic cannot be created, the SMN ReadOnlyAccess policy has already taken effect.
- Choose any other service on the Service List page. If a message appears indicating that you have insufficient permissions to access the service, the SMN ReadOnlyAccess policy has already taken effect.
- Choose Service List > Simple Message Notification. On the Topics page, if you can view existing topics, the SMN ReadOnlyAccess policy has already taken effect.
-
-
-
-
-
diff --git a/docs/smn/umn/smn_ug_0037_1.html b/docs/smn/umn/smn_ug_0037_1.html
new file mode 100644
index 000000000..caf36bafb
--- /dev/null
+++ b/docs/smn/umn/smn_ug_0037_1.html
@@ -0,0 +1,24 @@
+
+
+ Creating a User and Granting SMN Permissions
+ You can use Identity and Access Management (IAM) for fine-grained permissions control for your SMN resources. With IAM, you can:
+ - Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing SMN resources.
- Grant only the permissions required for users to perform a specific task.
- Entrust an account or cloud service to perform efficient O&M on your SMN resources.
+ If your account does not require individual IAM users, skip this chapter.
+ This section describes the procedure for granting permissions (see Figure 1).
+ PrerequisitesLearn about the system permissions (see Permissions) supported by SMN and choose policies or roles according to your requirements. To grant permissions for other services, learn about all permissions.
+
+ Process FlowThe following describes how to grant the SMN ReadOnlyAccess permissions.
+ Figure 1 Process for granting the SMN ReadOnlyAccess permissions
+ - On the IAM console, create a user group and assign permissions to it (SMN ReadOnlyAccess as an example).
Create a user group on the IAM console and assign the SMN ReadOnlyAccess permissions to the group.
+ - Create an IAM user and add it to the created user group.
Create a user on the IAM console and add the user to the group created in 1.
+ - Log in as the IAM user and verify permissions.
Log in to the SMN console by using the created user and verify that the user only has the SMN ReadOnlyAccess permissions.
+- Choose Service List > Simple Message Notification. On the SMN Topics page, click Create Topic in the upper right corner. If the topic cannot be created, the SMN ReadOnlyAccess policy has already taken effect.
- Choose any other service on the Service List page. If a message appears indicating that you have insufficient permissions to access the service, the SMN ReadOnlyAccess policy has already taken effect.
- Choose Service List > Simple Message Notification. On the Topics page, if you can view existing topics, the SMN ReadOnlyAccess policy has already taken effect.
+
+
+
+
+
diff --git a/docs/smn/umn/smn_ug_0038.html b/docs/smn/umn/smn_ug_0038.html
deleted file mode 100644
index 85f55ef9e..000000000
--- a/docs/smn/umn/smn_ug_0038.html
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
- Creating SMN Custom Policies
- You can create custom policies to supplement the system-defined policies of SMN. For the actions supported by custom policies, see section "Permissions Policies and Supported Actions" in Simple Message Notification API Reference.
- You can create custom policies in either of the following ways:
- - Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Create a JSON policy or edit an existing one.
- The following are examples of custom policies created for SMN. .
- Example SMN Custom Policies- Example 1: Grant permissions to create a topic.
{
- "Version": "1.1",
- "Statement": [
- {
- "Effect": "Allow",
- "Action": [
- "smn:topic:create"
- ]
- }
- ]
-}
- - Example 2: Grant permissions to deny topic deletion.
A policy with only "Deny" permissions must be used with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
-You can assign a system policy of SMN FullAccess and a custom policy of denying topic deletion to the user group which the user belongs to at the same time. Thus the user can perform all operations on SMN except deleting topics. The following is an example of a deny policy:
-{
- "Version": "1.1",
- "Statement": [
- {
- "Effect": "Deny",
- "Action": [
- "smn:topic:delete"
- ]
- }
- ]
-}
- - Example 3: Create a custom policy containing multiple actions.
A custom policy can contain multiple actions that belong to any global or project-level services. The following is a custom policy containing multiple actions:
-{
- "Version": "1.1",
- "Statement": [
- {
- "Effect": "Allow",
- "Action": [
- "smn:topic:create",
- "smn:tag:create"
- ]
- },
- {
- "Effect": "Allow",
- "Action": [
- "elb:certificates:create",
- "elb:whitelists:create",
- "elb:pools:create",
- "elb:members:create",
- "elb:healthmonitors:create",
- "elb:l7policies:create",
- "elb:listeners:create",
- "elb:loadbalancers:create"
- ]
- }
- ]
-}
-
-
-
-
-
diff --git a/docs/smn/umn/smn_ug_0038_1.html b/docs/smn/umn/smn_ug_0038_1.html
new file mode 100644
index 000000000..61c229a93
--- /dev/null
+++ b/docs/smn/umn/smn_ug_0038_1.html
@@ -0,0 +1,66 @@
+
+
+ Creating SMN Custom Policies
+ You can create custom policies to supplement the system-defined policies of SMN. For the actions supported by custom policies, see section "Permissions Policies and Supported Actions" in Simple Message Notification API Reference.
+ You can create custom policies in either of the following ways:
+ - Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Create a JSON policy or edit an existing one.
+ The following are examples of custom policies created for SMN. For details, see Creating a Custom Policy.
+ Example SMN Custom Policies- Example 1: Grant permissions to create a topic.
{
+ "Version": "1.1",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "smn:topic:create"
+ ]
+ }
+ ]
+}
+ - Example 2: Grant permissions to deny topic deletion.
A policy with only "Deny" permissions must be used with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
+You can assign a system policy of SMN FullAccess and a custom policy of denying topic deletion to the user group which the user belongs to at the same time. Thus the user can perform all operations on SMN except deleting topics. The following is an example of a deny policy:
+{
+ "Version": "1.1",
+ "Statement": [
+ {
+ "Effect": "Deny",
+ "Action": [
+ "smn:topic:delete"
+ ]
+ }
+ ]
+}
+ - Example 3: Create a custom policy containing multiple actions.
A custom policy can contain multiple actions that belong to any global or project-level services. The following is a custom policy containing multiple actions:
+{
+ "Version": "1.1",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "smn:topic:create",
+ "smn:tag:create"
+ ]
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "elb:certificates:create",
+ "elb:whitelists:create",
+ "elb:pools:create",
+ "elb:members:create",
+ "elb:healthmonitors:create",
+ "elb:l7policies:create",
+ "elb:listeners:create",
+ "elb:loadbalancers:create"
+ ]
+ }
+ ]
+}
+
+
+
+
+
diff --git a/docs/smn/umn/smn_ug_42000.html b/docs/smn/umn/smn_ug_42000.html
index 763645786..464fa59e2 100644
--- a/docs/smn/umn/smn_ug_42000.html
+++ b/docs/smn/umn/smn_ug_42000.html
@@ -3,9 +3,9 @@
Modifying the Display Name of a Topic
ScenariosYou have created a topic and want to modify its display name.
- Modifying the Display Name of a Topic- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Simple Message Notification under Application.
The SMN console is displayed.
- - In the navigation pane, choose Topics.
The Topics page is displayed.
- - Locate the topic, choose More > Modify Display Name in the Operation column. In the displayed Modify Display Name dialog box, enter a new display name.
Alternatively, locate the topic and click its name. In the Topic Details area, click  and enter a new display name.
+Modifying the Display Name of a Topic- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
+ - In the navigation pane, choose Topics.
The Topics page is displayed.
+ - Locate the topic, choose More > Modify Display Name in the Operation column. In the displayed Modify Display Name dialog box, enter a new display name.
Alternatively, locate the topic and click its name. In the Topic Details area, click and enter a new display name.
After you specify a display name, the sender in email messages will be presented as Display name<noreply@otc.t-systems.com>. Otherwise, the sender will be noreply@otc.t-systems.com.
- Click OK.
diff --git a/docs/smn/umn/smn_ug_47000.html b/docs/smn/umn/smn_ug_47000.html
index 841e83fcd..70abbdaa4 100644
--- a/docs/smn/umn/smn_ug_47000.html
+++ b/docs/smn/umn/smn_ug_47000.html
@@ -5,7 +5,7 @@
PrerequisitesYou have obtained the URN of the topic granted to you. For details about obtaining a topic URN, see Creating a Topic.
Procedure- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
+Procedure- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- On the Dashboard page, click Publish Message.
- Specify the topic URN, message subject, and message format and enter your message content.
Clicking  beside Topic URN only enables you to select a topic you created, instead of a topic that you are granted permissions to.
Figure 1 Publishing a message to a topic granted to you
diff --git a/docs/smn/umn/smn_ug_48000.html b/docs/smn/umn/smn_ug_48000.html
index 02cf6bfc1..850c39958 100644
--- a/docs/smn/umn/smn_ug_48000.html
+++ b/docs/smn/umn/smn_ug_48000.html
@@ -1,7 +1,7 @@
Deleting a Topic
-- Log in to the management console.
- Click
 on the upper left to select the desired region and project. - Select Simple Message Notification under Application.
The SMN console is displayed.
+- Log in to the management console.
- Click on the upper left to select the desired region and project.
- Select Application > Simple Message Notification.
The SMN console is displayed.
- In the navigation pane, choose Topics.
The Topics page is displayed.
- Locate a topic, click More in the Operation column, and select Delete.
- In the displayed Delete Topic dialog box, click OK.
Deleting a topic deletes all its subscriptions.
diff --git a/docs/smn/umn/smn_ug_90000.html b/docs/smn/umn/smn_ug_90000.html
deleted file mode 100644
index 7e7c3afca..000000000
--- a/docs/smn/umn/smn_ug_90000.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
- CTS Auditing
-
-
-
diff --git a/docs/smn/umn/smn_ug_90001.html b/docs/smn/umn/smn_ug_90001.html
new file mode 100644
index 000000000..dee344fe9
--- /dev/null
+++ b/docs/smn/umn/smn_ug_90001.html
@@ -0,0 +1,101 @@
+
+
+ Audit Using CTS
+ CTS records SMN-related operations, including request content, source IP addresses, request senders, and the time when a request was sent, for future query, audit, and backtracking.
+ PrerequisitesYou have enabled CTS.
+
+ SMN Operations Recorded by CTS
+ Table 1 SMN operations recorded by CTSOperation
+ |
+Resource Type
+ |
+Trace Name
+ |
+
|---|
+
+Creating a topic
+ |
+topic
+ |
+createTopic
+ |
+
+Deleting a topic
+ |
+topic
+ |
+deleteTopic
+ |
+
+Updating a topic
+ |
+topic
+ |
+updateTopic
+ |
+
+Updating a topic policy
+ |
+topic
+ |
+updateTopicAttribute
+ |
+
+Adding a subscription
+ |
+subscription
+ |
+subscribe
+ |
+
+Deleting a subscription
+ |
+subscription
+ |
+delsubscribe
+ |
+
+Creating a message template
+ |
+message_template
+ |
+createMessageTemplate
+ |
+
+Modifying a message template
+ |
+message_template
+ |
+updateMessageTemplate
+ |
+
+Deleting a message template
+ |
+message_template
+ |
+deleteMessageTemplate
+ |
+
+Adding resource tags in batches
+ |
+tag
+ |
+batchCreateTag
+ |
+
+Deleting a resource tag
+ |
+tag
+ |
+deleteTag
+ |
+
+
+
+
+
+
+
+
+
diff --git a/docs/smn/umn/smn_ug_a1000.html b/docs/smn/umn/smn_ug_a1000.html
index 5f3eddce3..dd155132c 100644
--- a/docs/smn/umn/smn_ug_a1000.html
+++ b/docs/smn/umn/smn_ug_a1000.html
@@ -1,7 +1,7 @@
JSON Message Format
- DescriptionThe JSON format allows you to specify different message content for different subscription protocols, including Default, SMS, HTTP, HTTPS, FunctionGraph (function), and Email. The message content you specify will be sent to subscription endpoints using applicable protocols.
+ DescriptionThe JSON format allows you to specify different message content for different subscription protocols, including Default, SMS, HTTP, HTTPS, FunctionGraph (function), and Email. The message content you specify will be sent to subscription endpoints using applicable protocols.
{
"default": "Dear Sir or Madam, this is a default message.",
"email": "Dear Sir or Madam, this is an email message.",
@@ -31,7 +31,7 @@
The total number of protocols is N, including the Default protocol and those you selected.
The size of the message is calculated as follows: - Three spaces in each of the N protocols: 3 x N = 3N bytes
- Four quotation marks in each of the N protocols: 4 x N = 4N bytes
- One colon in each of the N protocols: 1 x N = N bytes
- Message content "This is a default message." in each of the N protocols: 26 x N = 26N bytes
- Commas in (N – 1) protocols: 1 x (N – 1) = (N – 1) bytes
- Line breaks in (N + 1) protocols: 1 x (N + 1) = (N + 1) bytes
- Two braces: 2 bytes
- Protocol name Default: 7 bytes
Bytes of protocols you selected: - HTTP: 4 bytes
- HTTPS: 5 bytes
- Email: 5 bytes
- SMS: 3 bytes
- FunctionStage: 13 bytes
+ Bytes of protocols you selected: - HTTP: 4 bytes
- HTTPS: 5 bytes
- Email: 5 bytes
- SMS: 3 bytes
- FunctionStage: 13 bytes
Total size = 36N + 9 + Bytes of protocols you selected
For example, you selected the HTTP, HTTPS, and email protocols, and the message is as follows:
@@ -42,7 +42,7 @@
"https": "This is a default message."
}
The system adds a Default protocol, and the value of N is 4. The size of this JSON message is:
- - Fixed length: 36 x 4 + 9 = 153 bytes
- http: 4 bytes
- https: 5 bytes
- email: 5 bytes
+ - Fixed length: 36 x 4 + 9 = 153 bytes
- http: 4 bytes
- https: 5 bytes
- email: 5 bytes
The total size is 167 bytes (153 + 4 + 5 + 5 = 167).
diff --git a/docs/smn/umn/smn_ug_a9002.html b/docs/smn/umn/smn_ug_a9002.html
index c2245c1c9..7aee82e73 100644
--- a/docs/smn/umn/smn_ug_a9002.html
+++ b/docs/smn/umn/smn_ug_a9002.html
@@ -108,13 +108,13 @@
Table 3 HTTP/HTTPS notification message bodyParameter
|
-Description
+ | Description
|
|---|
type
|
-Indicates the message type, which is Notification.
+ | Indicates the message type, which is Notification.
|
signature
@@ -184,19 +184,19 @@
Table 4 Parameters of HTTP/HTTPS subscription cancellation message formatParameter
|
-Description
+ | Description
|
|---|
type
|
-Indicates the message type. Its value is UnsubscribeConfirmation.
+ | Indicates the message type. Its value is UnsubscribeConfirmation.
|
signature
|
Indicates the signature information.
-The signature includes the message, message_id, subscribe_url, timestamp, topic_urn, and type fields. For details about signature verification, see Message Signature Verification.
+The signature includes the message, message_id, subscribe_url, timestamp, topic_urn, and type fields. For details about signature verification, see Message Signature Verification.
|
topic_urn
diff --git a/docs/smn/umn/smn_ug_b0000.html b/docs/smn/umn/smn_ug_b0000.html
index 452438f66..c1c9963d8 100644
--- a/docs/smn/umn/smn_ug_b0000.html
+++ b/docs/smn/umn/smn_ug_b0000.html
@@ -28,7 +28,7 @@
| 2023-03-31
|
This issue incorporates the following changes:
-
+
|
2019-09-30
@@ -98,7 +98,7 @@
| 2017-05-30
|
This issue incorporates the following changes:
-- Removed the Publish Message button from the Topic page.
- Disallowed line breaks in a topic display name.
+- Removed the Publish Message button from the Topic page.
- Disallowed line breaks in a topic display name.
|
2017-03-30
| |
|
|---|
|
