Updated the documentation.

Author: Michael Khmelnitsky

doc_source/SendMessageToHttp.verify.signature.md

@@ -48,7 +48,7 @@ The following example is a string to sign for a `Notification`\.
        Timestamp
        2012-06-05T04:37:04.321Z
        TopicArn
-       arn:aws:sns:us-east-1:123456789012:s4-MySNSTopic-1G1WEFCOXTC0P
+       arn:aws:sns:us-east-2:123456789012:s4-MySNSTopic-1G1WEFCOXTC0P
        Type
        Notification
    ```  

doc_source/sns-access-policy-use-cases.md

@@ -16,7 +16,7 @@ Let's say you have a topic in the Amazon SNS system\. In the simplest case, you
 
 You can do this using the Amazon SNS API action `AddPermission`\. It takes a topic, a list of AWS account IDs, a list of actions, and a label, and automatically creates a new statement in the topic's access control policy\. In this case, you don't write a policy yourself, because Amazon SNS automatically generates the new policy statement for you\. You can remove the policy statement later by calling `RemovePermission` with its label\.
 
-For example, if you called `AddPermission` on the topic arn:aws:sns:us\-east\-1:444455556666:MyTopic, with AWS account ID 1111\-2222\-3333, the `Publish` action, and the label `give-1234-publish`, Amazon SNS would generate and insert the following access control policy statement:
+For example, if you called `AddPermission` on the topic arn:aws:sns:us\-east\-2:444455556666:MyTopic, with AWS account ID 1111\-2222\-3333, the `Publish` action, and the label `give-1234-publish`, Amazon SNS would generate and insert the following access control policy statement:
 
 ```
 {
@@ -29,7 +29,7 @@ For example, if you called `AddPermission` on the topic arn:aws:sns:us\-east\-1:
       "AWS": "111122223333"
     },
     "Action": ["sns:Publish"],
-    "Resource": "arn:aws:sns:us-east-1:444455556666:MyTopic"
+    "Resource": "arn:aws:sns:us-east-2:444455556666:MyTopic"
   }]
 }
 ```
@@ -55,7 +55,7 @@ The following example of a full policy gives the AWS account ID 1111\-2222\-3333
       "AWS": "111122223333"
     },
     "Action": ["sns:Subscribe"],
-    "Resource": "arn:aws:sns:us-east-1:444455556666:MyTopic",
+    "Resource": "arn:aws:sns:us-east-2:444455556666:MyTopic",
     "Condition": {
       "StringEquals": {
         "sns:Protocol": "https"
@@ -83,17 +83,17 @@ The example presented below is an Amazon SQS policy \(controlling access to your
     "Effect": "Allow",
     "Principal": "*",
     "Action": ["sqs:SendMessage"],
-    "Resource": "arn:aws:sqs:us-east-1:444455556666:MyQueue",
+    "Resource": "arn:aws:sqs:us-east-2:444455556666:MyQueue",
     "Condition": {
       "ArnEquals": {
-        "aws:SourceArn": "arn:aws:sns:us-east-1:444455556666:MyTopic"
+        "aws:SourceArn": "arn:aws:sns:us-east-2:444455556666:MyTopic"
       }
     }
   }]
 }
 ```
 
-This policy uses the `aws:SourceArn` condition to restrict access to the queue based on the source of the message being sent to the queue\. You can use this type of policy to allow Amazon SNS to send messages to your queue only if the messages are coming from one of your own topics\. In this case, you specify a particular one of your topics, whose ARN is arn:aws:sns:us\-east\-1:444455556666:MyTopic\.
+This policy uses the `aws:SourceArn` condition to restrict access to the queue based on the source of the message being sent to the queue\. You can use this type of policy to allow Amazon SNS to send messages to your queue only if the messages are coming from one of your own topics\. In this case, you specify a particular one of your topics, whose ARN is arn:aws:sns:us\-east\-2:444455556666:MyTopic\.
 
 The preceding policy is an example of the Amazon SQS policy you could write and add to a specific queue\. It would grant Amazon SNS and other AWS products access\. Amazon SNS gives a default policy to all newly created topics\. The default policy gives all other AWS products access to your topic\. This default policy uses an `aws:SourceArn` condition to ensure that AWS products access your topic only on behalf of AWS resources you own\.
 
