Secure Remote Access for Robots
Roboticks remote access lets you reach any device in your fleet without exposing it to the public internet. Reverse tunnels create secure public URLs for device web services, while device tunnels provide web-based terminal, SSH, and port forwarding access — all encrypted and auto-expiring.
Reverse Tunnels (Public URL Access)
Expose device web services via secure public URLs at device-*.fleet.roboticks.io. Built on AWS IoT Secure Tunneling with an ECS proxy architecture, reverse tunnels support HTTP, HTTPS, and WebSocket protocols. ALB-based Host header routing provides scalability. Each tunnel has authentication requirements, allowed user lists, usage metrics, and auto-expiration for security.
Device Tunnels (Terminal Access)
Access devices directly with web-based terminal (xterm.js), SSH client connections, or port forwarding for custom services. Tunnels have configurable timeouts (default 30 minutes with adjustable idle timeout), optional session recording for audit and training, and bandwidth tracking per tunnel.
Security Architecture
All remote access connections are encrypted end-to-end. Reverse tunnels leverage AWS IoT Secure Tunneling for zero-exposure access. Authentication requirements and allowed user lists restrict access per tunnel. Auto-expiration ensures tunnels don't persist indefinitely. Session recording creates audit trails for compliance.
Use Cases
Debug a robot in the field without physical access. Stream a device's web interface to a stakeholder for a demo. Forward a custom port to test a service running on the device. SSH into a device for emergency maintenance. All without modifying firewall rules or exposing the device network.
Documentation
For setup guides, API references, and technical details, visit the full documentation.