community.aws.ses_identity module – Manages SES email and domain identity
Note
This module is part of the community.aws collection (version 9.0.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
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.aws.ses_identity
.
New in community.aws 1.0.0
Synopsis
This module allows the user to manage verified email and domain identity for SES.
This covers verifying and removing identities as well as setting up complaint, bounce and delivery notification settings.
Prior to release 5.0.0 this module was called
community.aws.aws_ses_identity
. The usage did not change.
Aliases: aws_ses_identity
Requirements
The below requirements are needed on the host that executes this module.
python >= 3.6
boto3 >= 1.28.0
botocore >= 1.31.0
Parameters
Parameter |
Comments |
---|---|
AWS access key ID. See the AWS documentation for more information about access tokens https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys. The The aws_access_key and profile options are mutually exclusive. The aws_access_key_id alias was added in release 5.1.0 for consistency with the AWS botocore SDK. The ec2_access_key alias has been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
The location of a CA Bundle to use when validating SSL certificates. The |
|
A dictionary to modify the botocore configuration. Parameters can be found in the AWS documentation https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html#botocore.config.Config. |
|
Setup the SNS topic used to report bounce notifications. If omitted, bounce notifications will not be delivered to a SNS topic. If bounce notifications are not delivered to a SNS topic, feedback_forwarding must be enabled. |
|
Whether or not to include headers when delivering to the SNS topic. If topic is not specified this will have no impact, but the SES setting is updated even if there is no topic. Choices:
|
|
The ARN of the topic to send notifications to. If omitted, notifications will not be delivered to a SNS topic. |
|
Setup the SNS topic used to report complaint notifications. If omitted, complaint notifications will not be delivered to a SNS topic. If complaint notifications are not delivered to a SNS topic, feedback_forwarding must be enabled. |
|
Whether or not to include headers when delivering to the SNS topic. If topic is not specified this will have no impact, but the SES setting is updated even if there is no topic. Choices:
|
|
The ARN of the topic to send notifications to. If omitted, notifications will not be delivered to a SNS topic. |
|
Use a The Choices:
|
|
Setup the SNS topic used to report delivery notifications. If omitted, delivery notifications will not be delivered to a SNS topic. |
|
Whether or not to include headers when delivering to the SNS topic. If topic is not specified this will have no impact, but the SES setting is updated even if there is no topic. Choices:
|
|
The ARN of the topic to send notifications to. If omitted, notifications will not be delivered to a SNS topic. |
|
URL to connect to instead of the default AWS endpoints. While this can be used to connection to other AWS-compatible services the amazon.aws and community.aws collections are only tested against AWS. The The ec2_url and s3_url aliases have been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
Whether or not to enable feedback forwarding. This can only be false if both bounce_notifications and complaint_notifications specify SNS topics. Choices:
|
|
This is the email address or domain to verify / delete. If this contains an ‘@’ then it will be considered an email. Otherwise it will be considered a domain. |
|
A named AWS profile to use for authentication. See the AWS documentation for more information about named profiles https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html. The The profile option is mutually exclusive with the aws_access_key, aws_secret_key and security_token options. |
|
The AWS region to use. For global services such as IAM, Route53 and CloudFront, region is ignored. The See the Amazon AWS documentation for more information http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region. The Support for the |
|
AWS secret access key. See the AWS documentation for more information about access tokens https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys. The The secret_key and profile options are mutually exclusive. The aws_secret_access_key alias was added in release 5.1.0 for consistency with the AWS botocore SDK. The ec2_secret_key alias has been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
AWS STS session token for use with temporary credentials. See the AWS documentation for more information about access tokens https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys. The The security_token and profile options are mutually exclusive. Aliases aws_session_token and session_token were added in release 3.2.0, with the parameter being renamed from security_token to session_token in release 6.0.0. The security_token, aws_security_token, and access_token aliases have been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
Whether to create(or update) or delete the identity. Choices:
|
|
When set to Setting validate_certs=false is strongly discouraged, as an alternative, consider setting aws_ca_bundle instead. Choices:
|
Notes
Note
Caution: For modules, environment variables and configuration files are read from the Ansible ‘host’ context and not the ‘controller’ context. As such, files may need to be explicitly copied to the ‘host’. For lookup and connection plugins, environment variables and configuration files are read from the Ansible ‘controller’ context and not the ‘host’ context.
The AWS SDK (boto3) that Ansible uses may also read defaults for credentials and other settings, such as the region, from its configuration files in the Ansible ‘host’ context (typically
~/.aws/credentials
). See https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html for more information.
Examples
# Note: These examples do not set authentication details, see the AWS Guide for details.
- name: Ensure example@example.com email identity exists
community.aws.ses_identity:
identity: example@example.com
state: present
- name: Delete example@example.com email identity
community.aws.ses_identity:
email: example@example.com
state: absent
- name: Ensure example.com domain identity exists
community.aws.ses_identity:
identity: example.com
state: present
# Create an SNS topic and send bounce and complaint notifications to it
# instead of emailing the identity owner
- name: Ensure complaints-topic exists
community.aws.sns_topic:
name: "complaints-topic"
state: present
purge_subscriptions: false
register: topic_info
- name: Deliver feedback to topic instead of owner email
community.aws.ses_identity:
identity: example@example.com
state: present
complaint_notifications:
topic: "{{ topic_info.sns_arn }}"
include_headers: true
bounce_notifications:
topic: "{{ topic_info.sns_arn }}"
include_headers: false
feedback_forwarding: false
# Create an SNS topic for delivery notifications and leave complaints
# Being forwarded to the identity owner email
- name: Ensure delivery-notifications-topic exists
community.aws.sns_topic:
name: "delivery-notifications-topic"
state: present
purge_subscriptions: false
register: topic_info
- name: Delivery notifications to topic
community.aws.ses_identity:
identity: example@example.com
state: present
delivery_notifications:
topic: "{{ topic_info.sns_arn }}"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The identity being modified. Returned: success Sample: |
|
The arn of the identity being modified. Returned: success Sample: |
|
The notification setup for the identity. Returned: success Sample: |
|
The ARN of the topic bounce notifications are delivered to. Omitted if bounce notifications are not delivered to a topic. Returned: success |
|
The ARN of the topic complaint notifications are delivered to. Omitted if complaint notifications are not delivered to a topic. Returned: success |
|
The ARN of the topic delivery notifications are delivered to. Omitted if delivery notifications are not delivered to a topic. Returned: success |
|
Whether or not feedback forwarding is enabled. Returned: success |
|
Whether or not headers are included in messages delivered to the bounce topic. Returned: success |
|
Whether or not headers are included in messages delivered to the complaint topic. Returned: success |
|
Whether or not headers are included in messages delivered to the delivery topic. Returned: success |
|
The verification information for the identity. Returned: success Sample: |
|
The verification status of the identity. Returned: success Sample: |
|
The verification token for a domain identity. Returned: success |