Using a Jira data source - Amazon Kendra

Using a Jira data source

Jira is a project management tool for software development, product management, and bug tracking. If you are a Jira user, you can use Amazon Kendra to index your Jira projects, issues, comments, attachments, worklogs, and statuses. You can also specify which projects, issues, comments, attachments, worklogs, and statuses to include.

You can connect Amazon Kendra to your Jira data source using either the Amazon Kendra console or the JiraConfiguration API. For a list of features supported by each, see Supported features.

For troubleshooting your Amazon Kendra Jira data source connector, see Troubleshooting data sources.

Supported features

  • Change log

  • Field mappings

  • User context filtering

  • Inclusion/exclusion filters

  • Virtual private cloud (VPC)

Prerequisites

Before you can use Amazon Kendra to index your Jira data source, you must meet the following requirements:

  • You have created an Amazon Kendra index. You must create an index before you create the data source. You need the index id to connect your data source. For more information on how to create an Amazon Kendra index, see Creating an index.

  • You have an IAM role for your data source. Amazon Kendra uses this role to access the AWS resources required to create the Amazon Kendra resource. You provide the Amazon Resource Name (ARN) of the IAM role with the policy attached when you connect your data source to Amazon Kendra. If you are using the API, you must create an IAM role before you connect your datasource. If you use the AWS console, you can choose to use an existing IAM role or create a new one when you configure your Amazon Kendra connector. For more information on using an IAM role for your Jira data source, see IAM roles for data sources.

  • You have a Jira account in which you have:

    • Created Jira API token authentication credentials that include a Jira Id and a Jira Credential.

  • You have noted the Jira account URL from your Jira account settings. For example, company.atlassian.net or https://jira.company.com. You will need your Jira account URL to connect to Amazon Kendra.

    You can find more information on how to configure your Jira account on the Jira Developer Documentation page.

  • You have an AWS Secrets Manager secret containing the authentication credentials you are using to connect your Jira data source with your Amazon Kendra index. If you are using the console to create your data source, you can create the secret there, or you can use an existing Secrets Manager secret. If you are using the API, you must provide the Amazon Resource Name (ARN) of an existing secret. It is recommended that you regularly refresh or rotate your credentials and secret, and only provide the necessary level of access for your own security.

  • (Optional) If you want to map attributes or custom index fields from your Jira data source to your Amazon Kendra index, you must make sure that these attributes and custom fields already exist in your data source file system custom metadata.

Connecting Amazon Kendra to your Jira data source

To connect Amazon Kendra to your Jira data source you must provide details of your Jira credentials so that Amazon Kendra can access your data. If you have not yet configured Jira for Amazon Kendra see Prerequisites.

Console

