- Newest
- Most votes
- Most comments
To verify the ErrorOutputPrefix configuration for your Amazon Kinesis Data Firehose delivery stream with an S3 destination, you need to simulate an error condition that will cause Kinesis Data Firehose to fail to deliver the records to the main S3 prefix and instead route them to the error output prefix.
Here are a few ways you can simulate an error condition to test the ErrorOutputPrefix configuration:
Block or Deny Access to the Main S3 Prefix: Temporarily modify the permissions or bucket policy of your S3 destination bucket to deny access to the main prefix where data is normally delivered. This will cause Kinesis Data Firehose to fail to deliver records to the main prefix, triggering the error handling mechanism and routing the failed records to the ErrorOutputPrefix.
Modify the Data Format or Content: Intentionally send malformed or invalid data from your Lambda function to Kinesis Data Firehose. If Kinesis Data Firehose cannot process or parse the data due to the invalid format, it will route the failed records to the ErrorOutputPrefix.
Configure a Data Transformation or Processing Lambda: If you have configured a Lambda function for data transformation or processing with your Kinesis Data Firehose delivery stream, you can intentionally introduce an error or exception in that Lambda function. This will cause the data transformation to fail, and Kinesis Data Firehose will route the failed records to the ErrorOutputPrefix.
After simulating one of these error conditions, you should see new objects or files appearing in your S3 destination bucket under the ErrorOutputPrefix path. You can then verify the content of these files to ensure they contain the records that failed to be delivered to the main prefix.
Relevant content
- asked a year ago
- asked a year ago

Thanks for the response. I have tried using above ways, it does not seem working as expected. In which cases it will insert data using ErrorOutputPrefix.?Is there any other way to verify it.