Skip to content
This repository was archived by the owner on Jun 16, 2023. It is now read-only.

Commit cb193f6

Browse files
author
Michael Khmelnitsky
committed
Updated the documentation.
1 parent 2248e79 commit cb193f6

5 files changed

+13
-8
lines changed

doc_source/mobile-platform-endpoint.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@ class RegistrationExample
278278
// The platform endpoint already exists for this token, but with
279279
// additional custom data that createEndpoint doesn't want to overwrite.
280280
// Just use the existing platform endpoint.
281-
endpoint = m[0].Groups[1].Value;
281+
endpointArn = m[0].Groups[1].Value;
282282
}
283283
else
284284
{

doc_source/sns-document-history.md

+1
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ The following table lists changes to the *Amazon Simple Notification Service Dev
55

66
| Date | Documentation Update |
77
| --- | --- |
8+
| October 16, 2019 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-document-history.html) |
89
| 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\. |
910
| October 8, 2019 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-document-history.html) |
1011
| October 3, 2019 | Revised the information in the following sections: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sns/latest/dg/sns-document-history.html) |

doc_source/sns-large-payload-raw-message-delivery.md

+8-3
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,15 @@
11
# Amazon SNS Large Payload and Raw Message Delivery<a name="sns-large-payload-raw-message-delivery"></a>
22

3-
Amazon SNS \(and Amazon SQS\) allows you to send large payload messages \(from 64 to 256 kilobytes in size\)\. To send large payloads, you must use an AWS SDK that supports Signature Version 4\.
3+
Amazon SNS and Amazon SQS let you send and receive large payloads \(from 64 to 256 kilobytes in size\)\.
44

5-
In addition to sending large payloads, with Amazon SNS you can now enable raw message delivery for messages delivered to either Amazon SQS endpoints or HTTP/S endpoints\. This eliminates the need for the endpoints to process JSON formatting, which is created for the Amazon SNS metadata when raw message delivery is not selected\. For example when enabling raw message delivery for an Amazon SQS endpoint, the Amazon SNS metadata is not included and the published message is delivered to the subscribed Amazon SQS endpoint as is\. When enabling raw message delivery for HTTP/S endpoints, the messages will contain an additional HTTP header `x-amz-sns-rawdelivery` with a value of `true` to indicate that the message is being published raw instead of with JSON formatting\. This enables those endpoints to understand what is being delivered and enables easier transition for subscriptions from JSON to raw delivery\.
5+
**Note**
6+
To send large payloads, you must use an AWS SDK that supports Signature Version 4\.
67

7-
To enable raw message delivery using one of the AWS SDKs, you must use the `SetSubscriptionAttribute` action and configure the `RawMessageDelivery` attribute with a value of `true`\. The default value is `false`\.
8+
To avoid having Amazon SQS and HTTP/S endpoints process the JSON formatting of messages, Amazon SNS also allows raw message delivery:
9+
+ When you enable raw message delivery for an Amazon SQS endpoint, any Amazon SNS metadata is stripped from the published message and the message is sent as\-is\.
10+
+ When you enable raw message delivery for HTTP/S endpoints, the HTTP header `x-amz-sns-rawdelivery` with its value set to `true` is added to the message, indicating that the message has been published without JSON formatting\.
11+
12+
To enable raw message delivery using an AWS SDK, you must use the `SetSubscriptionAttribute` API action and set the value of the `RawMessageDelivery` attribute to `true`\.
813

914
## Enabling Raw Message Delivery Using the AWS Management Console<a name="raw-message-console"></a>
1015

doc_source/sns-message-attributes.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@ Message attributes are optional and separate from—but are sent together with
66

77
For information about sending messages with attributes using the AWS Management Console or the AWS SDK for Java, see the [Tutorial: Publishing a Message with Attributes to an Amazon SNS Topic](sns-tutorial-publish-message-with-attributes.md) tutorial\.
88

9-
**Important**
10-
To use message attributes with Amazon SQS endpoints, you must set subscription attribute `Raw Message Delivery` to `True`\. For more information about raw message delivery, see [Amazon SNS Large Payload and Raw Message Delivery](sns-large-payload-raw-message-delivery.md)\.
9+
**Note**
1110
Message attributes are sent only when the message structure is String, not JSON\.
1211

1312
You can also use message attributes to help structure the push notification message for mobile endpoints\. In this scenario, the message attributes are used only to help structure the push notification message\. The attributes are not delivered to the endpoint as they are when sending messages with message attributes to Amazon SQS endpoints\.

doc_source/sns-server-side-encryption.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -144,9 +144,9 @@ Several AWS services publish events to Amazon SNS topics\. To allow these event
144144
**Note**
145145
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*\.
146146

147-
1. [Create a customer master key \(CMK\)\.](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html#create-keys-console)
147+
1. Use the AWS managed CMK for Amazon SNS\.
148148

149-
1. To allow the AWS service feature to have the `kms:GenerateDataKey*` and `kms:Decrypt` permissions, add the following statement to the policy of the CMK using the correct service principal\.
149+
1. To allow the AWS service to have the `kms:GenerateDataKey*` and `kms:Decrypt` permissions, add the following statement to the CMK policy\.
150150

151151
```
152152
{

0 commit comments

Comments
 (0)