how to configure mediasoup server api in ec2 aws

Deployment & Scalability
1

Hi
Thank you for this great software.

I separate both app from versatica/mediasoup-demo.
server is on port 4000 and react app on 3000. its working will on localhost.
but when I deploy server to ec2 instance its not showing the remote video as shown in the following image:

image
image1280Ă—917 74.3 KB

info on remote screen:

audio

id: b07e559b-5059-47f2-af95-29c88095ca37

codec: opus

score:10, producerScore:0, producerScores:[0]

video

id: d48f3da5-1abd-46f4-bfa3-39e8fc6c385c

codec: VP8

resolution: 0x0

current spatial-temporal layers: undefined undefined

preferred spatial-temporal layers: 2 2 [ down ] [ up ]

priority: 1 [ down ] [ up ]

[ request keyframe ]

score:10, producerScore:0, producerScores:[0,0,0]

config details

https:
{
    listenIp: '54.176.90.13', 
    listenPort: process.env.PROTOO_LISTEN_PORT || 4000,
    tls:
    {
        cert: process.env.HTTPS_CERT_FULLCHAIN || `${__dirname}/certs/fullchain.pem`,
        key: process.env.HTTPS_CERT_PRIVKEY || `${__dirname}/certs/privatekey.pem`
    }
},

    webRtcTransportOptions:
    {
        listenIps:
            [
                {
                    ip: process.env.MEDIASOUP_LISTEN_IP || '0.0.0.0', // also tried with private ip address
                    announcedIp: process.env.MEDIASOUP_ANNOUNCED_IP || '54.176.90.13' //public ipv4 address
                }
            ],
        initialAvailableOutgoingBitrate: 1000000,
        minimumAvailableOutgoingBitrate: 600000,
        maxSctpMessageSize: 262144,
        // Additional options that are not part of WebRtcTransportOptions.
        maxIncomingBitrate: 1500000
    },

Here is Security groups:

image
image752Ă—261 13.1 KB

How I can able to access remote stream?
I don’t know which mistake I made…

2

Please don’t tag users explicitly, there are more people on the forum than Inaki and Jose that have other things to do in their life.

As to the issue in your inbound rule you are most likely lacking rules for RTC port range used for actual media flow, so only WebSocket works, but not WebRTC.

3

what is the RTC port range and how I will be able to run WebRTC?

4
5

it is already in config.js filr

image
image599Ă—526 34 KB

6

Of course it is, but according to your screenshot you didn’t open them publicly on your instance’s network rules.

7

OK
will open it with tcp or udp?

8

image
image707Ă—212 16.1 KB

9

Both. This is generic WebRTC, there is nothing mediasoup-specific about those ports.

10

check the above screen shot

11

It doesn’t include any UDP ports, which are preferred for WebRTC (and could be the only used by mediasoup-demo, I never used it to say for sure).

12

Its Working . I am very thankful to you. i was facing the problem from last week. you make my day.
THANK YOU.

image
image1514Ă—694 75.8 KB

1 Like
13

now it will work if i deploy my frontend app on s3 static hosting or we need to change something in frontend side?

14

No idea, I guess you’ll have to try and see what happens.
You can also mark the answer as solution so that it is clear for others that question was answered.

1 Like
15

sure…

16

Can you show any guide to deploy mediasoup server to aws?. Thank you.

17

There is nothing special in it, all the steps are written here in the docs, you can follow them:

2 days ago I did these steps on aws ubuntu instance:

  • install python gt 3.6
  • install python3-pip deb package
  • install build-essentials deb package
  • install mediasoup

It was pretty smooth

18

how about aws ecr? and docker file for media server? Thank you.

19

No interaction with these, but you will find resources if you search in this platform.

20

Create a new topic, don’t revive old topics… It helps no body.

All server setups are different, it’s not media-soups responsibility to teach you. In other words, figure it out.

If you can’t figure this out, I don’t want you hosting my private data, super sketch. :slight_smile: