Recently encounter an error/discrepancy in Instance KeyPair.
Yes I did terminate the old instance and start again. Also downloaded GIT Bash as advised in tutorial, etc. and follow it carefully to get new KeyPair again.
Still got errors which need refer to technical people as evident the tutorials and what I got are VERY DIFFERENT RESULTS. Not as expected in tutorials.
My concerns are as follows : (1) This is what results I got when connecting to instance : " ozzma@DESKTOP-GVQNLLP MINGW64
~ $ ssh -i "MynewKeyPair.pem" email@example.com Warning: Identity file MynewKeyPair.pem not accessible: No such file or directory. The authenticity of host 'ec2-18-191-55-43.us-east-2.compute.amazonaws.com (126.96.36.199)' can't be established. ECDSA key fingerprint is SHA256:wsNKuKipM2bHb+9enNAqztd3Zbdbq7WB1JNGNNCBySw. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'ec2-18-191-55-43.us-east-2.compute.amazonaws.com,188.8.131.52' (ECDSA) to the list of known hosts. Connection closed by 184.108.40.206 port 22 "
(2) Notice it is ECDSA key is different to RSA Key as described in Tutorials and maybe instance is expecting a RSA Key type, not a ECDSA as stated ??? Pls confirm what happen here???
(3) This is why when I used PUTTY , also got different responses as they state was RSA to convert the Private Key to Putty protocol.Putty message " Could NOT load private key. Not recognised key file format. Key is WRONG TYPE." Putty confimed not RSA type key. I proved above it was ECDSA.
(4) When the Private Key file was obtained, should it be opened first and saved? Or just save it without open it ? Reason got message saying " No file exist or wrong Directory " ??? Pls explain why ?
These are inbuilt errors in your Instance installation programs that mismatch what are expected to what actually got as the outputs. Please refer these ERRORS to technical/programmers/etc to fix properly. Got so frustrated when results does not match the expected outcome.
Hope to hear some responses from the experts soon.