Support AWS in addition to VirtualBox

[devalih]

Steps to provision to aws/ec2 machine.

• Go to aws/IAM https://console.aws.amazon.com/iam/home?region=us-west-1#users console
• Create a new access key and save the KEY and SECRET
• Go to aws/region:us-east-1/ec2 keypairs page https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#KeyPairs:sort=keyName
• Create a new pair and call it vagrant
• Save vagrant.pem file into your home

$ cat > env.sh
export AWS_KEY=""
export AWS_SECRET=""
export AWS_KEYNAME="vagrant"
export AWS_KEYPATH="~/vagrant.pem"
CTRL+D

$ chmod +x env.sh
$ . ./env.sh
$ vagrant up --provider=aws

[usernamenumber]

Is this ready for merging?

[devalih]

Yes it is.
But I would prefer that someone else try it locally before merging.

[usernamenumber]

I haven't used AWS much before so I'm in the process of getting all my account stuff set up. If someone can test before I can, please do. Otherwise I'll try to get to it and review and merge by the end of the week unless there's a reason to need it done sooner.

[usernamenumber]

I am still having trouble setting up AWS. When I try to go to the management console, I get a "We need additional information..." page, but following the instructions on it has not helped. I've submitted a support request. Sorry for the delay!

[usernamenumber]

Well, I've gotten my AWS account set up (I think), but now I'm getting a weird error trying to install the vagrant-aws plugin (details below, unrelated to your patch, of course). This PR has been waiting for a long time, and it shouldn't be able to break anything even if something is wrong, so I'm going to just merge it. I'm also going to create my own PR for a script I wrote to make deployment a bit friendlier.

[usernamenumber]

See #26