When manually assigning nodes to use a security group (SG) that is configured on a different virtual private cloud (VPC) during launch the plugin always tries to attach the node to default subnet, even when a vpc ID or subnet ID is specified in the networks option.

This causes the instance to not be created since the requested subnet is not part of the SG.