Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

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

avatar
Explorer

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

1 ACCEPTED SOLUTION

avatar
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.

Regards,
Gautam Gopalakrishnan

View solution in original post

9 REPLIES 9

avatar
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

Regards,
Gautam Gopalakrishnan

avatar
Explorer
what config are you looking for?

avatar
Master Collaborator

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. 

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

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

avatar
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.

Regards,
Gautam Gopalakrishnan

avatar
New Contributor

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.

avatar
New Contributor

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

avatar
Master Collaborator

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