07-25-2017 12:28 PM
Thank you so much for your information.
So i am currently testing it. But I have hosted my cloudera single node environment on AWS EC2 instance.
I also own a domain on godaddy www.datacloudera.com. I have changed the nameserver to the one in AWS DNS Zone. Should the hosted zone be public ? or private in a vpc?
But i am not sure how to proceed next. What are the steps which i should take post this one ?
07-25-2017 12:38 PM
This depends on your corporate network configuration. Private zones are only resolvable within your AWS VPC, so unless you have your corporate network connected to your VPC and DNS peering properly configured, it is often easier to configure DNS in your public zone. You will want to set both cdsw.datacloudera.com and *.cdsw.datacloudera.com A name records to your master node. Within AWS, it's often more flexible to point this records to an EIP so you can attach it to different nodes over time.
07-25-2017 12:43 PM
Thanks for the quick reply. This is my personal setup and I am a starter in this area. Will you be able to help me with baby steps ? APologies for being too demanding :)
what i have now done is created a DNS is route53 in public zone. And i have updated the name servers into my domain at godaddy.
Now what should i do next in AWS? Create a record set in AWS?
And what should i do on my EC2 instance where the Workbench has been installed?
11-29-2017 12:56 AM
Thanks for the explanation.
I am using cdsw for testing only.
So, i choosen the domain service with extention of xip.io
But , while i am launching the session it displaying as below :
It stays in schedulling phase and Terminal also not opening in client side.
Firewall restriction also i have done.
Please guide me