Doesn't support AWS VPC

[xbeta]

I got this error when trying to bootstrap on AWS VPC

± vagrant up --provider=aws
Bringing machine 'default' up with 'aws' provider...
==> default: HandleBoxUrl middleware is deprecated. Use HandleBox instead.
==> default: This is a bug with the provider. Please contact the creator
==> default: of the provider you use to fix this.
==> default: The cookbook path '/Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default' doesn't exist. Ignoring...
Updating Vagrant's berkshelf: '/Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default'
DEPRECATED: Your Berksfile contains a site location pointing to the Opscode Community Site (site :opscode). Site locations have been replaced by the source location. Change this to: 'source "https://supermarket.getchef.com"' to remove this warning. For more information visit https://github.com/berkshelf/berkshelf/wiki/deprecated-locations
Resolving cookbook dependencies...
Fetching 'docker' from git://github.com/bflad/chef-docker.git (at master)
Fetching 'mesos' from git://github.com/everpeace/cookbook-mesos.git (at master)
Fetching cookbook index from https://supermarket.getchef.com...
Using 7-zip (1.0.2)
Using apt (2.6.0)
Using ark (0.9.0)
Installing aufs (0.1.1)
Using build-essential (2.0.6)
Using chef_handler (1.1.6)
Installing device-mapper (0.1.0)
Installing dmg (2.2.0)
Using docker (0.35.2) from git://github.com/bflad/chef-docker.git (at master)
Installing dpkg_autostart (0.1.10)
Installing git (4.0.2)
Installing golang (1.4.0)
Installing homebrew (1.9.0)
Installing iptables (0.14.0)
Installing java (1.28.0)
Installing lxc (1.1.8)
Installing maven (1.1.0)
Using mesos (0.2.1) from git://github.com/everpeace/cookbook-mesos.git (at master)
Installing modules (0.2.0)
Using ohai (2.0.1)
Installing python (1.4.6)
Using runit (1.5.10)
Installing sysctl (0.6.0)
Installing ulimit (0.3.2)
Installing windows (1.34.6)
Using yum (3.3.2)
Using yum-epel (0.5.1)
Vendoring 7-zip (1.0.2) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/7-zip
Vendoring apt (2.6.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/apt
Vendoring ark (0.9.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/ark
Vendoring aufs (0.1.1) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/aufs
Vendoring build-essential (2.0.6) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/build-essential
Vendoring chef_handler (1.1.6) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/chef_handler
Vendoring device-mapper (0.1.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/device-mapper
Vendoring dmg (2.2.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/dmg
Vendoring docker (0.35.2) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/docker
Vendoring dpkg_autostart (0.1.10) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/dpkg_autostart
Vendoring git (4.0.2) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/git
Vendoring golang (1.4.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/golang
Vendoring homebrew (1.9.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/homebrew
Vendoring iptables (0.14.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/iptables
Vendoring java (1.28.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/java
Vendoring lxc (1.1.8) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/lxc
Vendoring maven (1.1.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/maven
Vendoring mesos (0.2.1) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/mesos
Vendoring modules (0.2.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/modules
Vendoring ohai (2.0.1) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/ohai
Vendoring python (1.4.6) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/python
Vendoring runit (1.5.10) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/runit
Vendoring sysctl (0.6.0) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/sysctl
Vendoring ulimit (0.3.2) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/ulimit
Vendoring windows (1.34.6) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/windows
Vendoring yum (3.3.2) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/yum
Vendoring yum-epel (0.5.1) to /Users/xbeta/.berkshelf/default/vagrant/berkshelf-20141002-37331-du312d-default/yum-epel

==> default: Warning! The AWS provider doesn't support any of the Vagrant
==> default: high-level network configurations (`config.vm.network`). They
==> default: will be silently ignored.
==> default: Launching an instance with the following settings...
==> default:  -- Type: m3.medium
==> default:  -- AMI: ami-33db9803
==> default:  -- Region: us-west-2
==> default:  -- Keypair: jenkins-builder
==> default:  -- Security Groups: ["corp", "mesos"]
==> default:  -- Block Device Mapping: []
==> default:  -- Terminate On Shutdown: false
==> default:  -- Monitoring: false
==> default:  -- EBS optimized: false
==> default:  -- Assigning a public IP address in a VPC: false
VagrantPlugins::AWS::Errors::FogError: There was an error talking to AWS. The error message is shown
below:

InvalidParameterCombination => VPC security groups may not be used for a non-VPC launch

[everpeace]

InvalidParameterCombination => VPC security groups may not be used for a non-VPC launch

It seems that this error message tells that you tried to spin up an instance in non-VPC area even though you specified VPC security groups. Are you sure to set subnet-id which is associated with security groups which you specified??

[xbeta]

@everpeace Well, because aws.subnet_id is not define in standalone/Vagrantfile. I'll try to add it and see if it works.

[everpeace]

@xbeta oh, you used standalone. Standalone doesn't assume to use VPC. So, you have to set normal security groups.

[xbeta]

@everpeace Sure. I added and it does created the instance in EC2, but the ssh waits seems to be stuck, it waits forever and hang there. Except I could manually ssh in and EC2 console shows that's running. Any thoughts on that?

[everpeace]

@xbeta maybe you have to check your aws_config.yaml again. Did you set ssh_private_key_path correctly??

vagrant's debug mode would also guide you to solve the issue.

$ vagrant up --debug

[xbeta]

@everpeace you are right, it's the bad keypair. It's OK now. The provisioning is running. By the way, why wouldn't standalone be allowed to run within VPC ? (Testing purpose)

[everpeace]

@xbeta Yeah, you're right. Definitely, I should support standalone within VPC. I will take this task in this weekend maybe. I would be really happy if you could issue pull request for this :-)

[everpeace]

I created a task for supporting VPC in standalone. so I closed this.

[xbeta]

@everpeace
btw, I received this error, not sure it's related or not:
https://gist.github.com/xbeta/c72aecb06075fa422984