@@ -115,7 +115,7 @@ If you publish messages directly \(rather than having an AWS resource publish me
     "Effect": "Allow",
     "Principal": "*",
     "Action": "sns:Publish",
-    "Resource": "arn:aws:sns:us-east-1:111122223333:MyTopic",
+    "Resource": "arn:aws:sns:us-east-2:111122223333:MyTopic",
     "Condition": {
       "StringEquals": {
         "AWS:SourceAccount": "444455556666"
@@ -142,7 +142,7 @@ The following example statement uses the `ArnLike` condition to make sure the AR
     "Effect": "Allow",
     "Principal": "*",
     "Action": "sns:Publish",
-    "Resource": "arn:aws:sns:us-east-1:111122223333:MyTopic",
+    "Resource": "arn:aws:sns:us-east-2:111122223333:MyTopic",
     "Condition": {
       "StringEquals": {
         "AWS:SourceAccount": "444455556666"
@@ -166,10 +166,10 @@ In this case, the CloudWatch alarm in account `111122223333` is allowed to publi
     "Effect": "Allow",
     "Principal": "*",
     "Action": "SNS:Publish",
-    "Resource": "arn:aws:sns:us-east-1:444455556666:MyTopic",
+    "Resource": "arn:aws:sns:us-east-2:444455556666:MyTopic",
     "Condition": {
       "ArnLike": {
-        "aws:SourceArn": "arn:aws:cloudwatch:us-east-1:111122223333:alarm:MyAlarm"
+        "aws:SourceArn": "arn:aws:cloudwatch:us-east-2:111122223333:alarm:MyAlarm"
       }
     }
   }]

doc_source/sns-document-history.md

@@ -5,6 +5,7 @@ The following table lists changes to the *Amazon Simple Notification Service Dev
 
 | Date | Documentation Update | 
 | --- | --- | 
+| October 18, 2019 |  [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-document-history.html)  | 
 | October 16, 2019 |  [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-document-history.html)  | 
 | October 10, 2019 | Fixed the code excerpt that initializes and uses the SNSMessageAttributeClass in the [To Publish a Message with Attributes to an Amazon SNS Topic Using the AWS SDK for \.NET](sns-tutorial-publish-message-with-attributes.md#publish-message-with-attributes-aws-dot-net) section\. | 
 | October 8, 2019 |  [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-document-history.html)  | 

doc_source/sns-http-https-endpoint-as-subscriber.md

@@ -191,7 +191,7 @@ If you added the following policy to an IAM user or group, you would give that u
           "Sid":"AllowPublishToMyTopic",
           "Effect":"Allow",
           "Action":"sns:Publish",
-          "Resource":"arn:aws:sns:us-east-1:123456789012:MyTopic"
+          "Resource":"arn:aws:sns:us-east-2:123456789012:MyTopic"
         }
       ]
     }
@@ -215,7 +215,7 @@ If you added the following policy to a topic MyTopic in account 123456789012, yo
             "AWS":"111122223333"
           },
           "Action":"sns:Publish",
-          "Resource":"arn:aws:sns:us-east-1:123456789012:MyTopic"
+          "Resource":"arn:aws:sns:us-east-2:123456789012:MyTopic"
         }
       ]
     }

doc_source/sns-message-and-json-formats.md

@@ -54,7 +54,7 @@ The subscription confirmation message is a POST message with a message body that
 A string that describes the message\. For subscription confirmation, this string looks like this:  
 
 ```
-You have chosen to subscribe to the topic arn:aws:sns:us-east-1:123456789012:MyTopic.\nTo confirm the subscription, visit the SubscribeURL included in this message.
+You have chosen to subscribe to the topic arn:aws:sns:us-east-2:123456789012:MyTopic.\nTo confirm the subscription, visit the SubscribeURL included in this message.
 ```
 
 **`MessageId`**  
@@ -184,7 +184,7 @@ The unsubscribe confirmation message is a POST message with a message body that
 A string that describes the message\. For unsubscribe confirmation, this string looks like this:  
 
 ```
-You have chosen to deactivate subscription arn:aws:sns:us-east-1:123456789012:MyTopic:2bcfbf39-05c3-41de-beaa-fcfcc21c8f55.\nTo cancel this operation and restore the subscription, visit the SubscribeURL included in this message.
+You have chosen to deactivate subscription arn:aws:sns:us-east-2:123456789012:MyTopic:2bcfbf39-05c3-41de-beaa-fcfcc21c8f55.\nTo cancel this operation and restore the subscription, visit the SubscribeURL included in this message.
 ```
 
 **`MessageId`**  
