Skip to main content
T
tracerflash
Participant
April 24, 2012
Question

Sizing of EC2 Instance for FMS Server - HDS and HLS Streams via Cloudfront

  • April 24, 2012
  • 1 reply
  • 609 views

Is there any reason to go larger than a "Large" EC2 FMS instance for live streaming HDS and HLS streams via Cloudfront?  Is it correct that the 100 connection limit for the large instance refers to a different P2P protocol?  It is my understanding that when distributing through Cloudfront the EC2 server should not see  very much traffic (just streaming the fragments out to the CDN edge locations).

Last but not least, is there any sort of reserve instance pricing option for the FMS server?  I understand the flexibility of being able to turn it off and on as needed, but for my particular client we would prefer to just have it on all the time for them, even though it will rarely be used.  In this use case, the high hourly price and no option to save $ with reserved pricing is a bummer.  Thank you for your help.

Best Regards,

-Mike

    This topic has been closed for replies.

    1 reply

    S
    ShivenK
    Inspiring
    April 25, 2012

    Hey Mike,

    Yes you are right in saying that for the HDS/HLS use case, a lesser powerful FMS instance would do, unless you plan to serve RTMP content since it is Apache and not FMS which is serving content in case of HDS, HLS.

    Yes the connection limit is only for RTMFP, the p2p protocol. All FMS instances enjoy no other restrictions.

    As per the reserved instances question, currently the pricing model only supports the per hour costing.

    Thanks!

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices