Identity Verification for Second SES Domain Pending for more than a week - Seeking Advice!

0

Hello fellow forum members,

I hope you're all doing well. I'm currently facing an issue with the identity verification process for my second SES (Amazon Simple Email Service) domain.

It has been a week since I initiated the identity verification, but unfortunately, it is still stuck in a pending state. I followed the necessary steps for verification, such as adding the required DNS records and ensuring accurate information submission. However, despite my efforts, the verification status hasn't progressed.

I have successfully completed identity verification for my first SES domain without any delays. Therefore, I'm a bit perplexed as to why the verification process is taking longer for the second domain.

Has anyone else encountered a similar situation where the identity verification process for a second SES domain has been delayed? Is there any additional action I can take to expedite the verification process? I have thoroughly reviewed all the provided information and everything seems to be in order.

I would greatly appreciate any insights, suggestions, or advice that you may have to help resolve this issue. Thank you in advance for your valuable assistance!

Best regards, Uddin

asked 8 months ago172 views
2 Answers
0

When you create an SES identity with Domain as an Identity type, you are asked to perform DKIM-based domain verification. To complete this verification, you are asked to copy the generated CNAME records to you domain's DNS provider.

If you create these records there, then verification process does not take much time. Instead, it is completed within few minutes.

The key thing here is to make sure that you have created proper CNAME records in your domain with proper values as shown in the picture below. When creating CNAME, don't include your domain name as that is included by default, just add the first segment till ._domainkey.

Enter image description here

AWS
answered 8 months ago
0

In my experience, even a second domain has never been on hold for a long period of time.
Try redoing the domain verification as described in the following document, or check to see if the correct domain is registered.
https://repost.aws/knowledge-center/ses-domain-stuck-pending-verification

By the way, are the first and second domains in separate host zones?
If they are using the same host zone, it would be a good idea to check for differences in domain verification settings.

profile picture
EXPERT
answered 8 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions