Recovery from lost EC2 PEM file - Revision history

Mflavell: /* Cleanup */

2024-11-08T21:07:06Z

Cleanup

← Older revision		Revision as of 21:07, 8 November 2024
Line 63:		Line 63:

	==Cleanup==		==Cleanup==
	Terminate ~~and~~ the recovery instance		Terminate the recovery instance

Mflavell at 21:06, 8 November 2024

2024-11-08T21:06:28Z

← Older revision		Revision as of 21:06, 8 November 2024
Line 1:		Line 1:
	=Introduction=		=Introduction=

	This ~~is a~~ 10-step process ~~that creates a new~~ .~~PEM file, and copies it to the old EBS volue~~.		This 10-step process will enable access to an EC2 instance you have lost access to.

			This assumes basic AWS / Linux knowledge.


Line 18:		Line 20:
	==Make recovery instance accessable==		==Make recovery instance accessable==

	Give the recovery instance an ~~exernal~~ IP and assign security groups.		Give the recovery instance an external IP and assign security groups.


Line 29:		Line 31:
	==Detatch the root vloume==		==Detatch the root vloume==

	~~Detatch~~ the root ~~valoue~~ from the old instance		Detach the root volume from the old instance
	Attach it to the recovery instance - it is best to use /xvdf		Attach it to the recovery instance - it is best to use /xvdf

Mflavell at 21:04, 8 November 2024

2024-11-08T21:04:30Z

← Older revision		Revision as of 21:04, 8 November 2024
Line 1:		Line 1:
	=Introduction=		=Introduction=

	This is a 10 step process that creates a new .PEM file, and copies it to the old EBS volue.		This is a 10-step process that creates a new .PEM file, and copies it to the old EBS volue.


	==Take notes==		==Take notes==

	Note down the AZ of the problem server, ~~it's~~ instance name and the ID of the root volume.		Note down the AZ of the problem server, its instance name, and the ID of the root volume.


	==Make a recovery instance==		==Make a recovery instance==
Line 12:		Line 13:
	Create a new instance in the same AZ		Create a new instance in the same AZ
	Create a new key pair for the instance and download it.		Create a new key pair for the instance and download it.
	~~Dont loose~~ the .PEM file again!!!		Don't lose the.PEM file again!!!


	==Make recovery instance accessable==		==Make recovery instance accessable==

	Give the recovery instance an exernal IP and assign security groups.		Give the recovery instance an exernal IP and assign security groups.


	==Stop the old instance==		==Stop the old instance==
Line 22:		Line 25:
	Stop the old instance.		Stop the old instance.
	Don't delete it!		Don't delete it!


	==Detatch the root vloume==		==Detatch the root vloume==
Line 27:		Line 31:
	Detatch the root valoue from the old instance		Detatch the root valoue from the old instance
	Attach it to the recovery instance - it is best to use /xvdf		Attach it to the recovery instance - it is best to use /xvdf


	==Mount the root volume==		==Mount the root volume==

	use lsblk to find the root volume, it shoud be /dev/xvdf1		use lsblk to find the root volume, it shoud be /dev/xvdf1


	==Make the Magic happen==		==Make the Magic happen==
Line 39:		Line 45:
	sudo mount /dev/xvdf1 /mnt/recovery_vol		sudo mount /dev/xvdf1 /mnt/recovery_vol
	cp .ssh/authorized_keys /mnt/recovery_vol/home/ubuntu/.ssh/authorized_keys		cp .ssh/authorized_keys /mnt/recovery_vol/home/ubuntu/.ssh/authorized_keys


	==Move the volume back==		==Move the volume back==

	Stop the ~~recoverey~~ instance		Stop the recovery instance
	Detach the volume from the old server		Detach the volume from the old server
	Attach the volume back on the old server		Attach the volume back on the old server


	==Start the old server==		==Start the old server==
Line 50:		Line 58:
	Sart the original instance		Sart the original instance
	Connect with the new .PEM file		Connect with the new .PEM file


	==Cleanup==		==Cleanup==
	Terminate and the recovery instance		Terminate and the recovery instance

Mflavell: /* Move the volume back= */

2024-11-08T21:03:33Z

Move the volume back=

← Older revision		Revision as of 21:03, 8 November 2024
Line 40:		Line 40:
	cp .ssh/authorized_keys /mnt/recovery_vol/home/ubuntu/.ssh/authorized_keys		cp .ssh/authorized_keys /mnt/recovery_vol/home/ubuntu/.ssh/authorized_keys

	==Move the volume back===		==Move the volume back==

	Stop the recoverey instance		Stop the recoverey instance

Mflavell: /* Mount the root volume= */

2024-11-08T18:25:59Z

Mount the root volume=

← Older revision		Revision as of 18:25, 8 November 2024
Line 28:		Line 28:
	Attach it to the recovery instance - it is best to use /xvdf		Attach it to the recovery instance - it is best to use /xvdf

	==Mount the root volume===		==Mount the root volume==

	use lsblk to find the root volume, it shoud be /dev/xvdf1		use lsblk to find the root volume, it shoud be /dev/xvdf1


	==Make the Magic happen==		==Make the Magic happen==

Mflavell: /* =Make the Magic happen */

2024-11-08T18:25:53Z

=Make the Magic happen

← Older revision		Revision as of 18:25, 8 November 2024
Line 33:		Line 33:


	===Make the Magic happen==		==Make the Magic happen==

	Copy the certs:		Copy the certs:

