End of support notice: On March 31, 2027, AWS will end support for AWS Service Management Connector. After March 31, 2027, you will no longer be able to access the AWS Service Management Connector console or AWS Service Management Connector resources. For more information, see [AWS Service Management Connector end of support](https://docs.aws.amazon.com/smc/latest/ag/smc-end-of-support.html). 

# Validating AWS Service Management Connector configurationsfor for Jira Service Management


You can validate the AWS Service Management Connector for Jira Service Management installation procedures.

**Topics**
+ [

# Validationg Service Catalog integration
](validate-sc.md)
+ [

# Validating AWS Systems Manager Automation integration
](jsd-sys-automation.md)
+ [

# Validating AWS Systems Manager OpsCenter integration
](opscenter.md)
+ [

# Validating Support integration
](jsd-support-validation.md)
+ [

# Validating AWS Systems Manager Incident Manager integration
](validate-sys-man-incident.md)
+ [

# Validating AWS Security Hub CSPM integration
](jsd-security-hub.md)

# Validationg Service Catalog integration
Service Catalog

 To validate Service Catalog integration, order a Service Catalog product or view provisioned products. 

**To order a Service Catalog product**

1. Log in to your Jira Service Management customer portal as the end user. 

1. In the Jira Service Management customer portal, choose **Request AWS product**.

1. Enter **Summary** details.

1. Open the **AWS product request detail** menu and select a product to provision.

1. Fill in the product request details, including product reference name, parameters, and tags.

1. Choose **Create** to submit the Jira Service Management request and provision the Service Catalog product.

1. After the request processes, a message appears indicating that your request was created. When the product is ready to provision, the end user receives a notification that the product is launching.

**To view provisioned products**

1. In the Jira Service Management customer portal, choose **Requests** in the upper right corner.

1. Choose **My Requests** in the Jira Service Management customer portal view.

1. Choose the AWS product you requested.

1. The AWS product details display, including the status of the product request, product events, and activities.

1. If that Connector feature is available, AWS Config information appears. You can expand **Configuration Items** or **Relationships** to see more information. Related resources can be loaded by continuing to expand them underneath the** Relationships** section.

1. Once the product is in the **Available** status, end users can request post-provision operations actions such as **Request update**, **Request termination**, and **Request self-service actions**. These actions render additional product events and activities within the request. Once the product terminates, the request closes in a resolved state.

# Validating AWS Systems Manager Automation integration
AWS Systems Manager Automation

 To validate AWS Systems Manager Automation integration, execute an automation document and view automation executions. 

**To execute an automation document**

1. Log in to your Jira Service Management customer portal as the end user. 

1. In the Jira Service Management customer portal, choose **Request AWS automation**.

1. Enter **Summary** details.

1. Open the **AWS automation request detail** menu and choose an automation document to execute.

1. Enter the automation request details, parameters, and tags.

1. Choose **Create** to submit the Jira Service Management request and execute the AWS Systems Manager Automation Document.

1. After the request processes, a message indicates the completion of the request. As the automation executes, the end user receives a notification of progress.

**To view automation executions**

1. In the Jira Service Management customer portal, choose **Requests** in the upper right corner.

1. Choose **My Requests** in the Jira Service Management customer portal view.

1. Choose the AWS automation execution you requested. The AWS automation execution details displays and includes the status of the execution, request details, and steps.

# Validating AWS Systems Manager OpsCenter integration
AWS Systems Manager OpsCenter

To validate AWS Systems Manager OpsCenter integration, view or create OpsItems.

**To view OpsItems in Jira Service Management from AWS Systems Manager**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to OpsCenter 

1. Choose **Open Issues** and select the **OpsItem **from AWS that you want to view.

**To create AWS Systems Manager OpsItems in Jira Service Management**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose **Create**. 

1. In the **Create Issue** field input the following details:
   + **Project**: Auto-populated.
   + **Issue Type**: Choose **AWS OpsItem **if you have multiple issue types.
   + **Summary**: Input Summary Details.
   + **Description**: Input Description.
   + **Priority**: Choose the appropriate Priority (default value is Low).
   + **Severity**: Choose the appropriate Severity (required for AWS OpsItem).
   + **Category**: Choose the appropriate Category (required for AWS OpsItem).
   + **Region**: Choose the appropriate AWS Region (required for AWS OpsItem).

1. Choose **Create**.
**Note**  
The newly created OpsItem from Jira Service Management displays in the AWS account view of OpsItem on the next sync between AWS and Jira Service Management.

**To update AWS Systems Manager OpsItems in Jira Service Management**

1. Log in to your** Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to OpsCenter.

1. Choose **Open Issues** and select the **OpsItem** from AWS that you want to update.

1. Choose **Edit Issue**.

1. Update fields available such as Summary, Description, Priority, Severity, Category. The **Resolved **button in the OpsItem issue is also available to select upon resolution.
**Note**  
Updates to OpsItem fields from Jira Service Management displays in the AWS account view of OpsItem on the next sync between AWS and Jira Service Management.

**To view AWS related resources in AWS Systems Manager OpsItems through Jira Service Management**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to OpsCenter.

1. Choose **Open Issues** and select the **OpsItem** from the OpsItem from AWS. 

1. Choose the AWS related resource section of the OpsItem selected. This section displays the related resource details.

**To execute runbooks on AWS Systems Manager OpsItems through Jira Service Management**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to OpsCenter.

1. Choose **Open Issues** and select the **OpsItem**.

1. Choose the OpsItem section of AWS Runbooks. The OpsItem that contains the associated runbooks display a list of automation documents available. (See them next to the star shaped symbol.)
   + Choose **Execute** on the desired runbook. An **Execute Runbook from OpsItem** screen displays.
   + Enter the workflow parameter details associated to the runbook. The runbook will not execute successfully without the correct parameter inputs.
   + Enter metadata tags details if applicable.
   + **Select Create**. An **Execute AWS Systems Manager Automation Request** issue generates and provides the execution status.

   OpsItems without associated runbooks are still able to run automated documents.

**To run automated documents not associated with runbooks**

1. In the OpsItem, choose **Show All Runbooks**. A list on AWS Runbooks display.

1. To narrow the list of runbooks available, enter details into the search bar above the first listed runbook.

1. Choose **Execute** on the desired runbook. An **Execute Runbook from OpsItem** screen displays.

1. Enter the workflow parameter details associated to the runbook. The runbook will not execute successfully without the correct parameter inputs. 

1. Enter metadata tags details if applicable.

1. Choose **Create**. An **Execute AWS Systems Manager Automation Request** issue displays and provides the execution status.

# Validating Support integration
Support

This section describes how to create, view, and manage integration features for Support.

**To view Support cases from Support as Jira incidents**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent **view, choose the Jira project associated to Support

1. Choose **Incidents** and select the Incident related to the Support case in AWS

**To create a general Support case as a Jira incident**

1. Log in to your Jira Agent view as an end user.

1. In the Jira Service Management Jira Agent view, choose the Jira project associated to Support.

1. Choose **Create **from list header and select Issue Type as **Incident**.

1. Complete the mandatory fields on the form.

   Under the Jira Issue Fields section
   + **Summary**- Brief summary of the question or issue
   + **Description** – Detailed account of the question or issue
   + **Priority **– Severity of the AWS Support case

   Under Support fields section
   + **Create Support case** – Check this box to create support case
   + **Support Service and Category** – AWS Service and Category of the support case
   + **AWS Cc Email Addresses** – Add cc email addresses to the Support case (not mandatory)

1. Choose **Create**.

1. Choose the Incident you created from the list. The **AWS Case Id** and **AWS Case Status **displays.

**For AWS managed services Accelerate customers to create AMS Accelerate Report Incident in Jira**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent **view, choose the Jira project associated to Support.

1. Choose **Create** from list header and select Issue Type as **Incident**.

1. Complete the mandatory fields on the form.

   Under **Jira Issue Fields** section
   + **Summary**- Brief summary of the question or issue
   + **Description** – Detailed account of the question or issue
   + **Priority** – Severity of the Support case

   Under **Support fields** section
   + **Create Support case** – Check this box to create support case
   + **AWS Support Service and Category** – Select AMS Operations – Service Request and choose category
   + **AWS Cc Email Addresses **– Add cc email addresses to the Support case (not mandatory)

1. Choose **Create**.

1. Choose the Incident you created from the list. The **AWS case Id **and **AWS case status** displays.

**To add a correspondence and attachment to an existing Support case in Jira incident**

1. Log in to your **Jira Agent **view as an end user

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to Support.

1. Choose **Incidents** and select the Incident related to the Support case in AWS.

1. Use **Add Comment** action or scroll to the bottom of the form and **Click to add comment** to add a correspondence with or without attachments

1. Choose **Share with customer**.

**To resolve an Support case in Jira**

1. Log in to your **Jira Agent **view as an end user.

1. In the **Jira Service Management Jira Agent **view, choose the Jira project associated to Support.

1. Choose **Incidents** and select the Incident related to the Support case in AWS.

1. In the Jira Incident form, choose an action from **Workflow**, **Resolve**.

1. Complete the required mandatory fields.

1. Choose **Resolve**.



**Fields mapped from Support case records to Jira Service Management Incident records**

**Status**: We map Support case status values to JSM state.


| JSM incident status | Support case status | 
| --- | --- | 
| OPEN | Unassigned | 
| OPEN | Opened | 
| WORK IN PROGRESS | Work in progress | 
| WORK IN PROGRESS | Reopened | 
| PENDING | Pending customer action | 
| COMPLETED | Resolved | 

**Priority**: We map Support case severity to JSM Incident Priority


| AWS severity | JSM incident priority | 
| --- | --- | 
| General Guidance | Minor | 
| System Impaired | Low | 
| Production System Impaired | Medium | 
| Production system down | High | 
| Business Critical system down | Blocker | 

# Validating AWS Systems Manager Incident Manager integration
AWS Systems Manager Incident Manager

This section describes how to validate AWS Systems Manager Incident Manager integration in Jira.

**To view Incident Manager incidents**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent **view, choose the Jira project associated to AWS Systems Manager Incident Manager

1. Use [Jira filters](https://confluence.atlassian.com/servicemanagementserver/saving-your-search-as-a-filter-939937027.html) to show only issues with the Issue Type **AWS Incident**

The resulting list displays all synced Incidents.

**To view Incident Manager incident details**

1. Log in to your **Jira Agent view** as an end user.

1. In the **Jira Service Management Jira Agent view**, choose the Jira project associated to AWS Systems Manager Incident Manager.

1. Use [ Jira filters](https://confluence.atlassian.com/servicemanagementserver/saving-your-search-as-a-filter-939937027.html) to show only issues with the Issue Type **AWS Incident**.

1. Choose **Issue Id (Key)** to open the AWS Incident.

1. Review the details of the AWS Incident from the issue.

1. (Optional) Chose the AWS Incident URL to open the incident in the AWS Incident Manager console.

If AWS Systems Manager integration is enabled, an OpsItem is linked to the AWS Incident.

**To resolve an Incident Manager incident**

1. Log in to your **Jira Agent view** as an end user.

1. In the **Jira Service Management Jira Agent view**, choose the Jira project associated to AWS Systems Manager Incident Manager.

1. Use [ Jira filters](https://confluence.atlassian.com/servicemanagementserver/saving-your-search-as-a-filter-939937027.html) to show only issues with the Issue Type **AWS Incident**.

1. Choose **Issue Id (Key)** to open the AWS Incident you want to resolve.

1. Choose **Resolve**.



**Fields mapped from Incident Manager incidents to Jira issue records**

This table shows how AWS Incident Manager Incidents map to a Jira issue.


| AWS Incident Management Incident | Jira AWS Incident | 
| --- | --- | 
| TITLE | Summary | 
| SUMMARY | Description | 
| INCIDENT ARN | AWS Incident ARN | 
| AWS ACCOUNT | AWS Account ID | 
| AWS REGION | AWS Region | 
| STATUS | AWS Incident Status | 
| START TIME | AWS Creation Time | 
| RESOLVED TIME | AWS Resolved Time | 
| UPDATED TIME | AWS Last Updated Time | 
| AWS INCIDENT URL | AWS Incident URL | 
| IMPACT | Priority | 

Incident Status is an integer in Jira Service Management. Jira Service Management Connector maps Incident Manager incident status values to Jira status values.


| AWS Incident Management Incident Status | Jira AWS Incident Status | 
| --- | --- | 
| Open | OPEN | 
| Resolved | RESOLVED | 

Jira Service Management Connector maps **Priority - Imact** of an AWS Incident to the priority of the corresponding JIRA issue.


| AWS Incident Management Incident Impact | Jira AWS Incident Priority | 
| --- | --- | 
| Critical | Blocker | 
| High | High | 
| Medium | Medium | 
| Low | Low | 
| No Impact | Minor | 

# Validating AWS Security Hub CSPM integration
AWS Security Hub CSPM

This section describes how to view AWS Security Hub CSPM Findings, update AWS Systems Manager OpsItems, and view AWS related resources in AWS Systems Manager OpsItems in Jira Service Management.

**To view AWS Security Hub CSPM Findings in Jira Service Management from AWS Systems Manager**

1. Log in to your **Jira Agent **view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to the AWS Security Hub CSPM Finding.

1. Choose **Open Issues** and select the **AWS Security Hub CSPM Finding** from AWS that you want to view.

**To update AWS Security Hub CSPM Finding in Jira Service Management**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to AWS Security Hub CSPM Finding.

1. Choose **Open Issues** and select the AWS Security Hub CSPM Finding from AWS that you want to update.

1. Choose **Edit Issue**.

1. Update the fields available, such as **Severity**, **Priority**, and **Criticality**.

1. Choose **Update** to save the details.

**Note**  
Updates to Security Hub Finding fields from Jira Service Management displays in the AWS account view of Findings on the next sync between AWS and Jira Service Management. Only the fields Severity, Priority, and Criticality update in the AWS account from Jira Service Management.

**To view AWS related resources in AWS Security Hub CSPM Findings through Jira Service Management**

1. Log in to your **Jira Agent** view as an end user.

1. In the **Jira Service Management Jira Agent** view, choose the Jira project associated to AWS Security Hub CSPM Finding.

1. Choose **Open Issues** and select the AWS Security Hub CSPM Finding.

1. In the selected AWS resources section of the AWS Security Hub CSPM Finding, you see the related resource details. If the resources relate and the AWS Config integration is active in the Connector, you can drill down on the Config resource details and relationships. The section remains empty if AWS resources do not relate in AWS Security Hub CSPM.

   AWS Security Hub CSPM findings follow the [AWS Security Finding Format](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-findings-format.html) (ASFF). Here’s a mapping of fields from AWS Security Hub CSPM findings to JSM Incident records.


| JIRA issue field | Security Hub ASFF field | 
| --- | --- | 
|  Created  | CreatedAt | 
|  Updated  |  UpdatedAt  | 
| Summary | Title | 
| Priority | Severity.Label | 
| Status | Workflow.Status | 

**Note**  
Jira does not duplicate findings. If a Security Hub CSPM finding is sent to Jira with the same finding ID as one previously sent to Jira, Jira updates the ticket with the most recent information in the finding.