Integrate with Amazon EventBridge

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.

You can set up routing rules to determine where to send your data to build application architectures that react in real time to all of your data sources. Amazon EventBridge makes it easy to build event-driven applications because it takes care of event ingestion and delivery, security, authorization, and error handling for you.

What does the integration offer?

Use Jira Service Management's Amazon EventBridge Integration to forward Jira Service Management alert events to Amazon EventBridge. When the integration is created in Jira Service Management, an event source will be created with the name aws.partner/opsgenie.com/{{integrationId}} automatically.

How does the integration work?

Depending on the rule attached to the event source, the alert events can be forwarded to many different AWS services like SNS, SQS, Lambda, Kinesis, CloudWatch, SSM etc..

Set up the integration

Amazon EventBridge is an outgoing integration. Setting it up involves the following steps:

Add an Amazon EventBridge integration in Jira Service Management
Configure the integration in Amazon EventBridge

Add an Amazon EventBridge integration

If you're using the Free or Standard plan in Jira Service Management, you can only add this integration from your team’s operations page. To access the feature through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be on Premium or Enterprise plan.

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 an Amazon EventBridge 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 EventBridge”.
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 API key.
You will use this key while configuring the integration in Amazon EventBridge later.
Enter values for the following parameters to set up the outgoing authentication:
- Amazon AWS Account ID: The 12-digit number that uniquely identifies your AWS account.
- Region: The AWS region where the partner event source should be created.
Save the changes.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Amazon EventBridge

After creating an integration through Jira Service Management, a partner event source will be created in Amazon EventBridge.

Go to AWS EventBridge partner event sources page and pick the newly created event source with the name aws.partner/opsgenie.com/{{integrationId}}, then click Associate with event bus and follow through setup dialog. After this step Jira Service Management partner event source setup is done.
To consume events in the Jira Service Management partner event source, go to AWS EventBridge rule creation page, fill in your rule Jira Service Management and description (optional). To listen to Jira Service Management events, select Event pattern option in Define pattern section and select Pre-defined pattern by service option in Event matching pattern section, then select Service partners option in Service provider section and find the Atlassian - Opsgenie option in Service name section.
In Select event bus section select Custom or partner event bus option and select the newly created Jira Service Management event source. In Select targets section configure target(s) you want to route Jira Service Management event payloads to, in this example we will route payloads to an AWS Lambda function. Optionally add tags to your rule, then click Create.

Sample event payload sent to Amazon EventBridge event bus

JSON

{
    "version": "0",
    "id": "c5f44bbb-34de-133d-eaff-5f52ff5ad720",
    "detail-type": "Create",
    "source": "aws.partner/jsm.com/1b8db399-7dc4-4f40-85fa-0fde193085c9",
    "account": "123456789012",
    "time": "2019-12-04T13:05:06Z",
    "region": "us-west-2",
    "resources": [],
    "detail": {
        "alertId": "66d9ff87-b253-442c-9d4d-5c2c539f9a31-1575464706692",
        "message": "Sample alert message!",
        "tags": [
            "tag1",
            "tag2"
        ],
        "tinyId": "318",
        "source": "sample.email@gmail.com",
        "entity": "entity1",
        "alias": "alias1",
        "createdAt": 1575464706692,
        "updatedAt": 1575464707610000000,
        "username": "sample.email@gmail.com",
        "userId": "d047b539-a9a8-4475-91f2-30b7fb25a474",
        "userFullName": "John Doe",
        "description": "Sample alert description.",
        "team": "Engineering Team A",
        "responders": [
            {
                "id": "df01caee-345c-4f85-a94f-5b1a4cdfc7f8",
                "type": "team",
                "name": "Engineering Team A"
            }
        ],
        "oldTeams": [],
        "teams": [
            "df01caee-345c-4f85-a94f-5b1a4cdfc7f8"
        ],
        "teamsForVisibility": [
            "df01caee-345c-4f85-a94f-5b1a4cdfc7f8"
        ],
        "actions": [
            "action1",
            "action2"
        ],
        "tag": [
            "tag1",
            "tag2"
        ],
        "details": {
            "property1": "value1"
        },
        "priority": "P3",
        "status": "open",
        "acknowledged": false
    }
}

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Jira Service Management Support