start machine doesn't use the provider group

[Kapil Thangavelu]

all machines from a provider should be 'tagged' with the provider security group.

[Kapil Thangavelu (hazmat)]

afaics, this isn't the case. i think this was something unrelated, at least the daggers branch doesn't do anything different for launch and it works appropriately.

[Kapil Thangavelu (hazmat)]

so the origin of this was in the spike 'dagger', which had a 'default' environment, which atm resulted in a group called 'default' being created, which clashed with the existing group. After some discussion, i'm amending this bug to reflect that groups created in ec2 should be qualified with 'ensemble-' to prevent such collisions in the future.