I found the solution - the undocumented 'ssh_host_attribute' attribute which is used in the code below allows control of which address to try first.
PR: https://github.com/mitchellh/vagrant-aws/pull/368 On Wednesday, 4 March 2015 15:56:37 UTC+11, Amos S wrote: > > Our setup: VPC network, connected from the office via Direct Connect. > > A colleague is trying to setup a Vagrant box inside this AWS VPC using > vagrant-aws which requires a public IP in order to access external > resources. > > When he tried to add 'aws.elastic_ip = true' or 'aws.associate_public_ip = > true', vagrant brought the box up alright but keeps trying to ssh into it > through the public IP, not through the private IP which is perfectly > accessible directly. > > The ssh port on the public IP is blocked, of course, so Vagrant fails. > > Is there a way to tell Vagrant to keep using the private IP even though it > assigned it an external IP? > > Digging through vagrant-aws' source code didn't come up with anything for > me. > > Thanks, > > --Amos > -- You received this message because you are subscribed to the Google Groups "Vagrant" 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.
