Shameless plug -- for people who want to automate this process, a guide that does this with Pulumi and SES in particular (while leaving space for an cloud-exter

Shameless plug -- for people who want to automate this process, a guide that does this with Pulumi and SES in particular (while leaving space for an cloud-external self-hosted SMTP server): https://vadosware.io/post/setting-up-ses-with-pulumi https://vadosware.io/post/setting-up-ses-with-pulumi I'm a big fan of Pulumi and have used this setup for 2 projects so far (it's part of a bigger framework of repeatable infra for SaaS projects I've been hacking on), and I can say it definitely delivers (pun intended). Code in the blog post might be a little stale -- I've just put an update in there to note that SES recently changed to using DKIM records primarily for domain verification, so the aws.ses.DomainIdentityVerification (Pulumi object) is no longer needed. One of the nice things about using Pulumi to do this is that since AWS allows you to use pre-made DKIM keys now, I read one right off disk (look into how to make a dkim key[0], it's interesting), and use it for both my personal email (I run maddy[1]) tied to the domain and SES. [0]: https://lxadm.com/Generating_DKIM_key_with_openssl https://lxadm.com/Generating_DKIM_key_with_openssl [1]: https://maddy.email https://maddy.email