You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We self-host JIRA and Confluence but have just started using JIRA Service Desk in the Cloud. We'd like to link JIRA and JIRA Service Desk but want to lock this connection down to keep our system secure. Per https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html Atlassian publishes it's available IP range for Cloud services but We currently use a mix of our own IP addresses and others provided by third parties is a bit disconcerting given not all IPs are managed by Atlassian and it's quite a large dynamic list.
The server we use for our JIRA and Confluence instances contain sensitive information. Anyone have any best practices or recommendation in making this Cloud to Server link setup in order to meet objectively strict security concerns?