Open SSH Session Error

[IvanFarkas]

Open SSH Session Error

• Error 1: error opening ssh session: The process Cannot access the file 'C:\Users[user]\AppData\Temp]tmp99F1B.tmp' because it is being used by another process.
• Error 2: error opening ssh session: Unknown error converting pem to ppk file. Exit Code: -1073741819

To Reproduce

• Create a Serverless ASP.NET Core 5 (Web API in container)
• Publish
• AWS Explorer -> AWS Elastic Beanstalk -> [Application] (Serverless) -> [Environment] (Serverless-dev)
• Click Connect to Instance
• Enter Private Key
• Click OK
• Get Error 1: error opening ssh session: The process Cannot access the file 'C:\Users[user]\AppData\Temp]tmp99F1B.tmp' because it is being used by another process.
• Close Error.
• Click OK again.
• Get Error 2: error opening ssh session: Unknown error converting pem to ppk file. Exit Code: -1073741819

Expected behavior SSH session like the one in the SSH_CLI image.

Screenshots Project Type

SSH UI

SSH CLI

Error 1

Error 2

Computer (please complete the following information):

• Windows Version: Win10Pro (21390.1010)
• Visual Studio Version: VS 2019 Pro (16.11.0)
• AWS Toolkit for Visual Studio Version: 1.21.2.0

Additional context

[shruti0085]

Thanks for reaching out @IvanFarkas . Unfortunately I was unable to reproduce your issue completely.

I was able to reproduce Error 2 - Unknown error converting pem to ppk file when I provided an incorrect key-pair(exactly like the one in the image attached in the issue description) when connecting to the instance attached to my Beanstalk environment.

A couple of questions:

• Can you confirm that in this textbox you are providing the contents of the EC2 Key-Pair that you selected while publishing this application to beanstalk through the toolkit?
• Also can you confirm that your EC2 Key-pair is in the correct format ? EC2 Private key supports RSA and must be in PEM format as indicated here. The image linked above is providing a dummy private key which has a beginning line as BEGIN OPENSSH PRIVATE KEY as opposed to BEGIN RSA PRIVATE KEY.

Lastly, can you re-try with a new VS instance after closing all previous/existing VS instances?

[awschristou]

Version 1.44.0.0 of the Toolkit was released today. It contains a fix for a bug that was causing SSH connections from the AWS Toolkit to fail with PEM to PPK conversion issues.