Securing Openvidu for production use on AWS

Issues with deployment
1

2.13 sees the inspector UI, kibana, API, and public websocket all running from 443.

This is a bit of a security issue for us as there is no way to update the ec2 security group to restrict public internet access to the inspector & kibana (and these interfaces are only protected by basic auth).

Ideally we would want to only allow public internet access to the websocket, the REST API and admin interfaces (kibana, inspector) can all be restricted to be accessed by our private IP ranges (internal network VPN for interfaces, our server IP ranges for the REST API).

Is it possible to configure Openvidu pro to set these ports?

2

Next release 2.14.0 will bring the ability to change the default HTTPS port where all services are available and also to limit the access to administration dashboards to a specific set of IPs. Stay tuned.