This should be the instance.id, not the name
Added a security group pool-like object

For easier categorizing
Both vpc and ec2 connection managers share name

The attribute name should be the same, to simplify things
This is not a key you need for ec2 creation

Better if we just rename it to vpc_id to avoid doing more stuff later
Revamped the security group stuff and vpc bits

Turns out it didn't quite work the way it was. And security group names
are not unique between ec2 and vpc. So have to make the distinction
between the two of them and still send one of the two depending if it is
ec2 or vpc. Quite a mess really.
Expose the security group drivers
Not needed because they share ``awsconnection``
Import security groups as securitygroup objects
Updating the creation process

Related: amazon now gives you up to 8 drives, apparently