nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JSM Cloud Assets - AWS Integration

Nicolae Doca

I am looking for a way to realize the integration between JSM and AWS in order to populate the JSM Asset schema with our AWS Assets. Unfortunately I see that the existing Atlassian plugin is only for on-premise (and also deprecated) however there is nothing for the cloud version.

Has anyone found a way to do this regardless if with another plugin or another way ?

Thanks

Accepted answers

All comments

Harry Theodorou

From my own struggles with this the only method offered by Atlassian at the moment is with manual json or csv import. You can get your export from AWS, Resource Groups & Tag Editor or Control Tower depending on your management and then either do manual imports or try to automate this procedure.

My approach at the moment is to automate the import part using Microsoft Power Automate Desktop and the export with Lambda functions on an S3 bucket mapped to a VM for the import part.

Any other suggestions are welcome.

By the way Atlassian must already be working on providing AWS Integration with the JSM Cloud version since they are no longer supporting the on prem however they don't have anything in the immediate pipeline and keep things close to their chest. This is a major requirement for large organizations to fully implement a CMDB solution.

Sekhar Reddy Idamakanti

Hi @Harry Theodorou

Thank you for the solution, is this working as expected for you ?

How you are managing the mapping (in bound and out bound relation) from asset discovery tool objects and this import objects? Is mapping is one time process or we need to keep on update when ever any changes in the objects side.

Harry Theodorou

We are still in the process of testing this as it involves

Automating the import in Assets - Done
Automating the export from AWS with a Lambda function to export/override filename - Not done
Mapping the export location on the machine that will be importing from - Done
Replicating process on a VM using a Jira service account and S3 bucket - Not done

The relations need to be mapped manually in the import step based on AWS tags of resources. In our case we are are mapping based on the environment and the environment is mapped on the application (e.g. Application A -> prod -> EC2, S3 etc). The mapping part works fine.

Steffen Opel [Utoolity]

I only noticed this post today, but maybe this helps with your mid-term planning regardless:

We (Utoolity) have developed a prototype for an AWS resources importer dubbed 'Integrate with AWS (Assets)' that we hope to publish as a commercially supported app in the Marketplace in the coming months.

Unfortunately we are encountering scaling issues with the Assets API and need assistance from Atlassian to remediate this. Our Atlassian contacts have been busy with Team '24 though, so this initiative stalled over April and we aim to pick it up again next week.

I'm afraid the prototype is not yet usable for third-parties, but if you are interested and willing to help us shape the product, feel free to join our early access program (EAP) to start the conversation early on.

If you'd rather wait for the EAP to be available, please watch AWS Integration for Assets Cloud (JSDCLOUD-9896), where we'll post a demo video soon, and I'll also provide an update here of course.

Sekhar Reddy Idamakanti

Hi @Harry Theodorou

Do you have the mapping format for the AWS assets ? I mean relation ship has to be mentioned in the CSV or JSON file before importing the file into schema. (Load balancers are connected to which Ip's and target groups.)

Ivan_ohfijn

Hi Steffen.

I am very interested in your new integration and I have signed up for the EAP. I wonder if you can give an idea of when you might have something that's worth testing? Do you think it might be weeks or months away?

Thanks.

Steffen Opel [Utoolity]

Hi @Ivan, and welcome to the Atlassian Community!

Thank you for signing up to our EAP, and apologies for not responding to your request in time, I dropped the ball on this due to an unforeseen personal absence. Please expect a more detailed answer on your EAP request soon.

Just briefly right here: We hope to get feedback on the scaling issues from Atlassian by end of June, and assuming there will be a path forward, we can evolve our prototype towards an official EAP throughout July. That being said, I'd be happy to discuss sharing an earlier version with you once we've picked up this workstream again next week, I'll be in touch!