Accessing the EC2 instance even if you loose the pem file is rather easy. 

1. First, create a new instance by creating new access file, call it 'helper' instance with same region and VPC as of the lost pem file instance.

2. Now stop the lost pem file instance. Remember not to terminate instance but to stop it.

3. Goto EBS volumes, select the root volume of the lost pem file instance and detach.

4. Now again select the detached volume and this time you have to attach this volume to helper instance which we created before. Since helper instance already has a root volume by default as /dev/sda1, the newly attached volume will be secondary(eg: /dev/sdf).

5. Login to your helper instance with its pem file.

6. Execute below commands:

# mount /dev/xvdf1 /mnt
# cp /root/.ssh/.authorized_keys /mnt/root/.ssh/
# umount /mnt

7. Detach the secondary volume from helper instance. 

8. Again attach the volume back to our recovery instance. Start the instance. Terminate the helper instance.

Use helper instance pem file to log into recovery instance.

Subscribe To our news letter

Subscribe to our news letter to receive latest blog posts into your inbox. Please fill your email address in the below form.
*We don't provide your email contact details to any third parties
Latest Comments
Related Articles
Deploying Django project on Elastic Beanstalk Shirisha Gaddi

Here You can learn about how to setup and deploy a Django application to Amazon Web Services (AWS).

Tools/technologies used:
Python v2.7
Django ...

Continue Reading...
Using AWS Lambda with S3 and DynamoDB Dinesh Deshmukh

AWS lambda is handy tool for event driven computation, here we will learn how to configure and setup lambda function so to run our function ...

Continue Reading...
Easy and Fast way to implement AWS Lambda service Dinesh Deshmukh

We are going to use a simple application called Gordan to prevent creating a lambda function and triggering actions which involves time taking and repetitive ...

Continue Reading...