move_ec2_instance
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
move_ec2_instance [2017/07/26 19:38] – [Move EC2 Instance] walkeradmin | move_ec2_instance [2017/07/26 20:22] – [Delete Old AMI] walkeradmin | ||
---|---|---|---|
Line 231: | Line 231: | ||
\\ | \\ | ||
\\ | \\ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== The Original EC2 Instance ==== | ||
+ | \\ | ||
+ | We didn't actually move the EC2 Instance, we simply made a backup, copied the backup to a new AZ and created a new EC2 Instance from that backup. | ||
+ | \\ | ||
+ | \\ | ||
+ | What this means is that the EC2 Instance that you originally had is still there, and if you left it running, it is still running and potentially costing you money. | ||
+ | \\ | ||
+ | \\ | ||
+ | From the dashboard, select the AZ where your original EC2 Instance was created (US East (Ohio) in my case.) | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | You can't see instances in different AZs on one page unfortunately, | ||
+ | \\ | ||
+ | \\ | ||
+ | So here we are, back at the original AZ where our original EC2 Instance is. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | We have to stop this instance for two reasons. It is using a server, so this is incurring a cost, yes we could just stop it and leave it BUT, it is also consuming hard disk space. Even worse is that we are using a lot of space now because of the copy process, consider this: | ||
+ | \\ | ||
+ | \\ | ||
+ | Original EC2 Instance is using..< | ||
+ | The AMI we created is using.....< | ||
+ | The AMI copy is using...........< | ||
+ | The new EC2 Instance is using...< | ||
+ | \\ | ||
+ | Total...........................< | ||
+ | \\ | ||
+ | \\ | ||
+ | Our free allowance is 30GB, so we need to do some cleaning up. | ||
+ | \\ | ||
+ | \\ | ||
+ | We need to do the following: | ||
+ | \\ | ||
+ | \\ | ||
+ | Stop the old EC2 Instance.\\ | ||
+ | Delete the old EC2 Instance.\\ | ||
+ | Delete the AMI Image.\\ | ||
+ | Delete the AMI Copy Image.\\ | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Stop the old EC2 Instance ==== | ||
+ | \\ | ||
+ | From the console, navigate to the old EC2 Instance. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Select <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | You will see a warning page about stopping an Instance. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Select <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | It might take a minute or two, but the instance will stop. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Keep checking the console until the instance status is <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ==== Delete old EC2 Instance ==== | ||
+ | \\ | ||
+ | To delete the old EC2 Instance, from the EC2 Console page. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Select <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | You will get a warning about terminating an instance. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Select <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Check the status of your old EC2 to check termination is complete. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | This might take a minute to two. | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ==== Delete Old AMI ==== | ||
+ | \\ | ||
+ | Naviage back to the EC2 Console (ensure you are on your old AZ) | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | From the menu on the right, go down to <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Your AMI will be listed in the main page. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Select <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | You will get a warning about deregistering an AMI. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Select <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
move_ec2_instance.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1