Feature request: create a "vagrant" security group if none is specified

[mdub]

The default security group won't necessarily allow SSH access. vagrant-aws could/should create it's own security group allowing inbound SSH connections.

[tralamazza]

Should vagrant-aws modify the default security group or create a new one? and if it creates, with what name? It would have to be an unique one.

[deinspanjer]

I ran into this. I'd suggest using "vagrant" if it exists and creating it with ssh inbound only if it doesn't already exist.

[tralamazza]

I'm marking this as enhancement, but it should be implemented as an option, not the default behavior.

[tralamazza]

For now I'll test if any security group allows incoming TCP 22 d87df07 and print a warning (the test is not perfect yet).