Getting Started - AWS Service Management Connector

Getting Started

Before installing the AWS Service Management Connector for Jira Service Management, you need an AWS account and an Atlassian instance with Jira Service Management pre-installed. Verify that you have the necessary permissions in your AWS account and Jira Service Management software.

For a zip file containing Connector add-on code as well as AWS Configuration files, download and extract the AWS Service Management Connector for JSM-Configuration Files.

Note

The Jira Products on AWS Reference Deployment Quick Start is available to use AWS resources for infrastructure required to install Jira Service Management data center version.

AWS prerequisites

  • To use Service Catalog with the Connector, you need an AWS account to configure your AWS portfolios and products. For more information, see Setting Up AWS Service Catalog.

  • To see AWS Config details, configure the service settings to record data for the resource types of interest. We recommend including provisioned products and AWS CloudFormation stacks, in addition to the major resource types your team uses. For more information, see Setting Up AWS Config with the Console.

  • To use AWS Systems Manager Automation with the Connector, you don't need AWS-side setup. A number of automation documents are available from AWS as standard. If you want to use additional automation documents, they are available in the Connector. For more information, see Working with Automation Documents (Playbooks).

  • To use AWS Systems Manager OpsCenter with the Connector, enable OpsCenter in the AWS Systems Manager console. For more information, see Getting Started with OpsCenter. The Connector also enables viewing resources and automation documents (runbooks) associated to OpsItem. For more information to associate resources to OpsItems in AWS OpsCenter, see Working with Related Resources . For more information to associate automation documents to OpsItems in AWS OpsCenter, see Remediating OpsItem issues using Systems Manager automation.

  • To use AWS Security Hub with the Connector, you must enable the service in all Regions and accounts where you want to sync Findings. For more information, see Setting up Security Hub. We recommend you connect Jira Service Management with the primary AWS account for AWS Security Hub. For more information, see Managing master and member accounts.

  • To use AWS Support with the Connector, your account must have a Business or Enterprise Support plan to use support integration.

  • To use AWS Systems Manager Incident Manager with the Connector and allow the Connector to synchronize Incidents for a specific Region, you must enable Incident Manager in that account and Region. For details on the service endpoint, see AWS Systems Manager Incident Manager endpoints and quotas.

Note

AWS Service Management Connector allows AWS Managed Services (AMS) Accelerate users to create Incidents and Service Requests through Jira Service Management. To ensure that your account has the required permissions to create AMS Accelerate support cases, make sure you onboard your account to Accelerate. For more information, see Getting Started with AMS Accelerate.

For each AWS account, the Connector for Jira Service Management also requires API access with Baseline permissions.

Jira Service Management prerequisites

In addition to your AWS account, you need the Jira Service Management software installed on your Atlassian instance before you can install the AWS Service Management Connector add-on. The Jira Service Management administrator needs the admin role to install the AWS Service Management Connector add-on.

Before configuring your AWS connector, ensure you follow Atlassian recommendations for securing your Jira Service Management instances. For more information, see Preventing Security Attacks.

The Connector for Jira Service Management add-on is available to download in the Atlassian Marketplace.