I found an old thread on this topic in the community, but maybe something has changed in the meanwhile.
So I ask for an update.
Which are the firewall rules (ports and domains) necessary to use Torizon Cloud?
Both from SoM side (i.e., device) and from developer side.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
To use Torizon Cloud effectively, you need to ensure that your firewall rules allow communication between your devices (System on Modules - SoMs) and the Torizon Cloud services, as well as from the developer’s side. Here are the general guidelines for the necessary firewall rules:
From the Device (SoM) Side:
Outbound Connections:
HTTPS (Port 443): Ensure that your devices can make outbound HTTPS connections to the Torizon Cloud servers. This is essential for secure communication and updates.
MQTT (Port 8883): If your devices use MQTT for telemetry or other communication, ensure that outbound connections on port 8883 are allowed.
DNS Resolution:
Ensure that your devices can resolve DNS queries to reach the Torizon Cloud services.
From the Developer Side:
Outbound Connections:
HTTPS (Port 443): Developers need to access the Torizon Cloud web interface and APIs, which require outbound HTTPS connections.
Development Tools:
If you are using development tools like TorizonCore Builder or the Torizon IDE Extension, ensure that these tools can also make outbound HTTPS connections to the Torizon Cloud.
General Recommendations:
Allowlist Torizon Cloud Domains: To ensure seamless communication, you might want to allowlist specific Torizon Cloud domains. These domains can be found in the Torizon Cloud documentation or by contacting Toradex support for the most up-to-date information.
Monitor and Adjust: Regularly monitor the communication logs and adjust the firewall rules as necessary to accommodate any changes in the Torizon Cloud infrastructure or your specific use case.
For the most accurate and up-to-date information, especially if there have been recent changes, I recommend checking the official Torizon Cloud documentation or contacting Toradex support directly.
Please, also check if these links can help you solve your problem:
I believe the only change since that other thread is that the gateway is now https://dgw.torizon.io/ instead of https://ota-ce.torizon.io/. Everything else should still be the same as stated in that thread.
