We needed to make special patches to get those working, it may be that we just haven't done this yet. I think you can get VPC by setting security group and/or subnet here instead of VPC explicitly, but I could be wrong (and we might need patches). Unfortunately I don't have much directly experience here to draw from.
On Tue, Jan 13, 2015 at 1:06 PM, <[email protected]> wrote: > I do not have a default VPC on AWS. I need to launch servers in a > specific VPC. > > I can pass :vpc_id to `connection.security_groups.create` and it works as > expected. > > However, passing :vpc_id to `connection.servers.create` seems to have no > effect. > I get this back from AWS: > > 'response_call': VPCIdNotSpecified => No default VPC for this user > (Fog::Compute::AWS::Error) > > Has anyone made `servers.create` work with a specific :vpc_id ? Any help > is appreciated. > > -- > You received this message because you are subscribed to the Google Groups > "ruby-fog" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ruby-fog" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
