- Mais recentes
- Mais votos
- Mais comentários
Dear Friends,
Thank you for those took the initiative to suggest solution for me.
- My problem root cause was the passphase we assgined for the KeyPairA did not work, so, either my guys recorded wrong passphrase in our record, or something crazy caused this,
- so when we used KeyPairA, our Instance A keep asking password, and we tried all he standard password my company use non of it worked
- We follow the two guide shown in the OP , both did not solve my problem
- I think because the Instance A is on ubuntu 14.04 and all he automation or vol attachment uses Ubuntu22 (assumed only)
- What we did is we AMI the instance, detach the volume and attached in a TEMP Instance (which is Ubuntu 14) , mount the volume to a folder in sda1
- SSH to Temp Instance, do this two this, sudo cp .ssh/authorized_keys /mnt/tempvol/home/ubuntu/.ssh/authorized_keys sudo cp etc/ssh/sshd_configs /mnt/tempvol/home/ubuntu/etc/ssh/sshd_config few files from the etc/ssh/ folder copied over too, I can not for sure say which file, copy the whole thing might solve so
- after this unmount, detach and attach back to Instance A and the KeyPair used in Temp Instance should work (at least it worked for me)
In the past, you could take a snapshot of an instance, create an AMI from that snapshot, create a new keypair, then run an instance based on the AMI with the new SSH keypair.
Then, login with the new keypair.
You would lose an instance store with this approach.
Try SSM connect which will allow you in assuming a few things:
- Agent is installed (by default in most newer AMIs)
- EC2 Instance Profile grants permission to SSM agent
- Your account has access to connect via SSM.
Once these are met in EC2 right click and select "Connect".
You can read details on setting it up at: https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started.html
Thanks for taking a bit time to answer my question, apricate it, we could not get SSM to work on the Instance A (the instance that have passphrase-forgotten keypair) I have solved this issue and I explained how I solve this for others reference
Conteúdo relevante
AWS OFICIALAtualizada há 2 anos
I tried to detach the volume, attached to temp_instance, mount it, copy the autorized key details form temp_instance to mounted volume, test and facing same asking for pasword.
Problem solved and here updating why this idea did not work for me, Instance A was on Ubuntu 14.04 Temp Instance B which was used to attached Volume form Instance A was on Ubuntu 22
So, some miss match and the new SSH keypair which was generated in Ubuntu 22 did not work with Ubuntu 14, honestly I do not know the root cause, did not spend time as I solved my problem (as explained below)