Permitting Inbound/Outbound Traffic with Jamf Cloud
-
IP addresses resolved from a simple nslookup query will not work, as these addresses can change at any time.
-
Jamf controls the IP addresses listed in this article and is the only organization with access to communicate through them.
Inbound Traffic to Jamf Cloud
To connect from your internal network to Jamf Cloud, add the Jamf Cloud DNS name to your safelist, for instance: https://example.jamfcloud.com.
For more information on the current IP address ranges used for inbound traffic to Jamf Cloud, see the following documentation from Amazon: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html
The IP address ranges in that article are not controlled by Jamf and may change any time.
Outbound Traffic from Jamf Cloud
To connect from Jamf Cloud to your internal service, add the following IP addresses to your firewall rules.
| Regions | IP Addresses |
|---|---|
| U.S. |
|
| U.S. GovCloud |
|
| EU Frankfurt |
|
| EU London |
|
| APAC Sydney |
|
| APAC Tokyo |
|
These IP addresses are required when configuring LDAP, SMTP, Rsyslog, SCCM, and other services.
In the event that the above IP addresses are changed, Jamf Cloud customers will be notified.
Outbound Traffic from the Jamf Cloud Distribution Point
| Regions | Domain |
|---|---|
| U.S. |
|
| EU Frankfurt |
|
| EU London |
|
| APAC Sydney |
|
| APAC Tokyo |
|
Additional Information
For service port information, see the following article: Network Ports Used by Jamf Pro