Boto create launch configuration in different VPCs with fabric and boto

Question

I keep getting this error returned from my boto create_launch_configuration () cmd wrapped in a fabric job.

This is cmd:

if user_data != '':
security_groups=list('sg-d73fc5b2')

print "Trying to use this AMI [%s]" % image_ami

lc = LaunchConfiguration(
  name=launch_config_name,
  image_id=image_ami,
  key_name=env.aws_key_name,
  security_groups=security_groups,
  instance_type=instance_type
)

launch_config = autoscale_conn.create_launch_configuration(lc)

and this is the answer

<ErrorResponse xmlns="http://autoscaling.amazonaws.com/doc/2011-01-01/">
    <Error>
        <Type>Sender</Type>
        <Code>ValidationError</Code>
        <Message>No default VPC for this user</Message>
    </Error>
    <RequestId>4371fa63-e008-11e3-8554-ff532bce5053</RequestId>
</ErrorResponse>

We disabled VPC by default to try to minimize errors that apply to VPC through API calls. We have several VPCs working from the same account, and it would be useful to be able to specify VPCs via boto.

Does anyone know how I can set this default VPC for each task?

Answer 1

, . , VPC , , this. , :

AWS VPC Auto Scaling VPC , ...

.