Concept
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
-
- A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in an AZ will not affect other AZs.
-
Figure 1 shows the relationship between regions and AZs.
-
Figure 1 Regions and AZs
-
-
Selecting a Region
Select a region closest to your target users for low network latency and quick access.
-
-
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
-
- For high DR capability, deploy resources in different AZs within the same region.
- For low network latency, deploy resources in the same AZ.
-
-
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
-
-
Concept
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
+
- A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
+
Figure 1 shows the relationship between regions and AZs.
+
Figure 1 Regions and AZs
+
+
Selecting a Region
Select a region closest to your target users for lower network latency and quick access.
+
+
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
+
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
+
+
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+
+
The advanced mode provides a more flexible topic policy. You can specify which users and cloud services can perform which topic operations, for example, querying topic details, modifying topics, publishing messages, and deleting topics.
-
Introduction to Topic Policies
A topic policy is configured by a topic creator to allow or disallow other users or cloud services to perform specified operations to a topic. Table 1 lists the elements consisting of a topic policy.
-
-
Table 1 Topic policy elementsParameter
- |
-Description
- |
-Constraint
- |
-
|---|
-
-Version
- |
-Policy specification version
- |
-Currently, only 2016-09-07 is supported.
- |
-
-Id
- |
-Policy ID, which uniquely identifies a policy
- |
-The policy ID cannot be left blank.
- |
-
-Statement
- |
-Statements used to configure which users and cloud services can perform specified operations in a topic policy. Each policy may contain one or more statements.
- |
-A policy must contain at least one statement. For details about elements in a statement, see Statement Elements.
- |
-
-
-
-
-
The following is an example topic policy, which contains two statements, Statement1 and Statement2.
-
{
- "Version": "2016-09-07",
- "Id": "access_policy_01",
- "Statement": [
- {Statement1},
- {Statement2}
- ]
-}
-
-
Statement Elements
Table 2 lists the elements composed of a statement, as shown in the following example topic policy:
-
{
- "Version": "2016-09-07",
- "Id": "__default_policy_ID",
- "Statement": [
- //The first statement.
- {
- "Sid": "__user_pub_0",
- "Effect": "Allow",
- "Principal": {
- "CSP": [
- "urn:csp:iam::123456789:root",
- "urn:csp:iam::987654321:root"
- ]
- },
- "Action": [
- "SMN:Publish",
- "SMN:QueryTopicDetail"
- ],
- "Resource": "urn:smn:regionId:e23bf08ebb924730b452426c60849564:ECM_BKS_Topic"
- },
- //The second statement
- {
- "Sid": "__service_pub_0",
- "Effect": "Allow",
- "Principal": {
- "Service": [
- "obs"
- ]
- },
- "Action": [
- "SMN:Publish",
- "SMN:QueryTopicDetail"
- ],
- "Resource": "urn:smn:regionId:e23bf08ebb924730b452426c60849564:ECM_BKS_Topic"
- }
- ]
-}
-
-
-
Table 2 Statement elements descriptionElement
- |
-Description
- |
-Constraint
- |
-
|---|
-
-Sid
- |
-Statement ID
- |
-The statement ID must be unique, for example, statement01 or statement02.
- |
-
-Effect
- |
-Statement effect
- |
-The value can be Allow or Deny.
- |
-
-Principal
-NotPrincipal
- |
-
- |
-Either the Principal or NotPrincipal element must be configured.
-If you enter CSP, you must specify user information in the format urn:csp:iam::domainId:root. You need to obtain the domain ID of each user you specify.
-If you enter Service, you must specify the cloud service names in lower case.
- |
-
-Action
-NotAction
- |
-- Action: allowed statement action
-- NotAction: statement action not allowed
You can use a wildcard character to configure a set of actions by type, for example, SMN:Update* and SMN:Delete*. If you only enter a wildcard character (*) in a statement, all supported actions are configured.
-
- |
-Either the Action or NotAction element must be configured.
-The following actions are supported:
-- SMN:UpdateTopic
- SMN:DeleteTopic
- SMN:QueryTopicDetail
- SMN:ListTopicAttributes
- SMN:UpdateTopicAttribute
- SMN:DeleteTopicAttributes
- SMN:DeleteTopicAttributeByName
- SMN:ListSubscriptionsByTopic
- SMN:Subscribe
- SMN:Unsubscribe
- SMN:Publish
-For details about mappings between actions and APIs, see section A.5 Mappings Between SMN Operations and APIs.
- |
-
-Resource
-NotResource
- |
-- Resource: topic to which a statement applies
- NotResource: topic to which the statement does not apply
- |
-Either the Resource or NotResource element must be configured.
-You need to enter a topic URN.
- |
-
-Condition
- |
-(Optional) Condition under which a policy statement takes effect
- |
-Enter supported condition operators and key words.
-For details, see Condition Elements.
- |
-
-
-
-
-
Condition Elements
Conditions determine whether a statement takes effect. They enable you to configure more fine-grained control over topic permissions. Table 3 lists elements in a condition.
-
-
Table 3 Condition elementsParameter
- |
-Description
- |
-Constraint
- |
-
|---|
-
-Condition operator
- |
-Character string, numeral, date, or time to be matched
- |
-The time you entered must comply with ISO 8601 specifications. For details, see Table 4.
- |
-
-Key word
- |
-Object to which the condition operation applies
- |
-The key word cannot be left blank. For details, see Table 5.
- |
-
-
-
-
-
A statement allows the requested operation only when all conditions in the statement are met. Otherwise, the operation will be denied.
-
As shown in Figure 1, when a condition contains multiple operators, for example, condition1 and condition2, an AND operation is executed.
-
When the operator condition1 contains multiple keywords, for example, conditionKey1 and conditionKey2, an AND operation is executed.
-
When the keyword conditionKey1 contains multiple values, for example, value11 and value12, an OR operation is executed.
-
Figure 1 Condition logic
-
An example condition is as follows:
"Condition": {
- "DateLessThan":{
- "csp:CurrentTime":"2016-11-07T15:35:00Z"
- },
- "StringLike": {
- "smn:Endpoint":["*@gmail.com","*@hotmail.com"]
- }
-}
-
-
-
Table 4 Condition operatorsCategory
- |
-Operator
- |
-Description
- |
-
|---|
-
-String
- |
-StringEquals
- |
-Match a string (case-sensitive).
- |
-
-StringNotEquals
- |
-Exclude a string (case-sensitive).
- |
-
-StringEqualsIgnoreCase
- |
-Match a string (case-insensitive).
- |
-
-StringNotEqualsIgnoreCase
- |
-Exclude a string (case-insensitive).
- |
-
-StringLike
- |
-Match a string. The value can contain one or more wildcard characters (*).
- |
-
-StringNotLike
- |
-Exclude a string. The value can contain one or more wildcard characters (*).
- |
-
-Numeric
- |
-NumericEquals
- |
-Match an integer or decimal.
- |
-
-NumericNotEquals
- |
-Exclude an integer or decimal.
- |
-
-NumericLessThan
- |
-Match any numeral less than an integer or decimal.
- |
-
-NumericLessThanEquals
- |
-Match any numeral less than or equal to an integer or decimal.
- |
-
-NumericGreaterThan
- |
-Match any numeral greater than an integer or decimal.
- |
-
-NumericGreaterThanEquals
- |
-Match any numeral greater than or equal to an integer or decimal.
- |
-
-Date
- |
-DateEquals
- |
-Match a date.
- |
-
-DateNotEquals
- |
-Exclude a date.
- |
-
-DateLessThan
- |
-Match any time earlier than a date and time point.
- |
-
-DateLessThanEquals
- |
-Match any time earlier than or equal to a date and time point.
- |
-
-DateGreaterThan
- |
-Match any time later than a date and time point.
- |
-
-DateGreaterThanEquals
- |
-Match any time later than or equal to a date and time point.
- |
-
-Bool
- |
-Bool
- |
-Match a Boolean value.
- |
-
-
-
-
-
-
-
Table 5 Condition key wordsKey Word
- |
-Description
- |
-
|---|
-
-csp:CurrentTime
- |
-Current time
- |
-
-smn:Protocol
- |
-Protocol of a subscription, which is valid only for the SMN:Subscribe action
- |
-
-smn:Endpoint
- |
-Endpoint of a subscription, which is valid only for the SMN:Subscribe action
- |
-
-
-
-
-
-
Simple Message Notification (SMN) is a reliable and flexible large-scale message notification service. It enables you to efficiently send messages to phone numbers, email addresses and HTTP/HTTPS servers and connect cloud services through notifications, reducing system complexity.
+
Simple Message Notification (SMN) is a reliable and flexible large-scale message notification service. It enables you to efficiently send messages to various endpoints, such as phone numbers, and email addresses,
SMN offers a publish/subscribe model to achieve one-to-multiple message subscriptions and notifications in a variety of message types. SMN involves two roles: publisher and subscriber. A publisher publishes messages to a topic, and SMN then delivers the messages to subscribers in the topic. The subscribers can be email addresses, phone numbers, message queues, and URLs.
A topic is a collection of messages and a logical access point, through which the publisher and the subscriber can interact with each other. Each topic has a unique topic name. The topic creator can configure topic policies to grant other users or cloud services permissions to perform certain operations to a topic, for example, querying subscriptions or publishing messages.
diff --git a/docs/smn/umn/en-us_topic_0043394889.html b/docs/smn/umn/en-us_topic_0043394889.html
index eef1f9fe..c310bc84 100644
--- a/docs/smn/umn/en-us_topic_0043394889.html
+++ b/docs/smn/umn/en-us_topic_0043394889.html
@@ -1,13 +1,13 @@
Message Template Management
-
Scenario
Message templates contain fixed and changeable content and can be used to send messages quickly. When you publish a message using a template, you can specify values for variables in the template.
-
Message templates are grouped by template name. You can create templates for different protocols using the same template name. You must specify the default protocol in any template name, or the system will not allow you to publish messages using that template name. When sending messages using a template, 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.
+
Scenarios
Message templates contain fixed and changeable content and can be used to create and send messages more quickly. When you use a template to publish a message, you can specify values for different variables in the template.
+
Message templates are identified by name, but you can create different templates with the same name as long as they are configured for different protocols. All template messages must include a Default template or they cannot be sent out. The Default template is used anytime a template has not been configured for a given protocol, but as long as there is a template for the protocol, then any subscriber who selected that protocol when they subscribed will receive a message using the corresponding template.
+
This section describes how to publish messages using a template.
-
To Create a Message Template
- Log in to the management console.
- Click
on the upper left to select the desired region and project. - In the Application category, click Simple Message Notification.
The SMN console is displayed.
- - In the navigation pane, choose Message Templates.
- Click Create Message Template.
The Create Message Template box is displayed.
-Figure 1 Create Message Template
+To Create a Message Template
- 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 Message Templates.
- In the upper right corner, click Create Message Template.
The Create Message Template dialog box is displayed.
+Figure 1 Create Message Template
- Specify the template name, protocol, and content.
Table 1 Parameters required for creating a message templateParameter
|
@@ -18,29 +18,29 @@
|---|
Template Name
|
Template name, which:
-- Contains letters, numerals, underscores (_), and hyphens (-) and starts with a letter or numeral.
- Is a character string 1 to 64 bytes long.
- Cannot be modified once the template is created.
+- Contains only letters, digits, hyphens (-), and underscores (_), and must start with a letter or digit.
- Can contain 1 to 64 bytes.
- Cannot be modified once the template is created.
|
Protocol
|
Endpoint protocol of the template, which cannot be changed once the template is created
-The value can be Default, SMS, HTTP, HTTPS, DMS, or Email.
-If you do not specify a protocol, the Default protocol is used.
+The protocol can be Default, SMS, HTTP, HTTPS, DMS, or Email.
+If you do not specify a protocol, Default is used.
|
Content
|
Template content
-You can use variables as placeholders. Before you send messages using the template, SMN replaces the variables with the message content you specify. A variable is a string of up to 21 characters. It may contain upper- or lower-case letters, numerals, hyphens (-), underscores (_), and periods (.) and must start with a letter or numeral.
+You can use variables as placeholders. Before you send messages using the template, SMN replaces the variables with the message content you specify. A variable can contain up to 21 characters and must start with a letter or digit. It can contain letters, digits, hyphens (-), underscores (_), and periods (.).
The message template must meet the following requirements:
- The template supports plain text only.
- The template content cannot be left blank and cannot exceed 256 KB.
-- A template can contain up to 90 non-repeating variables or 256 variables counting the repeated ones.
- When you send messages using a template, the message content you specify for each variable cannot exceed 1 KB.
+- The template can contain up to 256 variables in total, but that includes redundant variables. For unique variables, there can be no more than 90.
- When you send messages using a template, the message content you specify for each variable cannot exceed 1 KB.
|
For example, the template information is as follows:
