AWS cloud formation / diagnosing dead letter queue

Background:

Lets say you have installed the the Senzing AWS cloud formation stack.   You have then written a program to put your data on the SQS queue and records are hitting the dead letter queue rather than being loaded. 

What is happening:

Senzing is rejecting these records due to a configuration issue.  It's likely that the data source code just needs to be added.  You need to find the Senzing stream loader log and see what it says.  Then ssh into the senzing/sshd container and use the G2ConfigTool to add it.

How to find the logs:

Go into your AWS "CloudWatch" console ... https://console.aws.amazon.com/cloudwatch/home

Navigate to the CloudWatch logs section and find your "poc-simple" project name ...

Drill into this log group and locate the stream loader logs ...

You would then click into one or more of these and locate any errors reflected.   You may see things such as this ...

2021-01-21 15:03:31,145 senzing-50010889E G2Engine.addRecord() G2ModuleGenericException: 0027E|Unknown DATA_SOURCE value 'DNB-OWNER'; JSON:

 

Adding required configurations:

Please see the next article in the series about adding configuration in your AWS cloud formation environment ... AWS cloud formation / adding configuration for new data sources