1 回答
- 最新
- 投票最多
- 评论最多
1
I was able to manually add the SES domain identity as the provider with the following cli command...
aws cognito-idp update-user-pool --user-pool-id <id> --email-configuration SourceArn=<arn_for_domain_identity>,ReplyToEmailAddress=no-reply@domain.com,EmailSendingAccount=DEVELOPER,From=no-reply@domain.com,ConfigurationSet=<config_set_name> --profile <profile_name> --auto-verified-attributes email --user-attribute-update-settings AttributesRequireVerificationBeforeUpdate=email
I had to add the --auto-verified-attributes email --user-attribute-update-settings AttributesRequireVerificationBeforeUpdate=email to prevent an error saying that they did not match, despite the fact that describe said they did. Perhaps they are reset as part of setting the email configuration. This command also clears your lambda config if you have any set.
已回答 2 个月前
相关内容
AWS 官方已更新 1 年前- AWS 官方已更新 1 年前
I'm also having this problem. My verified domain was moved out of the sandbox long ago so for me that isn't a factor, my DNS records aren't managed by Route 53 but I can see that all required DNS records are still in place.
The posted answer to manually add the SES domain identity via CLI command fixed it for me too, thanks Jake.