Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle a cluster without public IP Address #9

Open
armaseg opened this issue Dec 26, 2016 · 0 comments · May be fixed by #10
Open

Handle a cluster without public IP Address #9

armaseg opened this issue Dec 26, 2016 · 0 comments · May be fixed by #10

Comments

@armaseg
Copy link

armaseg commented Dec 26, 2016

As @dkamenov suggested on #7: when you are running in a VPC, "there really isn't any need to assign a public IP". So, you can change in the LauchConfig the parameter "AssociatePublicIpAddress": "false", nevertheless, as you don't have a public IP, the HOSTNAME parameter used to create the docker image will be resolved as "unavailable".
@armaseg armaseg linked a pull request Dec 26, 2016 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle a cluster without public IP Address armaseg/cloudformation-zookeeper
1 participant
@armaseg