[JCLOUDS-987] AWS EC2: if specifying subnet ID, security groups are not created

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 2.0.0
• Component/s: jclouds-compute
• Labels: aws-ec2
• Assignee: Ignasi Barrera
• Reporter: Richard Downer
• Created: 11/Aug/15 12:53
• Updated: 29/Oct/15 00:56
• Resolved: 29/Oct/15 00:56

Description

If the template options for an EC2 instance specify a subnet ID, then jclouds will not create any security groups.

This is defined in this piece of code:
https://github.com/jclouds/jclouds/blob/master/providers/aws-ec2/src/main/java/org/jclouds/aws/ec2/compute/strategy/CreateKeyPairPlacementAndSecurityGroupsAsNeededAndReturnRunOptions.java#L182

The if statement checks if subnet has been set; the "false" part causes security groups to be created, but the "true" part does not - therefore if the subnet ID is set there are no security groups created.

The workaround is for the user to define the security groups ahead of time and specify the security group IDs in the template options.