Project

General

Profile

Bug #25037

Fix AWS-SNS Alert Service

Added by Devin Kusek over 1 year ago. Updated 12 months ago.

Status:
Resolved
Priority:
Important
Assignee:
Marcelo Araujo
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Here is what I have done:

My configuration:
Region: us-east-2
ARN: arn:sns:us-east-2.......................

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/

slack-consul.png (97.9 KB) slack-consul.png Marcelo Araujo, 07/12/2017 01:29 AM
11740

Associated revisions

Revision 3deb28ea (diff)
Added by Marcelo Araujo over 1 year ago

fix(consul/aws-sns): Add credentials and region to compliance with AWS SDK API requirements. Also fix a typo related with the region name in middlewared. Also the consul notifier expects the AWS entries been into awssns instead of aws-sns.

Tested at region: ap-northeast-1
Test results: Received the alert in two different mailbox as well as via SMS.

Ticket: #25037

Revision 079a2d2e (diff)
Added by Marcelo Araujo over 1 year ago

fix(consul-alerts): We need to restart consul-alerts too.

Ticket: #25037

Revision 5cbc4c6e
Added by Marcelo Araujo over 1 year ago

Merge pull request #233 from freenas/aws-sns

fix(consul/aws-sns): Add credentials and region to compliance with AWS SDK API requirements. Also fix a typo related with the region name in middlewared. Also the consul notifier expects the AWS entries been into awssns instead of aws-sns.

Tested at region: ap-northeast-1
Test results: Received the alert in two different mailbox as well as via SMS.

Ticket: #25037

Revision 6ec06adc (diff)
Added by Marcelo Araujo over 1 year ago

fix(consul/aws-sns): Add credentials and region to compliance with AWS SDK API requirements. Also fix a typo related with the region name in middlewared. Also the consul notifier expects the AWS entries been into awssns instead of aws-sns.

Tested at region: ap-northeast-1
Test results: Received the alert in two different mailbox as well as via SMS.

Ticket: #25037

Revision 25977a81 (diff)
Added by Marcelo Araujo over 1 year ago

fix(consul-alerts): We need to restart consul-alerts too.

Ticket: #25037

History

#1 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to William Grzybowski

#2 Updated by William Grzybowski over 1 year ago

  • Assignee changed from William Grzybowski to Marcelo Araujo

#3 Updated by Devin Kusek over 1 year ago

There was also someone that stated that it would be very useful to "specify the AWS access key ID or AWS secret access key." I second this.

#4 Updated by Devin Kusek over 1 year ago

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?

#5 Updated by Marcelo Araujo over 1 year ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Important
  • Target version set to 11.1

#6 Updated by Marcelo Araujo over 1 year ago

11740

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.

#7 Updated by Marcelo Araujo over 1 year ago

  • Status changed from Screened to Needs Developer Review
  • Assignee changed from Marcelo Araujo to William Grzybowski

Hi William, it should land on 11.1-RELEASE, please review it.

#8 Updated by William Grzybowski over 1 year ago

  • Status changed from Needs Developer Review to Screened
  • Assignee changed from William Grzybowski to Marcelo Araujo

Requested changes in the PR.

#9 Updated by Marcelo Araujo over 1 year 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?

Br,

#10 Updated by William Grzybowski over 1 year ago

  • Status changed from Needs Developer Review to Reviewed by Developer
  • Assignee changed from William Grzybowski to Marcelo Araujo

#11 Updated by Dru Lavigne over 1 year ago

  • Subject changed from AWS-SNS Alert Service Broken to Fix AWS-SNS Alert Service

#12 Updated by Dru Lavigne about 1 year ago

  • Status changed from Reviewed by Developer to Ready For Release
  • Target version changed from 11.1 to 11.1-BETA1

#13 Updated by Dru Lavigne about 1 year ago

  • Status changed from Ready For Release to Resolved

#14 Updated by Nick Wolff about 1 year ago

  • QA Status Test Fails FreeNAS added
  • QA Status deleted (Not Tested)

Tests Failing.

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.

#15 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.1-BETA1 to 11.1

Marcelo: please work with QA to resolve this.

#16 Updated by Dru Lavigne about 1 year ago

  • Status changed from Resolved to 46

#17 Updated by Dru Lavigne 12 months ago

  • Status changed from 46 to Fix In Progress

#18 Updated by Marcelo Araujo 12 months ago

  • Status changed from Fix In Progress to Ready For Release

#19 Updated by Nick Wolff 12 months ago

  • Needs QA changed from Yes to No
  • QA Status Test Passes FreeNAS added
  • QA Status deleted (Test Fails FreeNAS)

Test Passes

#20 Updated by Dru Lavigne 12 months ago

  • Status changed from Ready For Release to Resolved

Also available in: Atom PDF