The Jamf Protect agent uses TCP port 443 for all network communication.
If your environment uses transparent or explicit TCP proxies and primary agent communication is blocked, you can enable WebSocket/MQTT as an alternative protocol to the default of standard MQTT.
Depending on the region your Jamf Protect tenant is located in, the Jamf Protect agent may communicate with different AWS subdomains.
For information on network communication used by Jamf Security Cloud, see Network Communication used by Jamf Security Cloud.
HTTPS Interception (SSL Inspection) is not supported for connections to Jamf Protect due to Jamf Protect using mTLS for communication between devices and the Jamf Protect tenant. If client HTTPS traffic traverses a web proxy, you must disable HTTPS Interception for connections to Jamf Protect.