additional IPs for accessing atlassian cloud

Question

We were following this guide to allow traffic from the cloud to our internal server https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html?_ga=2.37614752.1454838913.1523332098-836828446.1522823018

However, another IP was discovered that needed to be added to the allowed list.  The IP in question is 168.1.55.158

Can someone confirm if this should be added to the IP ranges that are available on the above URL, and if there are any additional IPs that need to be considerd.

Thanks,

John

Shannon S · Answer

Hi John,

I reached out to our network engineering team, and they let me know that this is one of the IP addresses that is mentioned here:

To accelerate file transfers going through api.media.atlassian.com, we use a technology provider that will terminate your TCP connection in the closest public cloud provider. Because of this, you may see that api.media.atlassian.com will resolve to various IPs from various public cloud provider ranges. The list of public cloud providers and the particular one you're redirected to is highly dynamic and will change over time, even based on time of day. This is to give you the best possible experience when downloading and uploading files, but also means we can't provide a fixed IP range for this service.

I hope that clarifies things for you!

Regards,

Shannon

John Kazanis · Answer

By there way, I did a quick search on the IP that I am inquiring about  and it is from Teridion. Teridion (https://www.teridion.com/) is a content-delivery-platform like akamai, and it is used by SaaS providers like Atlassian. This guide https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html did not mention anything about Teridion, if you have any info about it please let me know. We need to whitelist the Teridion IP so that we can let the attachments sync to our ALM  server internally.

Thanks,

John

John Kazanis · Answer

There are no add ons from JIRA perspective.  It looks like the IP stated above is where the Jira issue is storing the cloud attachment. We simply were trying to retrieve the Jira issue and attachment details via a sync client into another test tool - HP ALM..

Not sure how this IP comes into play, so now even more confused.

Thanks anyway,

John