How to create stun turn server instance using AWS EC2

Question

Actually i wants to use my own stun/Turn server instance and i want to use Amazon EC2 .If anybody has any idea regarding this please share with me the steps to create or any

Answer 1

One method to install a turnserver on Amazon EC2 would be to choose Debian and to install the coturn package, which is the successor of the RFC5766-server.

The configuration file at /etc/turnserver.conf includes EC2 specific instructions. The information provided within this file is very exhaustive in general and should answer the majority of configuration questions.

Once configured, the coturn server can be stopped an started however you would any other service.

Answer 2

do an ssh login to your ec2 instance, then run the below commands for installing and starting the turn server.

simple way:

sudo apt-get install coturn

If you say no, I want the latest cutting edge, you can download source code from their downloads page in install it yourself, example:

sudo -i     # ignore if you already in admin mode
apt-get update && apt-get install libssl-dev libevent-dev libhiredis-dev make -y    # install the dependencies
wget -O turn.tar.gz http://turnserver.open-sys.org/downloads/v4.5.0.3/turnserver-4.5.0.3.tar.gz     # Download the source tar
tar -zxvf turn.tar.gz     # unzip
cd turnserver-*
./configure
make && make install 

sample command for running TURN server:

turnserver -a -o -v -n -u user:root -p 3478 -L INT_IP -r someRealm -X EXT_IP/INT_IP  --no-dtls --no-tls

command description:

• -X - your amazon instance's external IP, internal IP: EXT_IP/INT_IP
• -p - port to be used, default 3478
• -a - Use long-term credentials mechanism
• -o - Run server process as daemon
• -v - 'Moderate' verbose mode.
• -n - no configuration file
• --no-dtls - Do not start DTLS listeners
• --no-tls - Do not start TLS listeners
• -u - user credentials to be used
• -r - default realm to be used, need for TURN REST API

in your WebRTC app, you can use trun server like:

{
    url: 'turn:user@EXT_IP:3478',
    credential: 'root'
}