Fix AWS-SNS Alert Service
Here is what I have done:
The protocol on the AWS side is through "email".
Thats all correct?
Is there anything else in networking that should be checked? I can send messages directly from AWS-SNS to the endpoint so I dont think they are being blocked. I also messed around with the newest nightly that has the ability to send "Test Alerts" and that was also unsuccessful. I went one more and set an additional region, us-east-1, but that had the same outcome. Any help on this is greatly appreciated. Unless others are having problems, I must be missing something small.
EDIT: I have also set up SQS in Amazon and Email-JSON. I can send messages within the SQS service no problem and I can send the email-json messages to the email endpoint. Again, nothing seems to be wrong with the functionality. Is there any additional settings on the FreeNAS side for this to be functional?
Setting up a dummy "tank" and then removing one or two of the drives in order to trigger an alert. I get nothing on the SNS side. Generating real alerts does nothing to push them through the SNS Alert Service.
In all of these tests, I paid close attention to /var/log/messages and got no response.
I also tested this in the Nightlies that have the added "Send Fake Alert." The GUI responds that the fake alert is sent. Again, nothing is generated in the logs to support that and no alerts were sent to the SNS service that bounces them to a personal email.
On that note, I am able to post to the topic to receive said topic at my email destination. I can confirm the SNS relay to personal email account is not blocked and functional.
Forum Link associated with this bug: https://forums.freenas.org/index.php?threads/aws-sns-configuration.55807/
#6 Updated by Marcelo Araujo over 3 years ago
Devin Kusek wrote:
Wanted to update this and inform the bug report that this issue might be more widespread as another user reported that "Slack" was also not working. Is there any update as to when this might be tested and if a known resolution date was in the works?
Seems there is a problem with consul-alerts and AWS-SNS, I'm still investigating it, however with Slack there is no problem as you can see with the screenshot attached.
#9 Updated by Marcelo Araujo over 3 years ago
- Status changed from Screened to Needs Developer Review
- Assignee changed from Marcelo Araujo to William Grzybowski
Address the issues spotted in the pre-review: Remove redundant file.close() as well as the name CONSUL in the logger().
Thanks for the review. Could you double check it again?
#14 Updated by Nick Wolff about 3 years ago
- QA Status Test Fails FreeNAS added
- QA Status deleted (
Not seeing any logging of success/failures.
Would appreciate review of testing procedure which may have a misconfiguration or other issues.
I'm not seeing any traffic leaving the box via outgoing port 80 or 443 when I trigger real or fake alert. This suggest the sns api attempt isn't happening.
#18 Updated by Marcelo Araujo about 3 years ago
- Status changed from Fix In Progress to Ready For Release
Reviewed by kris already!