An invalid or out-of-range value was supplied for the input parameter.

[mayurbhagia]

After running the CFN template and when we goto Amazon SES under Verified Identities Click on Email and Notifications, it is giving error An invalid or out-of-range value was supplied for the input parameter when we select the SNS topic created by CFN

[tykocuw]

I'm also receiving this error for a topic that was previously configured and working for feedback notifications. Any updates on this?

[bgiorgini]

Which region? Is the SNS topic created in the same region as SES is running? Any more details you can provide?

[tykocuw]

The region is us-west-2. The topic and SES are in the same region. The topic was working just fine until I randomly received an email from AWS:

"An error occurred while trying to publish a notification of type "Bounce" to Amazon SNS topic "arn:aws:sns:us-west-2:123456789:my-topic-name".
Your Amazon SNS notification configuration for notification type "Bounce" with identity "my-email@random.com" has been removed and forwarding of feedback by email has been re-enabled."

I have a support case open but this is really odd since it was configured and working just fine. Now when I try to reconfigure the bounce notifications I get the following error:

An invalid or out-of-range value was supplied for the input parameter.
SNS topic arn:aws:sns:us-west-2:123456789:my-topic-name is invalid.

[schabe77]

To other users who found this page via a search engine:
I had the exact same problem: I received a mail, that the topic was disconnected and wasn't able to reconnect it anymore. The cause of the problem was the SNS topic was encrypted with the AWS managed SNS-KMS key. Unfortunately SES doesn't support AWS managed keys. That's why I couldn't connect the topic as a notification target.
When I connected the topic the first time, it wasn't encrypted. I changed it, which didn't affect the connection, but when SES tried to send the first notification, it found that it couldn't access it and removed the connection.

[dyferx]

SNS KMS encryption is supported by SES. You just need to grant the necessary KMS permissions to the SES service.
https://repost.aws/knowledge-center/ses-resolve-sns-bounce-notifications

[TyKommel]

This is still not working, even with a KMS CMK and the proper permissions as supplied by the docs.

[digitalfirehouse]

Same issue

[TyKommel]

I got this working, @dyferx is correct, it's all in the KMS permissions. By adding a condition to by KMS CMK policy with StringLIke matching the source account and also ArnLike to match AWS:SourceArn for the identities you are using to send the feedback for.

[TyKommel]

Stopped working again