Hi Ken,
Sorry to hear you had challenges login (SSH) to a Conductor after deployment.
I tried to reproduce the problem you are facing, but I have not been able to. I have launched two Conductors using the corresponding templates using both Juniper offerings in the AWS Marketplace:
- Session Smart Networking Platform (PAYG):
https://aws.amazon.com/marketplace/pp/prodview-l5kwn7puwvt3g?sr=0-1&ref_=beagle&applicationId=AWSMPContessa - Session Smart Networking Platform (BYOL):
https://aws.amazon.com/marketplace/pp/prodview-lz6cjd43qgw3c?sr=0-2&ref_=beagle&applicationId=AWSMPContessaI have been able to SSH to both Conductor successfully using the t128 username (the authentication method was publickey based).
- Which offer from the AWS Marketplace did you use?
- Do you still run into the same challenge when using the Conductor template?
If you can still reproduce the issue, we can setup a troubleshooting session to work through in real time if you agree.
Thank you very much.
Francisco.
------------------------------
Francisco Jose Mendez Cirera
Systems Engineer
------------------------------
Original Message:
Sent: 07-27-2022 10:42
From: Ken Pobst
Subject: AWS Conductor - SSH access
Hello,
I have deployed a conductor in AWS using the cloudformation template. The instance is up, but I am unable to ssh into the server. I receive the error -
No supported authentication methods available (server sent: publickey,gssapi-keyex,gssapi-with-mic)
I have generated a key pair in AWS, and saved the .pem file. I used PuttyGen to create a private key .ppk file and loaded that when trying to ssh into the server. I have tried the suggested username t128 as well as admin, root, centos, and ec2-user. All return the same error.
I created a new Centos Linux instance and using the same key pair/.ppk file was able to ssh into that instance with no problems(username=centos). Has anyone encountered a similar issue. Is t128 the correct username?
Thanks
Ken
------------------------------
Ken Pobst
------------------------------