Mflavell: /* Mount the root volume= */

2024-11-08T18:25:46Z

Mount the root volume=

← Older revision		Revision as of 18:25, 8 November 2024
Line 33:		Line 33:


	===Make the Magic happen===		===Make the Magic happen==

	Copy the certs:		Copy the certs:

Mflavell: /* Make recovery instance accessable= */

2024-11-08T18:25:41Z

Make recovery instance accessable=

← Older revision		Revision as of 18:25, 8 November 2024
Line 14:		Line 14:
	Dont loose the .PEM file again!!!		Dont loose the .PEM file again!!!

	==Make recovery instance accessable===		==Make recovery instance accessable==

	Give the recovery instance an exernal IP and assign security groups.		Give the recovery instance an exernal IP and assign security groups.


	==Stop the old instance==		==Stop the old instance==

Mflavell at 18:25, 8 November 2024

2024-11-08T18:25:20Z

← Older revision		Revision as of 18:25, 8 November 2024
Line 1:		Line 1:
	~~Step 1:~~		=Introduction=

	~~Before Starting~~, ~~we must have~~ to ~~note down~~ the ~~original instance availability zone (us-east-1a), Instance name and id you can find this on EC2 dashboard after selecting your instance~~.		This is a 10 step process that creates a new .PEM file, and copies it to the old EBS volue.

	~~Step 2:~~

	~~Launch a new instance with same availability zone (AZ) as we note down before you can select Availability Zone (AZ) at 3rd step (Configure Instance) while creating an instance.~~		==Take notes==

			Note down the AZ of the problem server, it's instance name and the ID of the root volume.

			==Make a recovery instance==

	~~Step 3 :~~		Create a new instance in the same AZ
			Create a new key pair for the instance and download it.
			Dont loose the .PEM file again!!!

	~~At last while we are launching~~ instance we will see the key-pair section (at last) from there we have an option for creating and downloading a new key pair and then we can launch the instance. Now we have to login with a newly created instance using new key-pair.		==Make recovery instance accessable===

	~~Step 4:~~		Give the recovery instance an exernal IP and assign security groups.

	As we know each instance contain one or more EBS volumes, that is instance storage, you have find out EBS volume of lost private-key instance, for that click on Instance Description and find , ‘ Root device ‘
	~~vol-02ee64fe9ba5c7302~~

			==Stop the old instance==

			Stop the old instance.
			Don't delete it!

	~~Step 5:~~		==Detatch the root vloume==

	~~Now click on EBS ID this will redirect to EBS Volume page and give a name to this EBS volume so you can identify each volumes. Then we have to detach this volume~~ from the ~~original instance (production~~ instance~~) for that we have~~ to ~~stop instance (left click on~~ instance ~~select Instance state~~ -~~> click stop).~~		Detatch the root valoue from the old instance
			Attach it to the recovery instance - it is best to use /xvdf

	~~Step 6:~~		==Mount the root volume===

	~~Once production instance is stopped, detach EBS volume (left click on volume and select detach) and attach it~~ to ~~the newly created instance.~~		use lsblk to find the root volume, it shoud be /dev/xvdf1
	~~Note: If you didn’t~~ find the ~~newly created instance in Attach Instance wizard than something wrong with your Availability Zone (AZ)~~

	~~Step 7:~~

	~~After Attaching EBS to~~ the ~~newly created instance, now you are able to connect this EBS using newly created instance. For that do log in to newly created instance terminal.~~		===Make the Magic happen===

	~~Step 8~~:		Copy the certs:

	~~After that we have to check whether new EBS is attached successfully or not with new instance you can check by running below command.~~		sudo mkdir /mnt/removery_vol
	~~lsblk~~ ~~– This command is used for determining if the volume is partitioned~~		sudo mount /dev/xvdf1 /mnt/recovery_vol
			cp .ssh/authorized_keys /mnt/recovery_vol/home/ubuntu/.ssh/authorized_keys

			==Move the volume back===

			Stop the recoverey instance
			Detach the volume from the old server
			Attach the volume back on the old server

	~~Step 9:~~		==Start the old server==

	~~If you find another disk than EBS is attached successfully, now we have to replace old authorized_eys (production or lost .pem)~~ with new ~~created authorized_keys for that run below commands~~.		Sart the original instance
			Connect with the new .PEM file

			==Cleanup==
			Terminate and the recovery instance
	~~1. sudo mkdir /mnt/removery_vol~~
	~~2. sudo mount /dev/xvdf1 /mnt/recovery_vol~~
	~~3. cp .ssh/authorized_keys /mnt/recovery_vol/home/ubuntu/.ssh/authorized_keys~~

	~~Step 10:~~

	~~After successfully changes on authorized_keys, detach this volume from new instance~~ and ~~attach it with Production (lost private-key)~~ instance~~, after attaching now start production instance.~~

	~~Step 11:~~

	~~Congratulations, now you can connect to this instance using newly created instance Private key (.pem) file.~~

	~~Don't lose it again... unless you like doing this!~~

Mflavell at 18:13, 8 November 2024

2024-11-08T18:13:10Z

← Older revision		Revision as of 18:13, 8 November 2024
Line 57:		Line 57:

	Congratulations, now you can connect to this instance using newly created instance Private key (.pem) file.		Congratulations, now you can connect to this instance using newly created instance Private key (.pem) file.

			Don't lose it again... unless you like doing this!