User Tools

Site Tools


move_ec2_instance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
move_ec2_instance [2017/07/26 18:37] – [Move EC2 Instance] walkeradminmove_ec2_instance [2017/07/26 19:40] – [Move EC2 Instance] walkeradmin
Line 80: Line 80:
 \\  \\ 
 \\  \\ 
-{{ :aws_move_instance_005.jpg?600 |}}+{{ :aws_move_instance_005.jpg?900 |}}
 \\  \\ 
 \\  \\ 
Line 89: Line 89:
 \\  \\ 
 \\  \\ 
-{{ :aws_move_instance_006.jpg?600 |}} +{{ :aws_move_instance_006.jpg?900 |}}
-\\ +
 \\  \\ 
 This is the back process complete. This is the back process complete.
 +\\ 
 +\\ 
 +Next we need to make the AMI available in our new region (AZ).
 +\\ 
 +\\ 
 +{{ :aws_move_instance_007.jpg?900 |}}
 +\\ 
 +Select <color #ff7f27>Actions</color>, then <color #ff7f27>Copy AMI</color>.
 +\\ 
 +\\ 
 +The Copy AMI page will open.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_008.jpg?600 |}}
 +\\ 
 +We have to make some initial choices here:
 +\\ 
 +\\ 
 +**Destination Region:**    This is the new AZ for your EC2 Instance (I want it in London)
 +**Name:**                  A name to identify the copied AMI (you will need this, so make it obvious)
 +\\ 
 +\\ 
 +Select <color #ff7f27>Copy AMI</color>.
 +\\ 
 +\\ 
 +A Copy AMI Confirmation window will open.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_008.jpg?600 |}}
 +\\ 
 +Select <color #ff7f27>Done</color>.
 +\\ 
 +\\ 
 +This also took around 5 minutes to complete for my EC2 Instance.
 +\\ 
 +\\ 
 +Before you continue, it is very important to ensure that you are now working in the correct AZ (Availability Zone). 
 +\\ 
 +\\ 
 +{{ :aws_move_instance_010.jpg?900 |}}
 +\\ 
 +In the top right of the web interface, ensure you see your zone.
 +\\ 
 +\\ 
 +Before you continue, ensure that the status for the AMI is <color #22b14c>available</color>. What you have just done is to copy the AMI you created in your original AZ, and put it in the AZ where you want the new EC2 Instance to reside.
 +\\ 
 +\\ 
 +when the AMI is available, select <color #ff7f27>Actions</color>.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_011.jpg?900 |}}
 +\\ 
 +From the menu, select <color #ff7f27>Launch</color>.
 +\\ 
 +\\ 
 +What launch does, it to take you through an identical process to when you create a new EC2 Instance.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_012.jpg?900 |}}
 +\\ 
 +Chose an instance type, select <color #ff7f27>t2micro</color> (free tier) and then select Next: <color #ff7f27>Configure Instance Details</color>.
 +\\ 
 +\\ 
 +**Configure Instance Details.**
 +\\ 
 +\\ 
 +{{ :aws_move_instance_013.jpg?900 |}}
 +\\ 
 +Unless you have a good reason, there are no changes required here. Select <color #ff7f27>Next: Add Storage</color>.
 +\\ 
 +\\ 
 +**Add Storage.**
 +\\ 
 +\\ 
 +{{ :aws_move_instance_014.jpg?900 |}}
 +\\ 
 +I normally accept the defaults here, but I do change from SSD to Magnetic. Select <color #ff7f27>Next: Add Tags</color>.
 +\\ 
 +\\ 
 +**Add Tags.**
 +\\ 
 +\\ 
 +{{ :aws_move_instance_015.jpg?900 |}}
 +\\ 
 +Nothing to do here, select <color #ff7f27>Next:Configure Security Group</color>.
 +\\ 
 +\\ 
 +**Configure Security Group**
 +\\ 
 +\\ 
 +{{ :aws_move_instance_016.jpg?900 |}}
 +\\ 
 +Here we have to open any ports that we were using for the instance we copied earlier. I was using port 80 as my EC2 Instance was a web server.
 +\\ 
 +\\ 
 +Add any relevant ports then select <color #ff7f27>Review and Launch</color>.
 +\\ 
 +\\ 
 +You will get a warning about storage.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_017.jpg?600 |}}
 +\\ 
 +Because we selected magnetic, we see this page. I have been using magnetic for a few weeks and have not yet incurred any costs.
 +\\ 
 +\\ 
 +Select <color #ff7f27>Next</color>.
 +\\ 
 +\\ 
 +After all the settings pages you will see a **confirmation page**.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_018.jpg?900 |}}
 +\\ 
 +Select <color #ff7f27>Launch</color>.
 +\\ 
 +\\ 
 +Because this is a new EC2 Instance, we need to create a new Key Pair.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_019.jpg?600 |}}
 +\\ 
 +Select <color #ff7f27>Create a new key pair</color> and enter a <color #ff7f27>Key pair name</color>.
 +\\ 
 +\\ 
 +Select <color #ff7f27>Download Key Pair</color>. (Don't lose the key, you will permanently lose access to your EC2 Instance.)
 +\\ 
 +\\ 
 +Select <color #ff7f27>Launch Instances</color>.
 +\\ 
 +\\ 
 +If you check the status of your EC2 Instance, you will see the following:
 +\\ 
 +\\ 
 +{{ :aws_move_instance_020.jpg?900 |}}
 +\\ 
 +The Availability Zone (AZ) has now changed to the region you selected. Your IP will also have changed, as IPs can't be moved between AZs you will have to update your DNS settings, also if you use Elastic IP Addresses, you will have to recreate new ones for this AZ.
 \\  \\ 
 \\  \\ 
  
 +----
 +
 +==== 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.
 +\\ 
 +\\ 
move_ec2_instance.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1