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.

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

Get aws_emr_cluster endpoint #10551

Closed
vkulov opened this issue Dec 6, 2016 · 5 comments · Fixed by #10563
Closed

Get aws_emr_cluster endpoint #10551

vkulov opened this issue Dec 6, 2016 · 5 comments · Fixed by #10563

Comments

@vkulov
Copy link

vkulov commented Dec 6, 2016

Hi,

I have successfully installed provisioned an EMR cluster using the aws_emr_cluster tag.

I'm having troubles accessing the EMR cluster endpoint or public DNS so I can use my cluster. I don't see an exported variable that points to any private or public address of my EMR cluster.

Please help. How do I use cluster if I don't have its IP or endpoint.

@Ninir
Copy link
Contributor

Ninir commented Dec 6, 2016

Hi @vkulov
Can you try using the master_public_dns attribute and tell us how it goes?

I think this is the thing you are looking for :)

@Ninir
Copy link
Contributor

Ninir commented Dec 6, 2016

It is live in #10563 !

@vkulov
Copy link
Author

vkulov commented Dec 7, 2016

Thank you. This is what I was looking for. :)

@DhaneshRaghavan
Copy link

any chance can we get the hostname of the master.

@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants