Gateway has no key pair associated?

Deadline
1

Hi,

Trying to ssh into my instances. When I click connect on the gateway in the aws console, it does not have the dashkey associated with it (as the docs seem to suggest it should). The actual render node instances do but they don’t have public IP’s

Am I missing something?

Thanks in advance

2

We manually inject the key into the “authorized_keys” file on startup if I remember correctly. Have you tried using the key already?

3

I tried using it with the SSH command but it rejected it

4

Heh. These forums are a bit too easy to throw out quick answers. I need to give more info in my replies here.

So, the “authorized_keys” file is populated by the dash key which is automatically generated into the AWS Portal Link installation directory. That’s outlined in the Connecting to a Linux AWS Portal Slave doc.

Because we don’t allow connecting directly to the AWS Portal instances from on-prem, you’ll have to use that doc to hop into the Gateway machine. From there, you’ll be able to use the key you have specified in the AWS console. You’ll have to copy it up to the Gateway however.