To connect Amazon Kendra to Jira

  1. Sign in to the Amazon Kendra at AWS Console.

  2. From the left navigation pane, choose Indexes and then choose the index you want to connect from the list of indexes.

  3. On the Getting started page, choose Add data sources.

    Note

    You can choose to configure or edit your User access control settings under Index settings.

  4. On the Add data source page, choose Jira, and then choose Add connector.

  5. On the Specify data source details page, enter the following information:

    1. Data source name—Enter a name for your data source. You can include hyphens but not spaces.

    2. (Optional) Description—Enter an optional description for your data source.

    3. Default language—A language to filter your documents for the index. Unless you specify otherwise, the language defaults to English. Language specified in metadata overrides selected language.

    4. Add new tag—Tags to search and filter your resources or track your AWS costs.

    5. Choose Next.

  6. On the Define access and security page, enter the following information:

    1. Jira Account URL—Enter your Jira Account URL.

    2. AWS Secrets Manager secret—Choose an existing secret or create a new Secrets Manager secret to store your Jira authentication credentials. If you choose to create a new secret an AWS Secrets Manager secret window opens.

      1. Enter following information in the Create an AWS Secrets Manager secret window:

        1. Secret name—A name for your secret. The prefix ‘AmazonKendra-Jira-’ is automatically added to your secret name.

        2. For Jira ID and Password/Token—Enter the authentication credential values you generated and downloaded from your Jira account.

      2. Choose Save.

    3. Virtual Private Cloud (VPC)—You can choose to use a VPC. If so, you must add Subnets and VPC security groups.

    4. IAM role—Choose an existing IAM role or create a new IAM role to access your repository credentials and index content.

      Note

      IAM roles used for indexes cannot be used for data sources. If you are unsure if an existing role is used for an index or FAQ, choose Create a new role to avoid errors.

    5. Choose Next.

  7. On the Configure sync settings page, enter the following information:

    1. Select which Jira projects to index—The Jira entities or content types you want to crawl.

    2. Statuses, Additional elements, and Issue types—Select content to refine the scope of your index.

    3. Change log—Select to update your index instead of syncing all your files.

    4. Regex patterns—Regular expression patterns to include or exclude certain files. You can add up to 100 patterns.

    5. Frequency—How often Amazon Kendra will sync with your data source.

    6. Choose Next.

  8. On the Set field mappings page, enter the following information:

    1. For Project, Issue, Comment, Attachment, Worklog—Select from the Amazon Kendra generated default data source fields you want to map to your index.

    2. Add field—To add custom data source fields to create an index field name to map to and the field data type.

    3. Choose Next.

  9. On the Review and create page, check that the information you have entered is correct and then select Add data source. Your data source will appear on the Data sources page once it is added successfully.

JiraConfiguration API

To connect Amazon Kendra to Jira

You must specify the following using the JiraConfiguration API:

  • Data source URL—You must specify your Jira account URL. For example, company.atlassian.net and https://jira.company.com.

  • Secret Amazon Resource Name (ARN)—You must provide the Amazon Resource Name (ARN) of a Secrets Manager secret that contains the authentication credentials you created in your Jira account. You provide the ARN using the CreateDataSource API. The secret is stored in a JSON structure with the following keys:

    { "jiraId": "Jira user name", "jiraCredential": "Jira API token" }
    Note

    It is recommended that you regularly refresh or rotate your credentials and secret, and only provide the necessary level of access for your own security. For more information on permissions, see IAM roles for Jira data sources.

  • IAM role—You must provide an IAM role with permissions to access your Secrets Manager secret and to call the required public APIs for the Jira connector and Amazon Kendra. For more information, see IAM roles for Jira data sources.

You can also add the following optional features:

  • Virtual Private Cloud (VPC)—You can choose to specify VpcConfiguration when you call CreateDataSource. See Configuring Amazon Kendra to use a VPC.

  • Change log—Whether Amazon Kendra should use the Jira data source change log mechanism to determine if a document must be added, updated, or deleted in the index.

    Note

    Use the change log if you don’t want Amazon Kendra to scan all of the documents. If your change log is large, it might take Amazon Kendra less time to scan the documents in the Jira data source than to process the change log. If you are syncing your Jira data source with your index for the first time, all documents are scanned.

  • Inclusion and exclusion filters—You can specify whether to include projects, issues, comments, attachments, worklogs, and statuses. You can also specify regular expression patterns to include or exclude projects, issues, comments, attachments, worklogs, and statuses.

    Note

    If you specify an inclusion filter, only content that matches the inclusion filter is indexed. Any document that doesn’t match the inclusion filter isn’t indexed. If you specify an inclusion and exclusion filter, documents that match the exclusion filter are not indexed, even if they match the inclusion filter.

  • Context filtering—You can choose to filter a user’s results based on their user or group access to documents. For more information, see User context filtering for Jira data sources.

  • Field mappings—You can choose to map your Jira data source fields to your Amazon Kendra index fields. For more information, see Mapping data source fields.

Learn more

To learn more about integrating Amazon Kendra with your Jira data source, see: