I meant response from other individuals trying to use the service to understand if this one on my side or widespread. I understand what support and development entails. Per this situation, my debug file will be the same as anyone else's that have tried to use AWS-SNS with no avail. Please understand that I have been working exclusively with FreeNAS in a multiple user/ multiple machine stance for some time now so I understand what networking functions need to be in place. I dedicated a week of my time solely on this issue so im fairly confident that this is not a "user error." I have eaten my words before though.... The mere fact that it generates nothing in the log messages is a clear sign to me that the implementation is off somewhere.



I have found a workaround by using AWS-SES instead and the proven email alert method time tested on FreeNAS. It is actually a better route to go in that AWS-SES gives you the ability to create multiple SMTP users/password and manage them through IAM so that a person managing multiple machines can have them go to one location and bounce to an alternate address. It is more secure and SMTP users can be deactivated if necessary in the event of some kind of breach per that user's account.