|endpoint||The subscription endpoint.|
|protocol||What type of subscription to add.|
|subscriber||The id of the SNS subscription resource created under |
|dead||Queue to be used as dead letter queue.|
|filter||The filter policy.|
|raw||true if raw message delivery is enabled for the subscription.|
|region?||The region where the topic resides, in the case of cross-region subscriptions.|
|subscriber||The scope in which to create the SNS subscription resource.|
The subscription endpoint.
The meaning of this value depends on the value for 'protocol'.
What type of subscription to add.
The id of the SNS subscription resource created under
cases, it is recommended to use the
uniqueId of the topic you are
(optional, default: No dead letter queue enabled.)
Queue to be used as dead letter queue.
If not passed no dead letter queue is enabled.
(optional, default: all messages are delivered)
The filter policy.
(optional, default: false)
true if raw message delivery is enabled for the subscription.
Raw messages are free of JSON formatting and can be sent to HTTP/S and Amazon SQS endpoints. For more information, see GetSubscriptionAttributes in the Amazon Simple Notification Service API Reference.
(optional, default: the region where the CloudFormation stack is being deployed.)
The region where the topic resides, in the case of cross-region subscriptions.
(optional, default: use the topic as the scope of the subscription, in which case
subscriberId must be defined.)
The scope in which to create the SNS subscription resource.
Normally you'd want the subscription to be created on the consuming stack because the topic is usually referenced by the consumer's resource policy (e.g. SQS queue policy). Otherwise, it will cause a cyclic reference.
If this is undefined, the subscription will be created on the topic's stack.