[asterisk-users] AWS/EC2 server selection

[Jeff LaCoursiere]

Amazon instances are shared resources.  I wouldn't want to count on 
timing or disk throughput, and you can't just ask them to do "ssd" - its 
a virtual machine!  500 simultaneous recordings is a hefty load, and I 
would want to know that the underlying hardware is dedicated to the task.

Sure you see lots of posts about hosting asterisk and/or freeswitch on 
EC2.  I have done it myself and even have some clients doing it now *for 
proof of concept*.   I've never heard of anyone using it for the kind of 
load you are talking about.  I'm assuming with such a giant load you are 
making a decent profit. Buy some hefty hardware and do the architecture 
properly.  You can rent half a rack at lots of high end datacenters for 
less than $1000/month.

j

On 03/07/2015 12:43 AM, Amit Patkar wrote:
> Hi Jeff
>
> Are you aware of any challenges of hosting it on AWS? It will help me 
> to work out alternate plan. Is there any recommendation? Should I 
> split it to multiple instances and balance traffic across multiple 
> small server instances? I can use Kamailio to balance traffic.
>
> I see many posts referring to AWS deployment. Please help me to choose 
> AWS server instance.
>
> *Thanks & Regards,*
> Amit Patkar
>
>
> On 3/7/2015 12:19 AM, Jeff LaCoursiere wrote:
>>
>> Why use Amazon?  With that kind of load I would want dedicated 
>> servers.  Call Rackspace or Softlayer.
>>
>> j
>>
>> On 03/06/2015 11:59 AM, Amit Patkar wrote:
>>> Hi
>>>
>>> I plan to host Asterisk instances on AWS/EC2 servers.
>>> Requirement is to run asterisk instance with transcoding (g.729 + 
>>> g.711) and full recording. Number of concurrent calls expected are 
>>> 500+. 2 instances will be configured for 100% redundancy. Heart beat 
>>> will be used to determine active instance.
>>> How should I choose EC2 instance?
>>> How many vCPU, RAM should be selected? I am assuming that server 
>>> with ssd is required as all 500+ calls needs to be recorded.
>>>
>>> Regards,
>>> Amit Patkar
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20150308/2e6fd93d/attachment.html>