vMix Forums
»
General
»
General Discussion
»
AWS Multi Instance Configuration
Rank: Newbie
Groups: Registered
Joined: 12/17/2020(UTC) Posts: 1
|
We are migrating from physical computers to the cloud using AWS. We have been successful in getting five g4dn.4xlarge instances setup and vmix installed. The challenge we are running into is getting the servers to see each other and share NDI.
Any guidance on this configuration would be appreciated.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 5/28/2020(UTC) Posts: 35 Location: London Thanks: 3 times Was thanked: 1 time(s) in 1 post(s)
|
They all need to be in the same VPC.
Also check your security policy, so that they're allowed to talk to each other.
|
|
|
|
Rank: Member
Groups: Registered
Joined: 5/2/2020(UTC) Posts: 19 Location: Dublin Thanks: 2 times Was thanked: 2 time(s) in 2 post(s)
|
Originally Posted by: esc87 We are migrating from physical computers to the cloud using AWS. We have been successful in getting five g4dn.4xlarge instances setup and vmix installed. The challenge we are running into is getting the servers to see each other and share NDI.
Any guidance on this configuration would be appreciated. There is a bit of a workaround that you need to do for NDI on AWS. - First of all, make sure all your devices are within the same VPC. I also suggest having an Elastic IP, otherwise in the next step you'll have to reconfigure each time you fire up your devices. - Download and install NDI Tools on every machine. - Configure NDI Access Manager - Add the IPs for all your vMix devices. - Restart your systems, open vMix. You should see the devices.
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 7/9/2020(UTC) Posts: 2 Location: Middeltown
|
Originally Posted by: KMR Originally Posted by: esc87 We are migrating from physical computers to the cloud using AWS. We have been successful in getting five g4dn.4xlarge instances setup and vmix installed. The challenge we are running into is getting the servers to see each other and share NDI.
Any guidance on this configuration would be appreciated. There is a bit of a workaround that you need to do for NDI on AWS. - First of all, make sure all your devices are within the same VPC. I also suggest having an Elastic IP, otherwise in the next step you'll have to reconfigure each time you fire up your devices. - Download and install NDI Tools on every machine. - Configure NDI Access Manager - Add the IPs for all your vMix devices. - Restart your systems, open vMix. You should see the devices. Can you explain Elastic IP? I just got a system up and moving NDI around with access manager running and so on. I would like to not have to set that up each time.
|
|
|
|
Rank: Member
Groups: Registered
Joined: 5/2/2020(UTC) Posts: 19 Location: Dublin Thanks: 2 times Was thanked: 2 time(s) in 2 post(s)
|
Originally Posted by: cravetech Can you explain Elastic IP? I just got a system up and moving NDI around with access manager running and so on. I would like to not have to set that up each time.
Yep. An elastic IP is a static public IP. I believe AWS charges about $1/month for those. Though, I don't suggest communications between your vmix instances need static public IPs, you CAN do static private IPs just by changing your VPN settings. I would put your private IPs in NDI Access Manager. I do setup static public IPs though on all of my vmix instances just for ease of access on the outside. I think AWS charges like $1 / Elastic IP / mo (something like that).
|
|
|
|
vMix Forums
»
General
»
General Discussion
»
AWS Multi Instance Configuration
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close