pallet-aws creating an instance in a vpc

[mccraig mccraig]

hi,

i'm using : 

pallet : 0.8.0-SNAPSHOT : 988a36cafe63dbc2af382f85cac58de5351bf241

pallet-aws : 0.2.3

awaze : 0.1.2-SNAPSHOT : cb1efe5e3e08d9b6e2b3973ae361c7cce1912292

and i'm trying to create an instance in an AWS VPC with a node-spec like this :

(def ubuntu-1404-pv-ebs-200-node

  (node-spec

   :image {:image-id "ami-aec41cd9"  ;; alestic eu-west-1 ubuntu 14.04 PV EBS-SSD

           :os-family :ubuntu

           :os-version "14.04"

           :os-64-bit true

           :login-user "ubuntu"

           :key-name "mccraigkey"}

   :location {:location-id "eu-west-1b"}

   :hardware {:hardware-id "m3.large"}

   :provider {:pallet-ec2

              {

               :network-interfaces [{:subnet-id "subnet-c9ece28f"

                                     :device-index 0

                                     ;; :private-ip-address "192.168.0.90"

                                     :security-group-id "sg-a249e4c7"

                                     :delete-on-termination "true"}]

               }

              }))

and i'm getting an Exception :

com.amazonaws.AmazonServiceException: Network interfaces and an instance-level security groups may not be specified on the same request (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 19eaeb70-8e07-4375-99e6-f9004b62a647)

at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:820)

at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:439)

at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:245)

at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:8798)

at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:3999)

at com.palletops.awaze.ec2$run_instances.doInvoke(ec2.clj:7316)

at clojure.lang.RestFn.invoke(RestFn.java:423)

at pallet.compute.ec2.Ec2Service.run_nodes(ec2.clj:383)

at pallet.core.api$create_nodes.invoke(api.clj:308)

i presume because pallet is passing an instance-level security group named after the pallet-group... 

can i stop pallet specifying an instance-level security group, or do something else to work around this ?

thanks

:craig