When spinning up instances in AWS I specify the following: aws.subnet_id="subnet-<xxxxxxxx>" # where <xxxxxxxx> is a private address space.
aws.associate_public_ip is left undefined so I believe it is false. vagrant up succeeds in creating and confirming ssh connectivity, vagrant ssh succeeds, ssh to the host succeeds. I change the config so that: aws.associate_public_ip = true Then vagrant chooses the public ip to ssh to instead of the private ip that is assigned from the subnet_id. I wish for vagrant to choose the private ip to use for ssh, and still a public facing interface as well. Does anyone know how? -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/75c81224-d4bf-4bd9-9b77-af282810b005%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
