In order to provide connectivity to the VergeSense cloud platform, and to provide connectivity to network resources for timestamps and serviceability, the following destinations, protocols and ports must be opened through any corporate firewall tools.
If you have any questions regarding the network requirements below, please contact VergeSense support (support@vergesense.com) for assistance.
Please note that the safelist below is for the G400 gateway. The L410 sensors rely on the G400 for connectivity to the VergeSense cloud platform, and the G400 is the only device in this solution that connects to your network. The L410s communicate only with each other and with the G400 over the mesh network.
G400 Gateway Network Requirements
AWS
| Remote Host | Protocol | Port | Justification |
| UDP | 123 | Time server | |
|
vergesense-firmware-uploads-prd.s3.us-west-2.amazonaws.com vergesense-firmware-uploads-prd.s3.amazonaws.com |
TCP/HTTPS | 443 |
AWS S3 bucket for downloading software updates |
|
verge-sense-debug.s3.us-west-2.amazonaws.com verge-sense-debug.s3.amazonaws.com |
TCP/HTTPS | 443 |
AWS S3 bucket for uploading debug images |
| vergesense-device-logs.s3.us-west-2.amazonaws.com | TCP/HTTPS | 443 |
AWS S3 bucket for posting logs |
|
a28r6qxaguevrd-ats.iot.us-west-2.amazonaws.com a28r6qxaguevrd-ats.iot.amazonaws.com |
TCP/MQTT | 443 |
AWS MQTT Broker and IoT Service for authentication |
| cknqf0eqv4hj.credentials.iot.us-west-2.amazonaws.com | TCP/HTTPS | 443 | AWS IOT Initial registration to VergeSense |
Updated
Comments
0 comments
Please sign in to leave a comment.