I'm looking for a way to automatically link AWS Health alerts to new JIRA tickets for our projects. The goal is to avoid creating duplicate tickets since forwarding emails to our JIRA Service Management project email would likely lead to duplicates. Does anyone have suggestions or best practices for setting this up?
2 Answers
Yeah, definitely steer clear of forwarding emails to JIRA. That can turn into a duplicate ticket nightmare that no one wants to face. Ideally, you'd use AWS EventBridge. Set it up to listen for the AWS Health events you're interested in, and then configure it to send the event data directly to your JIRA API endpoint for creating new issues. Since the event data is structured as JSON, it contains unique identifiers, which you can use to check if a related ticket already exists. This should help with keeping everything organized!
We faced similar issues at work, but went with a straightforward method: Set up a CRON job that checks the Health Dashboard daily, then uses a Lambda function to send notifications to JIRA. The Lambda checks against a DynamoDB table for any new entries, and if it finds any, it triggers an API call to JIRA. Not the fanciest solution, but it gets the job done!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures