You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.
I'm creating a VPC in which I'm putting a web server and a db server. I don't want the db server to have a public IP address, so it would be great if I could specify that in my Vagrantfile config.
Having requested this, I did find that you can get an instance to not have a public IP by default by assigning it to a non-default subnet (i.e. one you create). The downside of this is that vagrant hangs at the "waiting for SSH to become available" since the instance is not accessible over public IP. Is there a way around that?
I'm creating a VPC in which I'm putting a web server and a db server. I don't want the db server to have a public IP address, so it would be great if I could specify that in my Vagrantfile config.
According to http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html (right at the bottom of the page), there is an API parameter for specifying whether an instance in a VPC gets assigned a public IP or not:
"Use the NetworkInterface.n.AssociatePublicIpAddress parameter with the RunInstances request."
Thanks,
J.
The text was updated successfully, but these errors were encountered: