Cloud Connector FAQ
If a system is only accessible on an internal network, but an AWS RTVision cloud application needs to connect (to pull or push data), the Cloud Connector can be installed locally. This securely provides the necessary access without exposing the internal system to the internet.
The Cloud Connector runs as a Windows service that is always active. It starts an HTTPS server on the specified IP and port using a self-signed certificate. It offers two endpoints:
/health-check – Returns the connector version and can be used to test if digital signatures verify as expected.
/forward – Receives POST requests from an RTVision cloud application and initiates connections to internal systems. Currently the only integration types supported are HTTP(s), FTP(s), and ODBC database connections
During installation, only authorized sites are allowed to send requests to the /forward endpoint. All requests are validated with digital signatures using ECDSA with P-521 keys: the connector checks each incoming request against the originating site’s public key. If the signature doesn’t match, the request is rejected. The connector is written in Rust, providing compile-time safety checks to avoid common classes of vulnerabilities. Rust is also on the approved list of safer languages provided by NIST . All dependencies are also audited to ensure no known vulnerabilities are released.
Generally, no. The service will automatically update itself nightly (around midnight or 1 AM, depending on daylight savings) to ensure timely security patches. The installer also updates itself on first startup. Additionally the service will be set to auto-start if the machine restarts.
We send logs and issues to sentry to aid us in quickly debugging and identify issues such as errors occurring or performance bottlenecks.
https://rtvision.atlassian.net/wiki/spaces/OFFICE/pages/2800254977 can been read to see how we use sentry for our Cloud application
Contact support and we can look into logs that we have being sent to sentry