I’ve since figured all this out and thought I’d put something out there to help those who are as clueless as I was just a few months ago about ice connections, stun/turn servers, signaling, webRTC proxy, and all that goes with getting this working on a public IP.
There are two examples I shared. One is using AWS and the other is using Azure. Both examples run everything off the same machine. You can, however, use multiple instances if you want like installing coturn and running the stun/turn on a AWS Ubuntu instance and then running the signaling and webRTC on a Azure instance. However, I’m not going to cover that scenario since the 2 other examples should give you a good starting point for customizing your solution. I will say, it’s much easier to run everything off a single instance then dealing with load balancing and other optimizations when using more then one instance.
You’ll notice I did not block out the public IPs I use because I wanted to show everything. Those IPs are for testing purposes only and since they are only on for a few minutes here and there they have no value to you.
https://croftinteractive.blogspot.com
Hope it helps someone.