This is confusing little bit with Group and Security group. As VPC is like a group, or more than just group. Also using creatInGroup duplicate that purpose. Where as with AWS/EC2 it jsut add confusion.
In order to user VPC and Security group, you need to use subnet under the VPC. That way you can create node in VPC/subnet with security group in that VPC. *template.getOptions().as(AWSEC2TemplateOptions.class).subnetId(subnetId).securityGroupIds(securityGroupIdArr);* *Set<? extends NodeMetadata> nodes = computeService.createNodesInGroup(GroupName, count, template);* On Wed, Oct 1, 2014 at 9:28 AM, Yaron Rosenbaum <[email protected]> wrote: > Hi > > If I understand correctly, I have to specify a VPC (since I don't have a > default one), and the only way of doing it is by specifying a subnet. That, > however, ignores my request for specific security groups - and only adds me > to the 'default' one. > > https://jclouds.apache.org/guides/aws-ec2/ > "To create nodes in a subnet under Amazon VPC add the following option to > your template options. Note that VPCs and Security Groups are mutually > exclusive." > > Why? > > (Y) > > >
