opentf/website/source/docs/providers/aws/r/sns_topic_subscription.html.markdown

layout, page_title, sidebar_current, description

layout	page_title	sidebar_current	description
aws	AWS: sns_topic_subscription	docs-aws-resource-sns-topic-subscription	Provides a resource for subscribing to SNS topics.

aws_sns_topic_subscription

Provides a resource for subscribing to SNS topics. Requires that an SNS topic exist for the subscription to attach to. This resource allows you to automatically place messages sent to SNS topics in SQS queues, send them as HTTP(S) POST requests to a given endpoint, send SMS messages, or notify devices / applications. The most likely use case for Terraform users will probably be SQS queues.

Example Usage

You can directly supply a topic and ARN by hand in the topic_arn property along with the queue ARN:

resource "aws_sns_topic_subscription" "user_updates_sqs_target" {
    topic_arn = "arn:aws:sns:us-west-2:432981146916:user-updates-topic"
    protocol = "sqs"
    endpoint = "arn:aws:sqs:us-west-2:432981146916:terraform-queue-too"
}

Alternatively you can use the ARN properties of a managed SNS topic and SQS queue:

resource "aws_sns_topic" "user_updates" {
  name = "user-updates-topic"
}

resource "aws_sqs_queue" "user_updates_queue" {
	name = "user-updates-queue"
}

resource "aws_sns_topic_subscription" "user_updates_sqs_target" {
    topic_arn = "${aws_sns_topic.user_updates.arn}"
    protocol  = "sqs"
    endpoint  = "${aws_sqs_queue.user_updates_queue.arn}"
}

Argument Reference

The following arguments are supported:

• topic_arn - (Required) The ARN of the SNS topic to subscribe to
• protocol - (Required) The protocol to use. The possible values for this are: sqs, http, https, sms, or application. (email is an option but unsupported, see below)
• endpoint - (Required) The endpoint to send data to, the contents will vary with the protocol. (see below for more information)
• raw_message_delivery - (Optional) Boolean indicating whether or not to enable raw message delivery (the original message is directly passed, not wrapped in JSON with the original message in the message property).

Protocols supported

Supported SNS protocols include:

• http -- delivery of JSON-encoded message via HTTP POST
• https -- delivery of JSON-encoded message via HTTPS POST
• lambda -- delivery of JSON-encoded message to a lambda function
• sms -- delivery of message via SMS
• sqs -- delivery of JSON-encoded message to an Amazon SQS queue
• application -- delivery of JSON-encoded message to an EndpointArn for a mobile app and device

Unsupported protocols include the following:

• email -- delivery of message via SMTP
• email-json -- delivery of JSON-encoded message via SMTP

These are unsupported because the email address needs to be authorized and does not generate an ARN until the target email address has been validated. This breaks the Terraform model and as a result are not currently supported.

Specifying endpoints

Endpoints have different format requirements according to the protocol that is chosen.

• HTTP/HTTPS endpoints will require a URL to POST data to
• SMS endpoints are mobile numbers that are capable of receiving an SMS
• SQS endpoints come in the form of the SQS queue's ARN (not the URL of the queue) e.g: arn:aws:sqs:us-west-2:432981146916:terraform-queue-too
• Application endpoints are also the endpoint ARN for the mobile app and device.

Attributes Reference

The following attributes are exported:

• id - The ARN of the subscription
• topic_arn - The ARN of the topic the subscription belongs to
• protocol - The protocol being used
• endpoint - The full endpoint to send data to (SQS ARN, HTTP(S) URL, Application ARN, SMS number, etc.)
• arn - The ARN of the subscription stored as a more user-friendly property