Complete novice - wondering where to start.

We’re setting up a server to record and deliver a live 360 video stream on a website.

The website needs to be able to show the live video but also be able to pull up footage from any (specified) moment in the past.

We’re thinking that setting things up on Amazon AWS is a good idea but do we also need CloudFront?

There will be a physical Wowza server installed on location where the camera system is but bandwidth out is not enough for more than one person to view it at a time - do we need to install an additional wowza server on AWS in order to make it work as planned or?

In planning this first we need to be able to calculate how much it will likely cost at Amazon but we don’t know which parts on the calculator (https://calculator.s3.amazonaws.com/index.html) we’ll be using etc etc questions like:

Elastic IP:

Number of Additional Elastic IPs:

Elastic IP Non-attached Time:

Number of Elastic IP Remaps:

Data Transfer:

Inter-Region Data Transfer Out:

Data Transfer Out:

Data Transfer In:

VPC Peering Data Transfer:

Intra-Region Data Transfer:

Public IP/Elastic IP Data Transfer:

Elastic Load Balancing:

Number of Elastic LBs:

Total Data Processed by all ELBs:

Clearly we need a LOT of help :slight_smile:

Any advice welcome!

Thank you!

There’s no reason to have a Wowza server onsite if it can’t handle multiple clients. You should have one broadcast running from onsite to a Wowza instance in AWS. That instance can then handle recording, rebroadcasting, and VOD playback.

As far as size for your AWS instance, that’ll depend on your load (number of viewers). You’ll have to just have to feel it out as you go pretty much. Setup a demo and see how many clients you can connect while monitoring resource usage. Bandwidth is completely dependent on your stream.

Ahh thank you that makes sense.

On Amazon would the setup have a separate EC2 instance for processing AND storage bucket AND Cloudfront or does it just use a single EC2 instance and that’s it?

We really need to be able to work out how much it’s going to cost for different use cases including such things as ‘n’ users in EU, ‘n’ users in USA etc.

Any advice on how to correctly use the AWS calculator for a Wowza server to give a ‘rough’ idea in different scenarios would be greatly appreciated.

There’s no reason to have a Wowza server onsite if it can’t handle multiple clients. You should have one broadcast running from onsite to a Wowza instance in AWS. That instance can then handle recording, rebroadcasting, and VOD playback.

As far as size for your AWS instance, that’ll depend on your load (number of viewers). You’ll have to just have to feel it out as you go pretty much. Setup a demo and see how many clients you can connect while monitoring resource usage. Bandwidth is completely dependent on your stream.

Ahh thank you that makes sense.

On Amazon would the setup have a separate EC2 instance for processing AND storage bucket AND Cloudfront or does it just use a single EC2 instance and that’s it?

We really need to be able to work out how much it’s going to cost for different use cases including such things as ‘n’ users in EU, ‘n’ users in USA etc.

Any advice on how to correctly use the AWS calculator for a Wowza server to give a ‘rough’ idea in different scenarios would be greatly appreciated.

You’d probably only need 1 EC2 instance. Bucket would probably be needed for storage of VOD files. Cloudfront if you wanted to do caching of the VOD files, probably not needed.

As far as resources, you’d need to give us an idea of the stream you’re running. Resolution, quality, bitrate, etc.