question Re: Cloudera Director on AWS - Public Key Name field - bad syntax error in Archives of Support Questions (Read Only)

Cloudera Director on AWS - Public Key Name field - bad syntax error

shl7c — Thu, 16 Oct 2014 00:19:22 GMT

Anyone tried using Cloudera Director yet with AWS?

I can’t get the Public Key Name field to parse correctly. I’ve provided the name of the key, the name + .pem, and many other ideas. I always get:

The request cannot be fulfilled due to bad syntax.

Invalid environment: Invalid key name: personalKey

Anyone able to tell me what’s going on?

Thanks

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

GautamG — Thu, 16 Oct 2014 00:27:15 GMT

Hello. Thanks for using Director. Are you able to paste the config here for
review? You could also use pastebin if you prefer. Ensure you have redacted
your AWS credentials

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

Andrei Savu — Thu, 16 Oct 2014 04:39:43 GMT

There may be a mistmatch between the region you want to use and the one that has your key. Most of the resources in AWS are scoped to regions and can't be referenced globally.

The ".pem" extension is not needed.

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

shl7c — Fri, 17 Oct 2014 00:57:22 GMT

what config are you looking for?

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

shl7c — Fri, 17 Oct 2014 00:58:25 GMT

good idea. I did change the director Region option to match my director ec2 instance's Region. But that doesn't resolve the error.

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

shl7c — Fri, 17 Oct 2014 01:12:07 GMT

working now. tried same options as yesterday. not sure. but progress.

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

GautamG — Fri, 17 Oct 2014 01:34:15 GMT

Thanks for the feedback. So if we understand correctly, you modified
the region to one where the key exists and are now able to deploy your
cluster.

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

Natty — Fri, 24 Oct 2014 00:14:46 GMT

I ran into this issue as well. It seems like there's some sort of weird bug here. To provide some more details:

I plugged in the info about the key pair I was using on the Cloudera Director server, and left my region set to the default us-west-1. This failed with a pop-up error message that said "Invalid environment: Invalid key name: <keypair-name>" I swapped it to us-west-2 and it worked.

To the best of my knowledge, a keypair is not associated with a particular region, so this shouldn't occur.

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

Natty — Fri, 24 Oct 2014 00:15:34 GMT

Ah, nevermind. Somehow I missed Andrei's note.

Re: Cloudera Director on AWS - Public Key Name field - bad syntax error

Andrei Savu — Wed, 12 Nov 2014 22:07:23 GMT

Hi Natty! Have you been able to successfully run Director? Any feedback for future releases?