Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Cloudera director launches workers and master using own key

Solved Go to solution

Cloudera director launches workers and master using own key

Explorer

 

All workers and masters are launch using own key with name cloudera-aws-quickstart-mm-dd-YYYY on the cluster launcher node. This key pair will be used during the launch of EDH nodes.

 

How to get that key as without key i can't ssh to those workers and master right ?

Why extra key is used ?

 

Regards,

Kartik

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Cloudera director launches workers and master using own key

Contributor

Hi, 

 

If you're using the generated config file, the key referenced by it should be available on the filesystem of your Director instance. The filesystem path should be mentioned in the config file that was generated (labeled "privateKey").

 

Or else could you try running 'find' for it, by name, on the filesystem?

3 REPLIES 3
Highlighted

Re: Cloudera director launches workers and master using own key

Explorer

still don't  know the answer, why cluster created by cloudera-director using bootstrap aws.reference.conf are linked to cloudera-aws-quickstart-mm-dd-YYYY while cluster created by UI is using my account pem key.

Re: Cloudera director launches workers and master using own key

Contributor

Hi, 

 

If you're using the generated config file, the key referenced by it should be available on the filesystem of your Director instance. The filesystem path should be mentioned in the config file that was generated (labeled "privateKey").

 

Or else could you try running 'find' for it, by name, on the filesystem?

Re: Cloudera director launches workers and master using own key

Explorer

why director client and director server have different style of key usage.

 

Thanks Jayita for great help so far.