SES stuck at 'pending verification'

I understand your frustration with the SES domain verification process being stuck in "Pending" status. This is a common issue that can occur for several reasons. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. DNS propagation: Use tools like MXToolbox or dig to check if your DKIM CNAME records are resolving globally. If they're not, there might be an issue with DNS propagation.

2. Double-check DNS records: Ensure that the CNAME record names are exactly as specified by Amazon SES. Some DNS providers might automatically append the domain name to records, which can cause issues.

3. Verify no conflicting records: Make sure there are no conflicting DNS records for the same domain or subdomain.

4. Wait the full 72 hours: Sometimes, even though it's rare, it can take up to 72 hours for DNS records to become visible to Amazon SES. If you haven't waited the full 72 hours since your last attempt, it's worth giving it more time.

5. Contact your DNS Provider - Check with your DNS provider to confirm if there are any product specific configurations that might interfere with the SES verification process. Since you're using Cloudflare, try adding the records without the proxy (orange cloud) enabled. Sometimes, Cloudflare's proxy can interfere with DNS verification processes.

If after trying these steps and waiting the full 72 hours the status is still "Pending" or changes to "Failed", you may need to restart the verification process from the beginning. This would involve removing the existing DKIM records and setting up DKIM again in Amazon SES.

If the issue persists, it may be worth contacting AWS Support for further assistance, as they can provide more specific guidance based on your account and domain configuration. https://support.console.aws.amazon.com/support/home#/case/create

Sources
DKIM Verification Stuck in "Pending" for domain | AWS re:Post
AWS SES Custom From Domain DNS resolution issue | AWS re:Post