/
Import Configuration for AWS Importer

Import Configuration for AWS Importer

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

Multiple connections can be created after defining the sources and destinations.

  1. To begin, click the “Add New Connection” button.

image-20250227-131212.png

  1. Assign a name to your connection.

  2. Choose a source from the available list.

  3. Select a destination from the provided options.

  4. If this is your first attempt at configuring the import, choose “None” from the schedule list. You can modify this setting after completing the steps outlined on this page.

  5. Click the Save button.

  6. Press the Close button to return to the Connections list.

  7. Follow the three steps detailed below:

1. Build Object Type and Attributes

To proceed, click the Build button. Additionally, you have the option to enable or disable Object Schema sharing as per your requirements.

Pro Tip: Many of our customers often create references from other Object Schemas and require access to AWS data. To facilitate this, we recommend enabling Object Schema sharing.

Review the options and click the Build Data Model button.

image-20250227-131252.png

This step only needs to be completed once. Once the build is successful, you won’t need to repeat it. If this step has already been completed, a message will appear confirming it.

You may check your Object Schema now and make sure the Object Type and Attributes are successfully created.

Pio AWS Schema.png

2. Test Import

You can verify the configuration by clicking the Test button. This action will import the first 10 records for each resource type into your Object Schema, allowing you to confirm the following:

  • The AWS credentials are accurate, and the necessary permissions are granted.

  • The Jira credentials are valid.

  • The Object Schema is configured correctly.

After clicking the test import button, please wait a few minutes for the process to complete, and then review your Object Schema.

Additionally, you can click the Check button to monitor the status of the import execution.

3. Full Import

If you are happy with the results of the test import, please run a Full Import.

Pro Tips:

  • Please be aware that importing a substantial number of AWS records may require considerable time. We recommend performing this task during off-peak hours when JSM Assets is less actively used.

  • Refrain from clicking the Test Import and Full Import buttons in quick succession; ensure that the first import has completed before initiating the next one. JSM Assets does not accommodate multiple simultaneous imports.

Important Note: Daily Imports

Daily imports are typically scheduled during late-night hours (00:00-06:00), when the system is under lighter load. However, keep in mind that these hours are also used by Atlassian for JSM/Assets version updates. If there's a conflict, the import process may fail, and you will see an error message in your logs.

To ensure smooth operation, check your import flow daily and enable the Notify Me feature to receive alerts if an error occurs. We highly recommend reviewing the Operational Tips provided on the following page: Operations

Related content