Secure Tunnel between Atlassian Cloud and private cloud (non-Atlassian products)

AJ Hawley

We are setting up a new instance of JSM Premium within the Atlassian Cloud and are looking for a way to secure communication between Atlassian Cloud and our private cloud.

At this point, we have had zero success in establishing a method that ensures our enterprise automation endpoints are not exposed to the internet. Being non-Atlassian products, the typical Application Tunnels will not work for us.

Are there any organizations that have determined a method to secure automation from JSM workflows to call on-prem/private cloud execution of orchestration (ANSIBLE, Jenkins, HP Operation Orchestration).

Any insight would be appreciated!

Gordon S

We faced the same problem after the move from on Premise to Cloud.

As we won´t allow Atlassian to establish a permanent connection to our private infrastructure, we build a internal solution.

It´s based on Ansible which is powered by a custom service which pulls the ticket information and fires the playbooks with the parameters. We use it for user create/modify/block, group assignments, server/service updates...and a lot more.

So, it´s not directly triggered by/from JSM - we pull the data and do the magic.