Today Adobe announced the availability of a new hosting service for FMS: Flash Media Server on Amazon Web Services (AWS). Kevins Towes, FMS Product Manager, has full details on his blog.
In a nutshell, FMS on AWS allows you to quickly deploy a fully licensed instance of FMS 4 in the cloud. The charges are a combination of FMS license fees and Amazon AWS charges, plus a mark-up on the hourly AWS fees. For example a lareg FMS instance which is limited to 100 RTMFP P2P connections will cost $0.44 per hour to run. A normal AWS large instance (without FMS) is charged at around $0.38 per hour. To run such an FMs instance for a month will cost just over $300, plus any bandwidth on top plus a $5 recurring monthly fee.
I was able to test the AWS instances with FMS and I must say it was very easy to get up and running, especially when you are already an AWS customer as I was. I simply logged into the AWS portal, chose the FMS AMI bundle, went through the subscription sign-up and within minutes I had a fully working FMS 4 instance up and running, ready to stream.
I suggest you give FMS on AWS a try next time you need to run a large scale event or need to scale up your existing FMs infrastructure.

#1 by void on 12/17/10 - 1:22 PM
usually you should not worry a lot about computing power and memory when working in the cloud, but what happens when your "service" is mainly based on network ?
Which throughput is fms on aws REALLY able to give ? I mean: a single instance itself can push , say, 2gbps... is it true that if i put 10 instances i can achieve 20gbs ? Where is the bottleneck in networking ? I can't find any information about this.
Is it my fault ?
#2 by Stefan Richter on 12/17/10 - 1:49 PM
#3 by Milka on 12/23/10 - 7:52 PM
#4 by Chandru on 12/30/10 - 6:28 PM
Amazon is good enough for medium scale live streaming...