- Newest
- Most votes
- Most comments
It's strongly advised not to use email validation for ACM-issued public certificates. You should choose the DNS validation method and add the CNAME record(s) that ACM generates in the corresponding public DNS zone. It's explained in more detail in documentation: https://docs.aws.amazon.com/acm/latest/userguide/dns-validation.html
In addition to eliminating all complexities and ambiguities related to email delivery, DNS validation also allows ACM to keep renewing the certificate automatically, without human effort or risk of renewal being missed, for as long as the certificate is associated with some AWS resource and the relevant CNAME record(s) remaining in the public DNS zone.
Email validation is still technically available and supported, and it's reasonably certain that ACM is sending the emails. Delivery failures can be caused by countless different issues, and troubleshooting methods vary heavily by the target email system. In general terms, I'd suggest checking the email trace logs of your email platform if the email arrived, or asking your service provider to do that for you. Since you checked your spam and other folders, it's quite possible that the email platform rejected or redirected the email for some reason.
There are some general troubleshooting tips regarding email validation also in this documentation article: https://docs.aws.amazon.com/acm/latest/userguide/troubleshooting-email-validation.html
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago