Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 05-16-2016 08:32 PM - edited 09-16-2022 08:17 AM
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
Created 05-18-2016 09:21 PM
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?
Created 05-18-2016 10:25 AM
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.
Created 05-18-2016 09:21 PM
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?
Created on 05-18-2016 09:55 PM - edited 05-18-2016 09:56 PM
why director client and director server have different style of key usage.
Thanks Jayita for great help so far.