Hello,
My team successfully created a unique email to send to users on verification for a newly signed up Cogntio User in a Cognito User Pool. We had the system working by verifying an email address, "example@example.com". A developer then verified the domain "example.com", and then deleted the example@example.com verification in the hopes of using subdomains in the future.
However, this failed with the message: "Email address not verified for arn:aws:ses:us-east-1-XXXXXXXXX:identity/example@example.com".
Although I have added back the email address into the Ses verified configuration, we are still getting the error message. It is also no longer showing up in the dropdown box for Cognito ID.
This is clearly something getting set wrong because we added the domain, added the email, then deleted the email from the verified email list in US-Va-1. I do not want to pay for support when this is clearly Amazon's internal configuration issue. I've tried creating a new User Pool, but that did not work.
How do I go about resetting this email address so that it is recognized as verified by cognito again? Once again, it is currently verified address in the US-East-1 according to SES and we are unsandboxed at this time, but Cognito can not recognize that the verified address is actually verified.
AWS 공식업데이트됨 일 년 전
Having the same issue but for eu-west-1, I have used this email before so not sure whats going on.
I also am experiencing this. On top of what is said above. If you use boto call to list verified identities, https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ses.html#SES.Client.list_verified_email_addresses, they do not show up in the response list. So they show in the UI as verified, but not via an api call.