Page Comparison

...

Overview

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 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/jiraservicemanagement.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 such as SNS, SQS, Lambda, Kinesis, CloudWatch, and SSM.

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

To add an Amazon EventBridge integration in Jira Service Management:

1. Go to your team’s operations page.

2. On the left navigation panel, select Integrations and then Add integration.

3. Run a search and select “Amazon EventBridge”.

4. On the next screen, enter aname for the integration.

5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

6. Select Continue.
   The integration is saved at this point.

7. 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.

8. 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.

9. Save the changes.

10. 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 , a partner event source will be created in Amazon EventBridge.

1. Go to AWS EventBridge partner event sources page and pick the newly created event source with the name aws.partner/jiraservicemanagement.com/{{integrationId}}, then click Associate with event bus and follow through setup dialog. After this step partner event source setup is done.

2. To consume events in the partner event source, go to AWS EventBridge rule creation page , fill in your rule and description (optional). To listen to 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 option in Service name section.

3. In Select event bus section select Custom or partner event bus option and select the newly created event source. In Select targets section configure target(s) you want to route event payloads to, in this example we will route payloads to an AWS Lambda function. Optionally add tags to your rule, then select 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/jiraservicemanagement.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
    }
}