Summary

When working with custom script automations and integrations, you will need to use the external IP address from our Cloud instance in order to make this work. Since we currently use a mix of our own IP addresses and others provided by third parties, you might wonder if it's possible to use a Static IP address from your Cloud instance instead in order to make your custom script to work.

Environment

Cloud Only.

Diagnosis

Atlassian products use domains with many levels of subdomains under all the listed top-level domains. 
For example, a permit entry for *.atl-paas.net should allow both avatar-management--avatars.us-west-2.prod.public.atl-paas.net and jira-frontend-static.prod.public.atl-paas.net.

Additionally, you will need ensure that top-level domains themselves are also permitted, not just their subdomains.

For example, *.atlassian.com should permit both id.atlassian.com and atlassian.com.

Solution

It's not possible to specify an unique Static IP for your Jira Cloud instance as this could cause issues with other integrations and services we work with.

The Atlassian Cloud IP ranges and domains are all documented in the link below:

• Atlassian Could IP Ranges and Domains