By using AWS re:Post, you agree to the Terms of Use
/Domain and Email Address Identity have different Feedback notification settings for different SNS topics but both of them go to the same topic as what is set for the domain identity/

Domain and Email Address Identity have different Feedback notification settings for different SNS topics but both of them go to the same topic as what is set for the domain identity


I have 2 verified identities:

The reason for both is that I want email from to go to one SNS topic (Account Topic) while everything else in that domain goes to a different SNS topic (Domain Topic). That is the idea but the email sent from has its notifications go to the same SNS topic as

I know this should work because it is listed here

Verified email address identity settings override verified domain identity settings.

Note: I am not in the sandbox


  • Verified that each identity has different SNS Feedback notifications
  • Created a as a verified email address identity and set Bonce, Complaint, and Delivery notifications to go to the same SNS topic as (Account Topic) - this worked as expected with notifications going to the correct SNS topic (Account Topic)
  • Made sure that the character cases match for when sending email since email identities are case-sensitive
  • Deleted the Email address identity (, waiting 15 minutes, and then creating a new identity with the same address - the identity was immediately verified and still had the previous Bonce, Complaint, and Delivery settings as before which makes me think this account was never deleted off of AWS in the backend.
1 Answers
Accepted Answer

This is now fixed. I had to purchase the AWS support for $29 for this answer but it was worth it because it is now fixed so hopefully I save you from also having to pay for support.

For those of you that happen to stumble on this post and have the same issue, here is the fix.

The reason was due to the difference between how v2 and v1 SES APIs verify the email identity.

Generally, with SES if the domain at large is verified it is not required to verify a specific email address within that domain. That is unless you want changes to the configuration as to how certain email addresses should operate. However, to make use of email address identity while sending email using SES SMTP, you need to verify the email address using the v1 API.

In your web console, it might be showing as verified since it is using v2 calls. However, if you check the same using CLI, you will see the status as “Failed or pending”. This is very strange behavior and almost seems like a bug to me, but I do not work at AWS.

You can verify this by running this command: (Replace with your email identity)

aws ses get-identity-verification-attributes --identities ""

And it will show this…

    "VerificationAttributes": {
        "": {
            "VerificationStatus": "Pending"

Which is completely different than what is shown in the


  1. Open the Amazon SES console.
  2. From the AWS Region selector in the navigation bar, select the Region that your identity is in.
  3. From the list of Verified identities, select the email identity. Then, choose Delete
  4. Choose Create Identity. Then, re-enter the email identity details
  5. Then run this CLI command (Replace with your email identity)
aws ses verify-email-identity --email-address  

Note: This command adds an email address to the list of identities for your Amazon SES account in the current AWS region and attempts to verify it. As a result of executing this operation, a verification email is sent to the specified address.

  1. Click that verification link received in your mailbox for this email identity and verify the email address on AWS console as well as AWS CLI by running the verification attribute command
aws ses get-identity-verification-attributes --identities

The result should look like this...

    "VerificationAttributes": {
        "": {
            "VerificationStatus": "Success"
  1. Once the verification status is "Verified" on the console and shows "Success" on the CLI level, you can test by sending an email for the email identity and verify it is using the correct configuration set on SES.
answered a month 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