In this video, you’ll see how to integrate AWS Systems Manager OpsCenter into Jira Service Management (JSM).
With this capability, JSM users can track operational items related to AWS resources while using their existing Jira workflows.
Users can also execute Systems Manager Automation runbooks to remediate known issues right from JSM.
To get started, let’s quickly review OpsCenter in AWS Systems Manager.
OpsCenter provides a central location where operations engineers and IT professionals can view, investigate,
and resolve operational work items (OpsItems) related to AWS resources.
You can select an item to get more details, or even perform automation executions.
Now let’s switch to JSM and review how you can incorporate these same OpsItems directly into an existing service desk.
In the Administration settings, open the Manage apps screen.
For this example, the AWS Service Management Connector for Jira Service Management has already been installed and configured.
For information on how to do this, please refer to the AWS documentation or topic-specific video in this series.
Here’s the AWS account that was linked to JSM.
Let’s review the Connector settings.
Although the Connector is already configured and the OpsCenter feature is enabled,
no Jira projects have been mapped to our AWS account, which is required for synchronization to occur.
Let’s take care of that now.
All we need to do is associate the project with the AWS account and save the changes.
Now we’ll perform a synchronization to pipe over the data.
This synchronization also happens automatically at predefined intervals.
Let’s return to the service desk.
The same OpsItems you saw in OpsCenter are now accessible from here.
You can drill into an item in the queue to review its details and even edit the issue.
You can also perform standard JSM operations, such as assigning the issue.
You can also change the status of the issue.
For some issues, you can even drill down to see additional technical details that have been synchronized from AWS, such as data from AWS Config.
Associated AWS runbooks that have already been defined in OpsCenter are also accessible from here.
You can show all runbooks, if the one you are looking for is not displayed.
With the right permissions, you can execute runbooks directly from JSM.
As an example, let’s execute this runbook to start an EC2 instance.
We just need to pass the Instance ID as a parameter.
The notification shows that the automation has been successfully created.
Now we can flag this issue as resolved.
You can also create OpsItems right from JSM, and they will automatically synchronize back to OpsCenter in AWS.
Let’s return to OpsCenter to confirm that the issue is reflected there.
The OpsItem that was created in JSM has been synchronized through the Connector.
Let’s look at resolved OpsItems.
This is the OpsItem that we marked resolved within JSM.
As you can see, with OpsCenter integration into JSM, Jira users can view, investigate, and resolve OpsItems without having to log into AWS.
You've just seen how to integrate AWS Systems Manager OpsCenter into Jira Service Management (JSM).
You can learn more about this topic in the description and links for this video.
Thanks for watching. Now it’s your turn to try.