@@ -247,9 +247,9 @@ User-Agent: Amazon Simple Notification Service Agent
 If you send a request to the SetSubscriptionAttributes action and set the AttributeName parameter to a value of `DeliveryPolicy`, the value of the AttributeValue parameter must be a valid JSON object\. For example, the following example sets the delivery policy to 5 total retries\.
 
 ```
-http://sns.us-east-1.amazonaws.com/
+http://sns.us-east-2.amazonaws.com/
 ?Action=SetSubscriptionAttributes
-&SubscriptionArn=arn%3Aaws%3Asns%3Aus-east-1%3A123456789012%3AMy-Topic%3A80289ba6-0fd4-4079-afb4-ce8c8260f0ca
+&SubscriptionArn=arn%3Aaws%3Asns%3Aus-east-2%3A123456789012%3AMy-Topic%3A80289ba6-0fd4-4079-afb4-ce8c8260f0ca
 &AttributeName=DeliveryPolicy
 &AttributeValue={"healthyRetryPolicy":{"numRetries":5}}
 ...
@@ -279,9 +279,9 @@ For more information about the SetSubscriptionAttribute action, go to [SetSubscr
 If you send a request to the SetTopicAttributes action and set the AttributeName parameter to a value of `DeliveryPolicy`, the value of the AttributeValue parameter must be a valid JSON object\. For example, the following example sets the delivery policy to 5 total retries\.
 
 ```
-http://sns.us-east-1.amazonaws.com/
+http://sns.us-east-2.amazonaws.com/
 ?Action=SetTopicAttributes
-&TopicArn=arn%3Aaws%3Asns%3Aus-east-1%3A123456789012%3AMy-Topic
+&TopicArn=arn%3Aaws%3Asns%3Aus-east-2%3A123456789012%3AMy-Topic
 &AttributeName=DeliveryPolicy
 &AttributeValue={"http":{"defaultHealthyRetryPolicy":{"numRetries":5}}}
 ...

doc_source/sns-msg-status.md

@@ -52,7 +52,7 @@ After you configure message delivery status attributes for an application endpoi
         "token": "Examplei7fFachkJ1xjlqT64RaBkcGHochmf1VQAr9k-IBJtKjp7fedYPzEwT_Pq3Tu0lroqro1cwWJUvgkcPPYcaXCpPWmG3Bqn-wiqIEzp5zZ7y_jsM0PKPxKhddCzx6paEsyay9Zn3D4wNUJb8m6HXrBf9dqaEw",
         "attempts": 1,
         "providerResponse": "{\"multicast_id\":5138139752481671853,\"success\":1,\"failure\":0,\"canonical_ids\":0,\"results\":[{\"message_id\":\"0:1422313659698010%d6ba8edff9fd7ecd\"}]}",
-        "destination": "arn:aws:sns:us-east-1:111122223333:endpoint/FCM/FCMPushApp/c23e42de-3699-3639-84dd-65f84474629d"
+        "destination": "arn:aws:sns:us-east-2:111122223333:endpoint/FCM/FCMPushApp/c23e42de-3699-3639-84dd-65f84474629d"
     }
 }
 ```
@@ -72,7 +72,7 @@ After you configure message delivery status attributes for an application endpoi
         "token": "examp1e29z6j5c4df46f809505189c4c83fjcgf7f6257e98542d2jt3395kj73",
         "attempts": 1,
         "providerResponse": "NotificationErrorResponse(command=8, status=InvalidToken, id=1, cause=null)",
-        "destination": "arn:aws:sns:us-east-1:111122223333:endpoint/APNS_SANDBOX/APNSPushApp/986cb8a1-4f6b-34b1-9a1b-d9e9cb553944"
+        "destination": "arn:aws:sns:us-east-2:111122223333:endpoint/APNS_SANDBOX/APNSPushApp/986cb8a1-4f6b-34b1-9a1b-d9e9cb553944"
     }
 }
 ```

