You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the coturn config file (turnserver.conf), I came to know that we can setup and run coturn as stun-only service on aws ec2 instances.
Since these ec2 instances run only stun service, they dont need to have public IP address.
So my query is that can we setup stun-only corturn with multiple ec2 instances behing a aws elb?
If yes, can someone share the steps.
If not possible, can you detail the reasons pls.
Thank you.
The text was updated successfully, but these errors were encountered:
You can try using --tcp-proxy-port option in the config file
It should enable proxy protocol that would pass client IP as seen by LB (obviously you need to configure you LB accordingly).
Having said that:
It only works over TCP
You get dramatic reduction in performance and increase in complexity
There are alternatives to get to higher capacity by using loadbalancing traffic across multiple STUN servers using DNS rather than LB (if that is the goal)
Hope that helps @Hariprasad-Taduru . Pls update if you had any success - would like to hear if this options works.
Hi,
As per the coturn config file (turnserver.conf), I came to know that we can setup and run coturn as stun-only service on aws ec2 instances.
Since these ec2 instances run only stun service, they dont need to have public IP address.
So my query is that can we setup stun-only corturn with multiple ec2 instances behing a aws elb?
If yes, can someone share the steps.
If not possible, can you detail the reasons pls.
Thank you.
The text was updated successfully, but these errors were encountered: