I received a notification from AWS saying "Amazon SES failed to publish data to Kinesis Firehose". What does this mean, and how do I fix it?

Here are some reasons why Amazon SES might not publish data to Amazon Kinesis Firehose:

The delivery stream was deleted

SES is attempting to deliver to a Firehose delivery stream that no longer exists.

Check the Kinesis Firehose console to ensure that your delivery stream is still active. If your delivery stream was deleted, create a new one by following the instructions at Creating an Amazon Kinesis Firehose Delivery Stream.

Amazon SES no longer has the required permissions to publish to the delivery stream

Make sure that the IAM role associated with your Firehose delivery stream has a permissions policy and trust policy that allows SES to publish to it.

For an example of a permissions policy and trust policy that will allow SES to publish to Firehose, see Giving Amazon SES Permission to Publish to Your Firehose Delivery Stream. For general information about configuring IAM roles, see Modifying a Role.

Note: After you identify and fix the issue, be sure to re-enable your SES event destination. SES automatically disables event destinations after a failure in order to prevent future failed attempts.

SES, Kinesis Firehose, delivery stream, publish


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2017-03-15