doc_source/sns-release-notes.md

@@ -5,7 +5,8 @@ The following table lists Amazon SNS feature releases and improvements\. For cha
 
 | Date | Feature Release | 
 | --- | --- | 
-| September 10, 2019 | Amazon SNS supports the apns\-push\-type header field for mobile notifications sent through APNs\. For more information, see [Sending Messages to APNs as Background Notifications](sns-send-custom-platform-specific-payloads-mobile-devices.md#mobile-push-send-message-apns-background-notification)\. | 
+| October 18, 2019 | You can specify a custom APNs header value\. For more information, see [Sending Messages to APNs as Alert or Background Notifications](sns-send-custom-platform-specific-payloads-mobile-devices.md#mobile-push-send-message-apns-background-notification)\. | 
+| September 10, 2019 | Amazon SNS supports the apns\-push\-type header field for mobile notifications sent through APNs\. For more information, see [Sending Messages to APNs as Alert or Background Notifications](sns-send-custom-platform-specific-payloads-mobile-devices.md#mobile-push-send-message-apns-background-notification)\. | 
 | July 24, 2019 | You can troubleshoot messages passing through Amazon SNS topics using AWS X\-Ray\. For more information, see [Troubleshooting Amazon Simple Notification Service Topics Using AWS X\-Ray](sns-troubleshooting-using-x-ray.md) section\.  | 
 | July 5, 2019 |  [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-release-notes.html)  | 
 | May 16, 2019 |  [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-release-notes.html)  | 

doc_source/sns-send-custom-platform-specific-payloads-mobile-devices.md

@@ -47,16 +47,42 @@ one of the notification platforms.",
 }
 ```
 
-## Sending Messages to APNs as Background Notifications<a name="mobile-push-send-message-apns-background-notification"></a>
+## Sending Messages to APNs as Alert or Background Notifications<a name="mobile-push-send-message-apns-background-notification"></a>
 
-Amazon SNS sets the `apns-push-type` APNs header to `alert` or `background` depending on the `content-available` key in your APNs JSON payload configuration\. For more information, see [Pushing Background Updates to Your App](https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app) in the APNs documentation\.
-+ An `alert` APNs notification informs your users by displaying an alert message, playing a sound, or adding a badge to your application’s icon\.
+Amazon SNS can send messages to APNs as `alert` or `background` notifications \(for more information, see [Pushing Background Updates to Your App](https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app) in the APNs documentation\)\.
++ An `alert` APNs notification informs the user by displaying an alert message, playing a sound, or adding a badge to your application’s icon\.
 + A `background` APNs notification wakes up or instructs your application to act upon the content of the notification, without informing the user\.
 
+### Specifying Custom APNs Header Values<a name="specify-custom-header-value"></a>
+
+We recommend specifying custom values for the `AWS.SNS.MOBILE.APNS.PUSH_TYPE` [reserved message attribute](sns-message-attributes.md#sns-attrib-mobile-reserved) using the Amazon SNS `Publish` API action, AWS SDKs, or the AWS CLI\. The following CLI example sets `content-available` to `1` and `apns-push-type` to `background` for the specified topic\. 
+
+```
+aws sns publish \
+--endpoint-url https://sns.us-east-1.amazonaws.com \
+--target-arn arn:aws:sns:us-east-1:123456789012:endpoint/APNS_PLATFORM/MYAPP/1234a567-bc89-012d-3e45-6fg7h890123i \
+--message '{"APNS_PLATFORM":"{\"aps\":{\"content-available\":1}}"}' \
+--message-attributes '{ \
+  "AWS.SNS.MOBILE.APNS.TOPIC":{"DataType":"String","StringValue":"com.amazon.mobile.messaging.myapp"}, \
+  "AWS.SNS.MOBILE.APNS.PRIORITY":{"DataType":"String","StringValue":"10"}}', \
+  "AWS.SNS.MOBILE.APNS.PUSH_TYPE":{"DataType":"String","StringValue":"background"} \
+--message-structure json
+```
+
+### Inferring the APNs Push Type Header from the Payload<a name="inferring-push-type-header-from-payload"></a>
+
+If you don't set the `apns-push-type` APNs header, Amazon SNS sets header to `alert` or `background` depending on the `content-available` key in the `aps` dictionary of your JSON\-formatted APNs payload configuration\.
+
+**Note**  
+Amazon SNS is able to infer only `alert` or `background` headers, although the `apns-push-type` header can be set to other values\.
++ `apns-push-type` is set to `alert`
+  + If the `aps` dictionary contains `content-available` set to `1` and *one or more keys* that trigger user interactions\.
+  + If the `aps` dictionary contains `content-available` set to `0` *or* if the `content-available` key is absent\.
+  + If the value of the `content-available` key isn’t an integer or a Boolean\.
++ `apns-push-type` is set to `background`
+  + If the `aps` dictionary *only* contains `content-available` set to `1` and *no other keys* that trigger user interactions\.
 **Important**  
-If Amazon SNS sends a raw configuration object for APNs as a background\-only notification, you must include the `content-available` key in the `aps` dictionary and set the value to `1`\.  
-Although you can include custom keys, the `aps` dictionary must not contain any keys that trigger user interactions \(for example, alerts, badges, or sounds\)\.
-If the value of the `content-available` field isn’t an integer or a Boolean, the notification defaults to `alert`\.
+If Amazon SNS sends a raw configuration object for APNs as a background\-only notification, you must include `content-available` set to `1` in the `aps` dictionary\. Although you can include custom keys, the `aps` dictionary must not contain any keys that trigger user interactions \(for example, alerts, badges, or sounds\)\.
 
 The following is an example raw configuration object\.
 

doc_source/sns-send-message-to-sqs-cross-account.md

@@ -21,7 +21,7 @@ When the queue owner creates the subscription, the subscription does not require
             "AWS":"111122223333"
           },
           "Action":"sns:Subscribe",
-          "Resource":"arn:aws:sns:us-east-1:123456789012:MyTopic"
+          "Resource":"arn:aws:sns:us-east-2:123456789012:MyTopic"
         }
       ]
     }
@@ -62,7 +62,7 @@ After this policy has been set on MyTopic, a user can log in to the Amazon SNS c
  The user can also use the access key and secret key for the AWS account 111122223333 to issue the `sns-subscribe` command or call the `[Subscribe](https://docs.aws.amazon.com/sns/latest/api/API_Subscribe.html)` API action to subscribe an Amazon SQS queue to MyTopic in the account 123456789012\. The following `[sns\-subscribe](https://docs.aws.amazon.com/cli/latest/reference/sns/subscribe.html)` CLI command subscribes the queue MyQ from account 111122223333 to the topic MyTopic in account 123456789012\.
 
 ```
-aws sns subscribe --topic-arn arn:aws:sns:us-east-1:123456789012:MyTopic --protocol sqs --notification-endpoint arn:aws:sqs:us-east-1:111122223333:MyQ
+aws sns subscribe --topic-arn arn:aws:sns:us-east-2:123456789012:MyTopic --protocol sqs --notification-endpoint arn:aws:sqs:us-east-2:111122223333:MyQ
 ```
 
 **Note**  

doc_source/sns-server-side-encryption.md

@@ -126,7 +126,7 @@ The publisher must have the `kms:GenerateDataKey` and `kms:Decrypt` permissions
       "kms:GenerateDataKey",
       "kms:Decrypt"
     ],
-    "Resource": "arn:aws:kms:us-east-2:123456789012:key/1234abcd-12ab-34cd-56ef-1234567890ab"
+    "Resource": "arn:aws:kms:default-regionus-east-2:123456789012:key/1234abcd-12ab-34cd-56ef-1234567890ab"
   }, {
     "Effect": "Allow",
     "Action": [
@@ -141,9 +141,6 @@ The publisher must have the `kms:GenerateDataKey` and `kms:Decrypt` permissions
 
 Several AWS services publish events to Amazon SNS topics\. To allow these event sources to work with encrypted topics, you must perform the following steps\.
 
-**Note**  
-Currently, CloudWatch alarms don't work with Amazon SNS encrypted topics\. For information about publishing alarms to unencrypted topics, see [Using Amazon CloudWatch Alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/) in the *Amazon CloudWatch User Guide*\.
-
 1. Use the AWS managed CMK for Amazon SNS\.
 
 1. To allow the AWS service to have the `kms:GenerateDataKey*` and `kms:Decrypt` permissions, add the following statement to the CMK policy\.