Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can I make an AMI from a running instance that uses instance-store as its root device?

Or is it absolutely necessary to have an EBS backed storage? Does anyone have manuals/Howtos?

I am following the manual given on this site.

like image 396
theTuxRacer Avatar asked Jan 04 '11 06:01

theTuxRacer


People also ask

Is it possible to create an AMI when an instance is running?

From the Amazon EC2 Instances view, you can create Amazon Machine Images (AMIs) from either running or stopped instances. Right-click the instance you want to use as the basis for your AMI, and choose Create Image from the context menu.

Can instance store be used as root volume?

Instances that use instance stores for the root device automatically have one or more instance store volumes available, with one volume serving as the root device volume. When an instance is launched, the image that is used to boot the instance is copied to the root volume.

What are the different ways an AMI can be created in AWS?

Create your own AMI You can launch an instance from an existing AMI, customize the instance (for example, install software on the instance), and then save this updated configuration as a custom AMI. Instances launched from this new custom AMI include the customizations that you made when you created the AMI.

What root device options are available for launching an AMI on an EC2 instance?

So when you are creating an EC2 instance, AWS provides you with two choices for root device. Instance store-backed and EBS-backed.


Video Answer


1 Answers

You can create an AMI from either an EBS or S3-backed running instance. The simplest way is to use the AWS Management Console to select the instance and click 'Create Image' from the Instance Actions menu.

This will create either an EBS or S3-backed AMI, depending on the type of instance.

Be aware that creating an AMI from a Running instance is inherently potentially unsafe - the storage is not imaged as a hard 'point-in-time' snapshot, so changes to the filesystem whilst the image is being created may not be recorded, and may even result in a compromised image. You should quiesce the OS as far as possible before starting.

Note also that your instance will reboot during the image-creation process, so make sure you're prepared for any temporary loss of service from the VM.

like image 175
Eight-Bit Guru Avatar answered Oct 01 '22 19:10

Eight-Bit Guru