question Re: Why does Cloudbreak create unique key pairs for every cluster in AWS? in Archives of Support Questions (Read Only)

Why does Cloudbreak create unique key pairs for every cluster in AWS?

mjrhee — Wed, 27 Jul 2016 23:50:29 GMT

I would like to better understand the need to have both a local SSH key on the Cloudbreak instance and an AWS key pair for every cluster that Cloudbreak spins up.

Re: Why does Cloudbreak create unique key pairs for every cluster in AWS?

Krisz — Thu, 28 Jul 2016 00:42:45 GMT

You don't need an SSH key pair on the Cloudbreak instance. You need to provide a public SSH key when you create a credential then you can use the private key for SSHing to the instances that Cloudbreak will launch. That SSH key can be anywhere.

Cloudbreak creates a new key pair for every cluster and generates a unique name for it to avoid name collision if many user use the same AWS account.

Re: Why does Cloudbreak create unique key pairs for every cluster in AWS?

mjrhee — Thu, 28 Jul 2016 01:43:58 GMT

Thanks, @khorvath. That's helpful.

Is there any way to obtain the AWS key pairs that are generated for each cluster?

Re: Why does Cloudbreak create unique key pairs for every cluster in AWS?

Krisz — Thu, 28 Jul 2016 02:07:35 GMT

Each key pair is generated from the public SSH key you provided and a unique name as you can see it here:

https://github.com/sequenceiq/cloudbreak/blob/master/cloud-aws/src/main/java/com/sequenceiq/cloudbreak/cloud/aws/AwsCredentialConnector.java#L71

so basically you have the public and private key as well.