/
Destination Configuration for AWS Importer

Destination Configuration for AWS Importer

Owned by Pio
Last updated: Apr 02, 2025 by Eva Ruzheva

There are 3 steps in the process of creating a destination. You can create multiple destinations.

1. Add new destination

Our application leverages Jira Rest API for programmatic access while updating Object Schema, Object Type, and Attribute configurations of JSM Assets.

You'll need assistance from a Jira Administrator to complete the steps outlined on this page.

  1. Create a Jira Admin User to be used in the application (e.g. jira_bot@example.com)

  2. Ensure the user has a JSM Agent License.

  3. Login with the bot user and create an API Token (How to…)

  4. On the Destination Tab, select “Add New Destination” button.

image-20250226-155331.png

 

  1. Give a name for your destination

  2. Enter the User Email (e.g. jira_bot@example.com) and Jira API Token in the Jira Connection Settings.

  3. The Jira Service Management Site Name is the first part of your Jira Cloud URL.

  • Example: If your base URL is https://site-name.atlassian.net Please just enter your "site-name".

  1. Click Add button.

  2. Once the success message is displayed, click Close to return to the list of destinations.

2. Schema Selection

  1. Click Set/Select button

image-20250226-161223.png

2- You have two options in this section. You may create a new Object Schema or use an existing one.

Pro Tip: To effectively manage your AWS-related data, create a new Object Schema dedicated to its storage. This approach enables you to assign roles specifically to the relevant users or groups. Remember that the imported data may contain personal information, so it's crucial to adhere to your organization's data handling guidelines.

Option 1: New Schema

  • Click the New Object Schema option.

  • Fill in the fields for your new Schema

  • Click Create Object Schema

image-20250227-130210.png

Option 2: Use an Existing Object Schema

  • Select an Existing Object Schema.

  • Choose a schema from the dropdown.

  • Click "Use Existing Object Schema" to continue

image-20250227-130544.png

If an Object Type already exists in your current schema, we will inform you and request that you make the necessary updates before proceeding.

Regardless of whether you choose Option 1 or 2, be sure to remove the default values from the Object Schema Roles menu. Here's how it should look:

Object Schema Roles.png

Then, only add the relevant users, groups, or apps.

3. Set Import Token

To import a large amount of data into JSM Assets, you need to generate a key that securely authorizes the data transfer (more info).
Please add the Import Token for your External Import configuration in Assets.

  1. After selecting the Object Schema, locate the Import Tab link by clicking on the Object Schema. This action will direct you to the Import Page, where you can generate an Import Token.

image-20250402-204146.png

 

  1. Click "Create Import" to begin the setup.

  1. Select "External Import" and click "Next".

Screenshot 2025-01-10 at 14.25.10.png

  1. Enter a Name and Description.

Name: AWS Importer for JSM Assets

Description: Data is imported from AWS automatically.

Screenshot 2025-01-10 at 14.36.17.png

  1. Click the three dots (…) and select "Generate new token".

  1. Copy the generated token.

  1. Select “Set” button under Import Token for the desired schema. Paste the token into the Import Token field in Import Token Configuration, then click "Save Import Token".

Screenshot 2024-08-10 at 01.37.51.png

  1. If successful, click the Close button to return to the list of destinations.

  2. Now, it is time to import.