# Media Soup with AWS Infrastructure

**URL:** https://mediasoup.discourse.group/t/media-soup-with-aws-infrastructure/6854
**Category:** Deployment & Scalability
**Created:** [September 2, 2025, 8:24am UTC](https://mediasoup.discourse.group/t/media-soup-with-aws-infrastructure/6854 "2025-09-02T08:24:05Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![aditigupta](https://avatars.discourse-cdn.com/v4/letter/a/ed655f/32.png) [@aditigupta](https://mediasoup.discourse.group/u/aditigupta)
#### Post date: [September 2, 2025, 8:24am UTC](https://mediasoup.discourse.group/t/media-soup-with-aws-infrastructure/6854/1 "2025-09-02T08:24:05Z")

</div>

I’m reaching out to seek your advice on setting up an application environment. The project involves Node.js, WebRTC, MediaSoup, and a React-based application, with a requirement for scalability.

We attempted to implement an ECS Fargate setup for the Node.js application, which includes WebRTC and MediaSoup components. However, we ran into challenges since MediaSoup requires a static IP address and an ephemeral port range. We tried both Network Load Balancer and Global Accelerator, but neither approach worked. On top of that, creating ~15k listeners in an NLB for port mapping doesn’t seem feasible.

Could you please share your thoughts or suggest a possible solution?