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

AWS Integration unable to fetch data from large environments

XMLWordPrintable

    • 1
    • 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.

      AWS integration seems to currently have limitations regarding large environments, our case is a AWS environment with 200+ accounts, and we are unable to import data in a meaningful timeframe for the implementation to be viable.Two improvements that could help with this:1) Ability to create configurations via code (API or such): We could manage the problem by creating separate import configurations for each accounts, but doing this by hand will not be sustainable in the long run2) Further optimizing the import process: Trying to put more than 10-20 accounts to a single import process will cause it to crash since the import takes more than an hour which in turn causes the AWS access token to expire. The import tool does not handle this exception and becomes stuck.Also the import tool seems to fetch all object types from a single accounts before moving to the next one, is it possible to improve this to run the import in a more parallel way? Do you have any suggestions on how we could improve our configuration or if any improvements on the AWS integration can be expected in the coming year?   

              Unassigned Unassigned
              da0dd4439f59 Alex Cooksey
              Votes:
              8 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: