AWS SES support for email sending configuration

[hashibot]

This issue was originally opened by @ksperling as hashicorp/terraform#11232. It was migrated here as part of the provider split. The original body of the issue is below.

---

#6771 / hashicorp/terraform#5387 added AWS SES support for email receiving functionality.

It would be great if sending functionality could be provisioned via terraform as well, specifically creation of domain and email identities and configuration sets.

There are a number of up-votes for this on hashicorp/terraform#6771 (comment) but since that's a closed issue I thought it's better to open a separate one.

[synchrone]

I believe this is now implemented, except for DKIM records retrieval (tracked as #1347)

[ghost]

@synchrone, how is this implement? I mean, I don't see any aws_ses_email_identity in the documentation.

[synchrone]

Ah, you want to add the identities with terraform. I overlooked that one.

[ghost]

double thinking it, is not a good idea... there's no advantage at all, you still have to verify that the email exists and if other applications use the same identity ([email protected]) it would crash, as the record already exists.

[davidbegin]

I have a use case, where we have Terraform handling multiple AWS Accounts for different environments, and would like a consistent way to populate SES with Email Address Identities.

They will still need to be verified, but it is nice when we are provisioning a new environment,
or adding a new employee who needs to be verified in all AWS accounts.

[tdmalone]

This appears to be possible through the AWS CLI: https://docs.aws.amazon.com/cli/latest/reference/ses/verify-email-identity.html

And through the Go SDK: https://docs.aws.amazon.com/sdk-for-go/api/service/ses/#SES.VerifyEmailIdentity

---

And for listing identities: https://docs.aws.amazon.com/sdk-for-go/api/service/ses/#SES.ListIdentities

[tdmalone]

Another thing to think about would be what happens when you try to re-add an identity that already exists. It appears this doesn't fail, but instead generates an e-mail notification to validate the user again.

Also, when listing current identities, it doesn't appear possible (at a quick glance) to see which ones are pending or verified.

[ezyang]

Just ran into this problem just now! I guess the answer for now is to populate this ourselves.

[nywilken]

The aws_ses_email_identity resource has been merged and will be released with version 2.11.0 of the Terraform AWS provider, later this week.

[bflad]

The new aws_ses_email_identity resource has been released in version 2.11.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!