amazon-ec2 resize - How to safely upgrade an Amazon EC2 instance from t1.micro to large?
increase downtime (5)
From my experience, the way I do it is create a snapshot of your current image, then once its done you'll see it as an option when launching new instances. Simply launch it as a large instance at that point.
This is my approach if I do not want any downtime(i.e. production server) because this solution only takes a server offline only after the new one is up and running(I also use it to add new machines to my clusters by using this approach to only add new machines). If Downtime is acceptable then see Marcel Castilho's answer.
I have an Amazon EC2 micro instance (t1.micro). I want to upgrade this instance to large. This is our production environment, so what is the best and risk-free way to do this?
Is there any step by step guide to do this?
Use the AWS EC2 console, not ElasticFox.
- Create a new AMI of the instance
- Launch it
- Make a snapshot of the disk
- Launch a large EBS instance with the same AMI type (please note that at this point the disk will contain the data that was present when this AMI was created, not your latest changes)
- Once is fully booted, stop the new instance
- Detach the root volume from the stopped instance
- Create a virtual disk from the snapshot created before in the same availability zone of the new instance
- Attach the root volume to /dev/sda1
- Start the new instance again
Using the AWS Management Console
- Go to "Volumes" and create a Snapshot of your instance's volume.
- Go to "Snapshots" and select "Create Image from Snapshot".
- Go to "AMIs" and select "Launch Instance" and choose your "Instance Type" etc.
Using AWS Management Console:
- Right-Click on the instance
- Instance Lifecycle > Stop
- Instance Management > Change Instance Type
This is the aws suggested solution You can detach the root volume from the original instance after stopping it. The root volume is attached at /dev/sda1. Once this is detached, please attach it to the new instance. After the volume is attached, you may have to mount it from the OS. After it's mounted, you should see the data within it.
After you've done adding the new key, you can detach it and attach to the original instance at /dev/sda1.
I suggest creating a snapshot of the root volume before making any changes.
Before trying out any solutions just try out in the not important instances or spot instances