Hi Steve,

AWS released multicast support for Transit Gateway. If that covers your use case, I’d recommend using that: https://aws.amazon.com/about-aws/whats-new/2019/12/run-ip-multicast-workloads-aws-transit-gateway/

Since this solution uses an overlay network the scale will be limited by the performance of n2n. They try to use peer to peer connections, but your multicast traffic will eventually have to be sent over the underlying vpc network. I’d recommend doing a load test to make sure the performance matches your expectations.

If you want to load balance the supernode, you’d have to search the n2n documentation to see if that is possible.

Kind regards,
Ben

I’d like to know how well this scales under extremely heavy loads and if the server running supernode can be load balanced under AWS?

Thanks

Hey Peter,

The supernode is part of the n2n tunnel by default, so it’s not needed that you run both on the same instance.

Hi emkay,

Thanks for you reply. You can use MINT (http://sourceforge.net/projects/mc-mint/) or iperf to test if multicasting works.

iperf example:

Client; iperf -c 224.0.0.10 -b 50K -t 300 -T 5 -u 1234 -i 1 -l 136

Server : iperf -s -B 224.0.0.10 -u -i 1

Br,

Senne Vaeyens