Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-15976

AWS Assets import require significant time for decidingAction step

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Assets Integration
    • 0
    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When importing large amounts of data from AWS that involve multiple accounts and regions, the AWS Asset Import process can take considerable time, particularly during the decision-making phase of the action steps involved in the import.

      The reason is that "outboundReference()" is executed because "Caller Identity" is used as one of identifiers of object types in AWS import configuration. The Object mapping AQL

      "AWS Account Id" IN (${Caller Identity${0}})

      Reference: AWS data imported into Assets

      It would be helpful to review the current AWS implementation when importing a lot of data from AWS accounts

          Form Name

            [JSDSERVER-15976] AWS Assets import require significant time for decidingAction step

            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            Support reference count New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 1
            SET Analytics Bot made changes -
            UIS Original: 3 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            UIS New: 1
            Pablo Bartolome made changes -
            Description Original: When importing large amounts of data into AWS that involve multiple accounts and regions, the AWS Asset Import process can take considerable time, particularly during the *decision-making phase* of the action steps involved in the import.
              
            The reason is that "outboundReference()" is executed because "Caller Identity" is used as one of identifiers of object types in AWS import configuration. The Object mapping AQL

            {code:java}
            "AWS Account Id" IN (${Caller Identity${0}})
            {code}

            Reference: [AWS data imported into Assets|https://confluence.atlassian.com/assetapps/aws-data-imported-into-assets-1168848119.html]

            It would be helpful to review the current AWS implementation when importing a lot of data from AWS accounts             		New: When importing large amounts of data from AWS that involve multiple accounts and regions, the AWS Asset Import process can take considerable time, particularly during the *decision-making phase* of the action steps involved in the import.
              
            The reason is that "outboundReference()" is executed because "Caller Identity" is used as one of identifiers of object types in AWS import configuration. The Object mapping AQL

            {code:java}
            "AWS Account Id" IN (${Caller Identity${0}})
            {code}

            Reference: [AWS data imported into Assets|https://confluence.atlassian.com/assetapps/aws-data-imported-into-assets-1168848119.html]

            It would be helpful to review the current AWS implementation when importing a lot of data from AWS accounts

            Marios Andriotelis added a comment -

            Hi,

            As Pablo mentioned, this process takes a significant amount of time and slows down the import. Please review it and provide a fix

            Thank you!

            Marios Andriotelis added a comment - Hi, As Pablo mentioned, this process takes a significant amount of time and slows down the import. Please review it and provide a fix Thank you!

            Konstantinos Konstantinou added a comment -

            Hi team,

            This issue is severely impacting our efficiency and delaying crucial tasks. A resolution is urgently needed to streamline the import process and eliminate these bottlenecks.

            I appreciate your prompt attention to this matter.

            Best regards

            Konstantinos Konstantinou added a comment - Hi team, This issue is severely impacting our efficiency and delaying crucial tasks. A resolution is urgently needed to streamline the import process and eliminate these bottlenecks. I appreciate your prompt attention to this matter. Best regards

              Unassigned Unassigned
              9f03f4114502 Pablo Bartolome
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: