Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.
When resources change state, they automatically send Amazon CloudWatch events into an event stream. Create rules that match selected events in the stream and route them to targets to take action. Use rules to also take action on a pre-determined schedule.
Use the Amazon CloudWatch Events integration in Jira Service Management to forward Amazon CloudWatch Events notifications to Jira Service Management. Jira Service Management determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iOS & Android push notifications, and escalates alerts until they are acknowledged or closed.
When a state changes in your AWS resources, an alert is automatically created in Jira Service Management through the integration.
Amazon CloudWatch Events is an API-based integration. Setting it up involves the following steps:
Add an Amazon CloudWatch Events integration in Jira Service Management
Configure the integration in Amazon CloudWatch Events
Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.
Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.
To add a CloudWatch Events integration in Jira Service Management, complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “Amazon CloudWatch Events”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the endpoint URL generated for your account.
You will use this URL while configuring the integration in Amazon CloudWatch Events later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
To configure the integration in Amazon CloudWatch Events, complete the following steps:
Go to the SNS dashboard and select Create Topic.
Fill in the required fields in the dialog and select Create topic.
On the Topic details page, select Create subscription.
Select HTTPS for Protocol.
Paste the endpoint URL previously copied into Endpoint.
Select Create subscription.
If the configuration is successful, a confirmation alert is created in Jira Service Management.
Go to the CloudWatch dashboard.
From the left side menu, select Events > Rules.
Select Create rule.
Select an Event Source to get notifications from.
Add the SNS topic previously created as the target.
Select Configure details.
Enter a name for the rule and select Create rule.
(in JSON format)
1
2
3
4
5
6
7
8
9
10
11
{
"Type": "Notification",
"MessageId": "96d4c7c2-999e-57ab-aade-95f2f518987f",
"TopicArn": "arn:aws:sns:us-west-2:450xxxxxxx:test",
"Message": "{\"version\":\"0\",\"id\":\"3ee38987-e0ce-29f1-91a1-32704265286f\",\"detail-type\":\"EC2 Instance State-change Notification\",\"source\":\"aws.ec2\",\"account\":\"4500xxxxxx\",\"time\":\"2017-09-11T10:49:41Z\",\"region\":\"us-west-2\",\"resources\":[\"arn:aws:ec2:us-west-2:4500xxxxxxx:instance/i-04d6ebefdb7xxxx\"],\"detail\":{\"instance-id\":\"i-04xxxxxx\",\"state\":\"terminated\"}}",
"Timestamp": "2017-09-11T10:49:42.630Z",
"SignatureVersion": "1",
"Signature": "Iv8exxxx/DIfFd0eZ4eyo4vjrb/wEEoNji9S3xGQtpo1E9gXyMM8spmrULq20o25+OKXwZd5tRue7D69olvdcUdqRAN/bBfaHHq6tKVxnVnidgNq1VknAMeQRgd8qwVW1gARXTdO2z9AeDrOCH/ozEgNK3vwoFsDDxwKFxlFa9aioxxOu0uGlyuUpIb2rOaOwSo0aloE14XY9tgWrGlAxp+YwyHJbwXj36oAAU0GZOZV5C4TMhnRIdBnI9Yxxxxxxxx/tj6+gRnP4KeldOFHpaBGdw3/hOMdq9vA8yH934sA==",
"SigningCertURL": "https://sns.us-west-2.amazonaws.com/SimpleNotificationService-433026a4050d2xxxxxxxxxx.pem",
"UnsubscribeURL": "https://sns.us-west-2.amazonaws.com/?Action=Unsubscribe&SubscriptionArn=arn:aws:sns:us-west-2:4500xxxxxxx:test:5c91fe30-xxxxx-4627-a7f7-xxxxxxx"
}
Jira Service Management parses the payload as follows:
(in JSON format)
1
2
3
4
5
6
7
8
9
{
"id":"5c1f7731-23e0-0e90-124f-38ddb2811b49",
"detail-type":"EC2 Instance State-change Notification",
"source":"aws.ec2",
"account":"4500xxxxxxx",
"time":"2017-09-11T10:03:33Z",
"region":"us-west-2",
"detail":{"instance-id":"i-04d6ebxxxxxxxxx","state":"stopping"}}"
}
Was this helpful?