Search results

I'm not sure if there are additional benefits for a single server in a VPC. I'm pretty sure the Security Groups handle all of your requirements in this case i.e. all incoming ports blocked by default except those you nominate. If you were using multiple servers (say a separate database server)...

You might like to look at Vagrant too http://www.vagrantup.com/. There is a plugin to support EC2 as a provider: https://github.com/mitchellh/vagrant-aws so you could build it locally on VMWare and, once you have a working build script just do the same thing with the EC2 provider to launch...

Are you talking about building and testing Asterisk 12 on a local VMWare instance and then migrating that to EC2? It looks like importing VMWare images is supported but I haven't tried this. http://aws.typepad.com/aws/2013/12/vm-import-export-for-linux.html

BTW, here's the article I mentioned. http://aliensgrin.com/2014/01/20/pbx-in-a-flash-piaf-on-amazon-ec2/ It's a broad overview of our experience setting up PIAF on AWS for our business. I'll keep it up to date with the progress here.

Thanks wardmundy, hope it works out. The EC2 solution has been a good "instant gratification" tool for evangelising PIAF so it would be great to have it hanging around. Even if it doesn't we still have some options up our sleeve so keep us posted.

Costs In my experience AWS are pretty transparent about pricing and the "pay for what you use" principle seems to be consistent. "Transparent" doesn't always mean "easy to figure out" though, I agree. The simplest way to pin down the real costs is to put the AMIs on an otherwise unused account...

These will be missed. I'm sure they have been very useful to get PIAF going "in a flash" so there is instant gratification for people curious about trying it out. I was just about to finish a blog post on our experience using the AMIs to create the PBX we use in our office so I'll include this...