Multiple SES Domain Verifications in one account
Greetings from Vancouver Island,
I have a successful domain (domain1.com) verified and out of the SES Sandbox. Is it possible to have a second domain set up within the same AWS Account/SES Instance. I've gone through the steps to verify the second domain (domain2.com), verified the DKIM entries in Route53, all of this within the same account. The SES process to verify a domain, put the CNAME records into the hosted zone for domain2 but the verification pending has been there for two days. Is there a limit or process step I've missed?
Thanks in advance.
- Newest
- Most votes
- Most comments
Please note that verifying domain ownership can take up to 72 hours due to DNS propagation. As soon as AWS detects all the required DKIM records, your domain's identity status should change to 'Verified'. Make sure to double-check the DKIM records in your Route53 zone.
What AWS regions are you using? Please note the following (from the documentation):
Not all AWS regions use the default SES DKIM domain, dkim.amazonses.com—to see if your region uses a region specific DKIM domain, check the DKIM Domains table in the AWS General Reference.
If you're still experiencing issues, please contact AWS Support.
Relevant content
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated a month ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
Thanks for the quick reply. As I test, I verified another domain that I have control over and within 2 minutes is got verified precisely as it is supposed to. I'm in ca-central-1 and now have two domains verified, out of the sandbox, etc. What I can't figure out is one this one silly domain stays in pending mode even when SES does successfully add the CNAME records to the hosted zone. I hope I can get some support from AWS as there is some weird thing I'm missing or messed up with respect to this one domain. Thanks again.
If this is a production issue, please raise a support case. re:Post is not an official support channel; everyone here operates on "best efforts". We (even AWS staff) have no visibility into your environment; but the support team does - hence why raising a support case is the best path forward.