community.aws.sns_topic – Manages AWS SNS topics and subscriptions
Note
This plugin is part of the community.aws collection (version 1.5.0).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.aws
.
To use it in a playbook, specify: community.aws.sns_topic
.
New in version 1.0.0: of community.aws
Synopsis
The community.aws.sns_topic module allows you to create, delete, and manage subscriptions for AWS SNS topics.
As of 2.6, this module can be use to subscribe and unsubscribe to topics outside of your AWS account.
Requirements
The below requirements are needed on the host that executes this module.
boto
python >= 2.6
Parameters
Parameter |
Comments |
---|---|
AWS access key. If not set then the value of the AWS_ACCESS_KEY_ID, AWS_ACCESS_KEY or EC2_ACCESS_KEY environment variable is used. If profile is set this parameter is ignored. Passing the aws_access_key and profile options at the same time has been deprecated and the options will be made mutually exclusive after 2022-06-01. |
|
The location of a CA Bundle to use when validating SSL certificates. Only used for boto3 based modules. Note: The CA Bundle is read ‘module’ side and may need to be explicitly copied from the controller if not run locally. |
|
A dictionary to modify the botocore configuration. Parameters can be found at https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html#botocore.config.Config. Only the ‘user_agent’ key is used for boto modules. See http://boto.cloudhackers.com/en/latest/boto_config_tut.html#boto for more boto configuration. |
|
AWS secret key. If not set then the value of the AWS_SECRET_ACCESS_KEY, AWS_SECRET_KEY, or EC2_SECRET_KEY environment variable is used. If profile is set this parameter is ignored. Passing the aws_secret_key and profile options at the same time has been deprecated and the options will be made mutually exclusive after 2022-06-01. |
|
Use a botocore.endpoint logger to parse the unique (rather than total) “resource:action” API calls made during a task, outputing the set to the resource_actions key in the task results. Use the aws_resource_action callback to output to total list made during a playbook. The ANSIBLE_DEBUG_BOTOCORE_LOGS environment variable may also be used. Choices:
|
|
Delivery policy to apply to the SNS topic. |
|
Display name of the topic. |
|
Url to use to connect to EC2 or your Eucalyptus cloud (by default the module will use EC2 endpoints). Ignored for modules where region is required. Must be specified for all other modules if region is not used. If not set then the value of the EC2_URL environment variable, if any, is used. |
|
The name or ARN of the SNS topic to manage. |
|
Policy to apply to the SNS topic. |
|
Uses a boto profile. Only works with boto >= 2.24.0. Using profile will override aws_access_key, aws_secret_key and security_token and support for passing them at the same time as profile has been deprecated. aws_access_key, aws_secret_key and security_token will be made mutually exclusive with profile after 2022-06-01. |
|
Whether to purge any subscriptions not listed here. NOTE: AWS does not allow you to purge any PendingConfirmation subscriptions, so if any exist and would be purged, they are silently skipped. This means that somebody could come back later and confirm the subscription. Sorry. Blame Amazon. Choices:
|
|
The AWS region to use. If not specified then the value of the AWS_REGION or EC2_REGION environment variable, if any, is used. See http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region |
|
AWS STS security token. If not set then the value of the AWS_SECURITY_TOKEN or EC2_SECURITY_TOKEN environment variable is used. If profile is set this parameter is ignored. Passing the security_token and profile options at the same time has been deprecated and the options will be made mutually exclusive after 2022-06-01. |
|
Whether to create or destroy an SNS topic. Choices:
|
|
List of subscriptions to apply to the topic. Note that AWS requires subscriptions to be confirmed, so you will need to confirm any new subscriptions. Default: [] |
|
Endpoint of subscription. |
|
Protocol of subscription. |
|
When set to “no”, SSL certificates will not be validated for boto versions >= 2.6.0. Choices:
|
Notes
Note
If parameters are not set within the module, the following environment variables can be used in decreasing order of precedence
AWS_URL
orEC2_URL
,AWS_PROFILE
orAWS_DEFAULT_PROFILE
,AWS_ACCESS_KEY_ID
orAWS_ACCESS_KEY
orEC2_ACCESS_KEY
,AWS_SECRET_ACCESS_KEY
orAWS_SECRET_KEY
orEC2_SECRET_KEY
,AWS_SECURITY_TOKEN
orEC2_SECURITY_TOKEN
,AWS_REGION
orEC2_REGION
,AWS_CA_BUNDLE
Ansible uses the boto configuration file (typically ~/.boto) if no credentials are provided. See https://boto.readthedocs.io/en/latest/boto_config_tut.html
AWS_REGION
orEC2_REGION
can be typically be used to specify the AWS region, when required, but this can also be configured in the boto config file
Examples
- name: Create alarm SNS topic
community.aws.sns_topic:
name: "alarms"
state: present
display_name: "alarm SNS topic"
delivery_policy:
http:
defaultHealthyRetryPolicy:
minDelayTarget: 2
maxDelayTarget: 4
numRetries: 3
numMaxDelayRetries: 5
backoffFunction: "<linear|arithmetic|geometric|exponential>"
disableSubscriptionOverrides: True
defaultThrottlePolicy:
maxReceivesPerSecond: 10
subscriptions:
- endpoint: "[email protected]"
protocol: "email"
- endpoint: "my_mobile_number"
protocol: "sms"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Dict of sns topic details Returned: always |
|
list of attributes set during this run Returned: always Sample: [] |
|
whether check mode was on Returned: always Sample: false |
|
Delivery policy for the SNS topic Returned: when topic is owned by this AWS account Sample: “{\”http\”:{\”defaultHealthyRetryPolicy\”:{\”minDelayTarget\”:20,\”maxDelayTarget\”:20,\”numRetries\”:3,\”numMaxDelayRetries\”:0, \”numNoDelayRetries\”:0,\”numMinDelayRetries\”:0,\”backoffFunction\”:\”linear\”},\”disableSubscriptionOverrides\”:false}}\n” |
|
Display name for SNS topic Returned: when topic is owned by this AWS account Sample: “My topic name” |
|
Topic name Returned: always Sample: “ansible-test-dummy-topic” |
|
AWS account that owns the topic Returned: when topic is owned by this AWS account Sample: “111111111111” |
|
Policy for the SNS topic Returned: when topic is owned by this AWS account Sample: “{\”Version\”:\”2012-10-17\”,\”Id\”:\”SomePolicyId\”,\”Statement\”:[{\”Sid\”:\”ANewSid\”,\”Effect\”:\”Allow\”,\”Principal\”:{\”AWS\”:\”arn:aws:iam::111111111111:root\”}, \”Action\”:\”sns:Subscribe\”,\”Resource\”:\”arn:aws:sns:us-east-2:111111111111:ansible-test-dummy-topic\”,\”Condition\”:{\”StringEquals\”:{\”sns:Protocol\”:\”email\”}}}]}\n” |
|
whether the topic is present or absent Returned: always Sample: “present” |
|
List of subscribers to the topic in this AWS account Returned: always Sample: [] |
|
List of subscribers added in this run Returned: always Sample: [] |
|
Count of confirmed subscriptions Returned: when topic is owned by this AWS account Sample: “0” |
|
Count of deleted subscriptions Returned: when topic is owned by this AWS account Sample: “0” |
|
List of existing subscriptions Returned: always Sample: [] |
|
List of new subscriptions Returned: always Sample: [] |
|
Count of pending subscriptions Returned: when topic is owned by this AWS account Sample: “0” |
|
Whether or not purge_subscriptions was set Returned: always Sample: true |
|
ARN of the SNS topic (equivalent to sns_arn) Returned: when topic is owned by this AWS account Sample: “arn:aws:sns:us-east-2:111111111111:ansible-test-dummy-topic” |
|
Whether the topic was created Returned: always Sample: false |
|
Whether the topic was deleted Returned: always Sample: false |
|
The ARN of the topic you are modifying Returned: always Sample: “arn:aws:sns:us-east-2:111111111111:my_topic_name” |
Authors
Joel Thompson (@joelthompson)
Fernando Jose Pando (@nand0p)
Will Thames (@willthames)