Problem deploying multiple OpenVidu Pro clusters

OpenVidu v2 Issues with deployment
1

Hi

We created another Openvidu Pro cluster in the same AWS Region but in a different VPC and found that the new OpenVidu Server detects the media nodes of the other OpenVidu Pro cluster we have created (which is in another VPC).

The problem is that if the new OpenVidu Pro Server cannot communicate with the media nodes in the other cluster it cannot add the new media node to the cluster.

After both VPCs were able to communicate and the new OpenVidu Pro Server could communicate with the media nodes in the other cluster the new OpenVidu Pro Server was able to add the new media nodes to the cluster

We use the latest version of the CloudFromation template (https://s3-eu-west-1.amazonaws.com/aws.openvidu.io/CF-OpenVidu-Pro-latest.yaml) to create both clusters and use the same license key.

We need both clusters to be separated, do you have any suggestions?

Why is this happening?
Do we need to use a different license key or create the new cluster in a different AWS region?

2

Hello @jorge,

Thank you for reporting the issue. We have a bug in Cloud Formation templates. We are working to fix it and we plan to release a new version the next week.

Please stay tuned.