Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Terraform Module to Provide an Amazon Simple Notification Service (SNS)

NotificationsYou must be signed in to change notification settings

cloudposse/terraform-aws-sns-topic

Repository files navigation

Project Banner

Latest ReleaseLast UpdatedSlack CommunityGet Support

Terraform module to provision SNS topic

Tip

👽 Use Atmos with Terraform

Cloud Posse usesatmos to easily orchestrate multiple environments using Terraform.
Works withGithub Actions,Atlantis, orSpacelift.

Watch demo of using Atmos with Terraform
Example of runningatmos to manage infrastructure from ourQuick Start tutorial.

Introduction

This module provides:

  • SNS topic creation
  • SNS topic policy
  • SNS topic subscriptions

It's possible to subscribe SQS as Dead Letter Queue.

Usage

Amazon Simple Notification Service (Amazon SNS) is a web service that coordinates and manages the delivery or sending of messages to subscribing endpoints or clients.SNS documentation

There are many ways SNS can be used. As an example we can imagine CloudWatch sending alerts to SNS, by using subscribers such notificationscan be sent further to PagerDuty, OpsGenie or any other oncall management tool.

Important

In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentationand the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact versionyou're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematicapproach for updating versions to avoid unexpected changes.

Examples

module"sns" {source="cloudposse/sns-topic/aws"# Cloud Posse recommends pinning every module to a specific version# version     = "x.x.x"attributes=var.attributesname=var.namenamespace=var.namespacestage=var.stagesubscribers={    opsgenie= {      protocol="https"      endpoint="https://api.example.com/v1/"      endpoint_auto_confirms=true    }  }sqs_dlq_enabled=false}

Requirements

NameVersion
terraform>= 1.3.0
aws>= 3.0

Providers

NameVersion
aws>= 3.0

Modules

NameSourceVersion
thiscloudposse/label/null0.25.0

Resources

NameType
aws_sns_topic.thisresource
aws_sns_topic_policy.thisresource
aws_sns_topic_subscription.thisresource
aws_sqs_queue.dead_letter_queueresource
aws_sqs_queue_policy.defaultresource
aws_iam_policy_document.aws_sns_topic_policydata source
aws_iam_policy_document.sqs_queue_policydata source

Inputs

NameDescriptionTypeDefaultRequired
additional_tag_mapAdditional key-value pairs to add to each map intags_as_list_of_maps. Not added totags orid.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration.
map(string){}no
allowed_aws_services_for_sns_publishedAWS services that will have permission to publish to SNS topic. Used when no external JSON policy is usedlist(string)[]no
allowed_iam_arns_for_sns_publishIAM role/user ARNs that will have permission to publish to SNS topic. Used when no external json policy is used.list(string)[]no
attributesID element. Additional attributes (e.g.workers orcluster) to add toid,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by thedelimiter
and treated as a single ID element.
list(string)[]no
content_based_deduplicationEnable content-based deduplication for FIFO topicsboolfalseno
contextSingle object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables asnull to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional_tag_map, which are merged.
any
{
"additional_tag_map": {},
"attributes": [],
"delimiter": null,
"descriptor_formats": {},
"enabled": true,
"environment": null,
"id_length_limit": null,
"label_key_case": null,
"label_order": [],
"label_value_case": null,
"labels_as_tags": [
"unset"
],
"name": null,
"namespace": null,
"regex_replace_chars": null,
"stage": null,
"tags": {},
"tenant": null
}
no
delimiterDelimiter to be used between ID elements.
Defaults to- (hyphen). Set to"" to use no delimiter at all.
stringnullno
delivery_policyThe SNS delivery policy as JSON.stringnullno
delivery_statusEnable Message delivery status for the various SNS subscription endpoints.
The success_role_arn and failure_role_arn arguments are used to give Amazon SNS write
access to use CloudWatch Logs on your behalf.
The success_sample_rate argument is for specifying the sample rate percentage (0-100) of
successfully delivered messages.
object({
application = optional(object({
success_role_arn = string
failure_role_arn = string
success_sample_rate = number
}))
firehose = optional(object({
success_role_arn = string
failure_role_arn = string
success_sample_rate = number
}))
http = optional(object({
success_role_arn = string
failure_role_arn = string
success_sample_rate = number
}))
lambda = optional(object({
success_role_arn = string
failure_role_arn = string
success_sample_rate = number
}))
sqs = optional(object({
success_role_arn = string
failure_role_arn = string
success_sample_rate = number
}))
})
{}no
descriptor_formatsDescribe additional descriptors to be output in thedescriptors output map.
Map of maps. Keys are names of descriptors. Values are maps of the form
{<br/> format = string<br/> labels = list(string)<br/>}
(Type isany so the map values can later be enhanced to provide additional options.)
format is a Terraform format string to be passed to theformat() function.
labels is a list of labels, in order, to pass toformat() function.
Label values will be normalized before being passed toformat() so they will be
identical to how they appear inid.
Default is{} (descriptors output will be empty).
any{}no
enabledSet to false to prevent the module from creating any resourcesboolnullno
encryption_enabledWhether or not to use encryption for SNS Topic. If set totrue and no custom value for KMS key (kms_master_key_id) is provided, it uses the defaultalias/aws/sns KMS key.booltrueno
environmentID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'stringnullno
fifo_queue_enabledWhether or not to create a FIFO (first-in-first-out) queueboolfalseno
fifo_topicWhether or not to create a FIFO (first-in-first-out) topicboolfalseno
id_length_limitLimitid to this many characters (minimum 6).
Set to0 for unlimited length.
Set tonull for keep the existing setting, which defaults to0.
Does not affectid_full.
numbernullno
kms_master_key_idThe ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK.string"alias/aws/sns"no
label_key_caseControls the letter case of thetags keys (label names) for tags generated by this module.
Does not affect keys of tags passed in via thetags input.
Possible values:lower,title,upper.
Default value:title.
stringnullno
label_orderThe order in which the labels (ID elements) appear in theid.
Defaults to ["namespace", "environment", "stage", "name", "attributes"].
You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.
list(string)nullno
label_value_caseControls the letter case of ID elements (labels) as included inid,
set as tag values, and output by this module individually.
Does not affect values of tags passed in via thetags input.
Possible values:lower,title,upper andnone (no transformation).
Set this totitle and setdelimiter to"" to yield Pascal Case IDs.
Default value:lower.
stringnullno
labels_as_tagsSet of labels (ID elements) to include as tags in thetags output.
Default is to include all labels.
Tags with empty values will not be included in thetags output.
Set to[] to suppress all generated tags.
Notes:
The value of thename tag, if included, will be theid, not thename.
Unlike othernull-label inputs, the initial setting oflabels_as_tags cannot be
changed in later chained modules. Attempts to change it will be silently ignored.
set(string)
[
"default"
]
no
nameID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.
This is the only ID element not also included as atag.
The "name" tag is set to the fullid string. There is no tag with the value of thename input.
stringnullno
namespaceID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally uniquestringnullno
redrive_policyThe SNS redrive policy as JSON. This overrides thedeadLetterTargetArn (supplied byvar.fifo_queue = true) passed in by the module.stringnullno
regex_replace_charsTerraform regular expression (regex) string.
Characters matching the regex will be removed from the ID elements.
If not set,"/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.
stringnullno
sns_topic_policy_jsonThe fully-formed AWS policy as JSONstring""no
sqs_dlq_enabledEnable delivery of failed notifications to SQS and monitor messages in queue.boolfalseno
sqs_dlq_max_message_sizeThe limit of how many bytes a message can contain before Amazon SQS rejects it. An integer from 1024 bytes (1 KiB) up to 262144 bytes (256 KiB). The default for this attribute is 262144 (256 KiB).number262144no
sqs_dlq_message_retention_secondsThe number of seconds Amazon SQS retains a message. Integer representing seconds, from 60 (1 minute) to 1209600 (14 days).number1209600no
sqs_queue_kms_data_key_reuse_period_secondsThe length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS againnumber300no
sqs_queue_kms_master_key_idThe ID of an AWS-managed customer master key (CMK) for Amazon SQS Queue or a custom CMKstring"alias/aws/sqs"no
stageID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'stringnullno
subscribersRequired configuration for subscibres to SNS topic.
map(object({
protocol = string
# The protocol to use. The possible values for this are: sqs, sms, lambda, application. (http or https are partially supported, see below) (email is an option but is unsupported, see below).
endpoint = string
# The endpoint to send data to, the contents will vary with the protocol. (see below for more information)
endpoint_auto_confirms = optional(bool, false)
# Boolean indicating whether the end point is capable of auto confirming subscription e.g., PagerDuty (default is false)
filter_policy = optional(string, null)
# The filter policy JSON that is assigned to the subscription. For more information, see Amazon SNS Filter Policies.
filter_policy_scope = optional(string, null)
# The filter policy scope that is assigned to the subscription. Whether thefilter_policy applies toMessageAttributes orMessageBody. Default is null.
raw_message_delivery = optional(bool, false)
# 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) (default is false)
}))
{}no
tagsAdditional tags (e.g.{'BusinessUnit': 'XYZ'}).
Neither the tag keys nor the tag values will be modified by this module.
map(string){}no
tenantID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is forstringnullno

Outputs

NameDescription
aws_sns_topic_subscriptionsSNS topic subscription.
dead_letter_queue_arnThe ARN of the dead letter queue.
dead_letter_queue_idThe ID for the created dead letter queue. Same as the URL.
dead_letter_queue_nameThe name for the created dead letter queue.
dead_letter_queue_urlThe URL for the created dead letter SQS queue.
sns_topicSNS topic.
sns_topic_arnSNS topic ARN.
sns_topic_idSNS topic ID.
sns_topic_nameSNS topic name.
sns_topic_ownerSNS topic owner.

Related Projects

Check out these related projects.

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-goterraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team.
✅ Your team owns everything.
✅ 100% Open Source and backed by fanatical support.

Request Quote

📚Learn More

Cloud Posse is the leadingDevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

  • Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
  • Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
  • Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
  • Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
  • GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Request Quote

Day-2: Your Operational Mastery

  • Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
  • Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
  • Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
  • Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
  • Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
  • Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
  • Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

Request Quote

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use theissue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

  1. Review ourCode of Conduct andContributor Guidelines.
  2. Fork the repo on GitHub
  3. Clone the project to your own machine
  4. Commit changes to your own branch
  5. Push your work back up to your fork
  6. Submit aPull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Running Terraform Tests

We useAtmos to streamline how Terraform tests are run. It centralizes configuration and wraps common test workflows with easy-to-use commands.

All tests are located in thetest/ folder.

Under the hood, tests are powered by Terratest together with our internalTest Helpers library, providing robust infrastructure validation.

Setup dependencies:

To run tests:

  • Run all tests:
    atmostest run
  • Clean up test artifacts:
    atmostest clean
  • Explore additional test options:
    atmostest --help

The configuration for test commands is centrally managed. To review what's being imported, see theatmos.yaml file.

Learn more about ourautomated testing in our documentation or implementingcustom commands with atmos.

🌎 Slack Community

Join ourOpen Source Community on Slack. It'sFREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totallysweet infrastructure.

📰 Newsletter

Sign up forour newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus alive Q&A that you can’t find anywhere else.It'sFREE for everyone!

License

License

Preamble to the Apache License, Version 2.0

Licensed to the Apache Software Foundation (ASF) under oneor more contributor license agreements.  See the NOTICE filedistributed with this work for additional informationregarding copyright ownership.  The ASF licenses this fileto you under the Apache License, Version 2.0 (the"License"); you may not use this file except in compliancewith the License.  You may obtain a copy of the License at  https://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, either express or implied.  See the License for thespecific language governing permissions and limitationsunder the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.


Copyright © 2017-2025Cloud Posse, LLC

README footer

Beacon

About

Terraform Module to Provide an Amazon Simple Notification Service (SNS)

Topics

Resources

Code of conduct

Security policy

Stars

Watchers

Forks

Sponsor this project

 

Packages

No packages published

Contributors19


[8]ページ先頭

©2009-2025 Movatter.jp