AWS :vpc_id on connection.servers.create

77 views
Skip to first unread message

cl...@divaos.com

unread,
Jan 13, 2015, 2:06:32 PM1/13/15
to ruby...@googlegroups.com
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.

geemus (Wesley Beary)

unread,
Jan 13, 2015, 2:27:36 PM1/13/15
to ruby...@googlegroups.com
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.

--
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 ruby-fog+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Frederick Cheung

unread,
Jan 13, 2015, 2:53:44 PM1/13/15
to ruby...@googlegroups.com
You don't request an instance be launched into a vpc by specifying a vpc_id but by specifying a subnet_id (this comes from the underlying api Amazon provides). Would be helpful if fog warned about this parameter being ignored though.

Fred

Sent from my iPhone
--

cl...@divaos.com

unread,
Jan 13, 2015, 2:56:39 PM1/13/15
to ruby...@googlegroups.com
I can confirm that setting :subnet_id for connection.servers.create does in fact work.

Thanks a bunch.
Reply all
Reply to author
Forward
0 new messages