Thanks for the hints.
I finally solved the problem.
1. Stop the slackware instance in question.
2. unattach the root ebs volume
3. launch a fresh instance using default amazon AMI (with the access key name as amazon.pem here).
4. reattach the slackware root ebs volume to the new amazon as /dev/sdf
5. ssh into the new amazon instance and mount /dev/sdf to /mnt
6. copy the /root/.ssh/authorized_keys to /mnt/root/.ssh/
7. chroot /mnt and run 'passwd root' to reset the root password
8. umount /dev/sdf
9. reattach the slackware root ebs back to previous slackware instance in question as block /dev/sda1
10. Restart the slackware instance in question.
11. ssh -i amazon.pem root@dns_of_slackware_instance_here
All is fine, but weird to find out that an ubuntu kernel is running within slackware territory
.
Code:
root@cloud-slack:/etc/rc.d# cat /etc/slackware-version
Slackware 14.0
root@cloud-slack:/etc/rc.d# uname -a
Linux cloud-slack 3.2.0-29-virtual #46-Ubuntu SMP Fri Jul 27 17:23:50 UTC 2012 x86_64 Intel(R) Xeon(R) CPU E5645 @ 2.40GHz GenuineIntel GNU/Linux