Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting up coturn for stun-only service behind AWS ELB #1433

Open
Hariprasad-Taduru opened this issue Feb 14, 2024 · 1 comment
Open

Setting up coturn for stun-only service behind AWS ELB #1433

Hariprasad-Taduru opened this issue Feb 14, 2024 · 1 comment

Comments

@Hariprasad-Taduru
Copy link

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.

@eakraly
Copy link
Collaborator

eakraly commented Feb 19, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants