Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Feature request: config parameter to specify whether public IP is assigned #205

Closed
jayfresh opened this issue Feb 21, 2014 · 3 comments
Closed

Comments

@jayfresh
Copy link

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.

@jayfresh
Copy link
Author

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?

@aweinograd
Copy link

+1 I have the opposite problem. All of my instances are in a subnet and I want a specific few to have public IPs

@rtyler
Copy link
Collaborator

rtyler commented May 30, 2014

I believe @pxsta's change fixes this

@rtyler rtyler closed this as completed May 30, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants