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 19:40] – [Move EC2 Instance] walkeradminmove_ec2_instance [2017/07/26 19:53] walkeradmin
Line 242: Line 242:
 \\  \\ 
 \\  \\ 
 +From the dashboard, select the AZ where your original EC2 Instance was created (US East (Ohio) in my case.)
 +\\ 
 +\\ 
 +{{ :aws_move_instance_021.jpg?900 |}}
 +\\ 
 +You can't see instances in different AZs on one page unfortunately, so if you have co-located EC2 Instances, you have to navigate between AZs.
 +\\ 
 +\\ 
 +So here we are, back at the original AZ where our original EC2 Instance is.
 +\\ 
 +\\ 
 +{{ :aws_move_instance_022.jpg?900 |}}
 +\\ 
 +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..<color #ed1c24>8GB</color>\\ 
 +The AMI we created is using.....<color #ed1c24>8GB</color>\\ 
 +The AMI copy is using...........<color #ed1c24>8GB</color>\\ 
 +The new EC2 Instance is using...<color #ed1c24>8GB</color>\\ 
 +\\ 
 +Total...........................<color #ed1c24>32GB</color>
 +\\ 
 +\\ 
 +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.\\ 
 +\\ 
 +\\ 
 +
move_ec2_instance.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1