Powerful New Amazon EC2 Boot Features

| | Comments (9)

Today a powerful new feature is available for our Amazon EC2 customers: the ability to boot their instances from Amazon EBS (Elastic Block Store).

Customers like the simplicity of the AMI (Amazon Machine Image) model where they either choose a preconfigured AMI or upload their own AMI into Amazon S3. A wide variety of operating systems and software configurations is available for use. But customers have also asked us for more flexibility and control in the way that Amazon EC2 instances are booted such that they have finer grained control over for example what software configurations and data sets are available to the instance at boot time.

serverfolders-small.jpg

The ability to boot from Amazon EBS gives customers very powerful control over the boot configuration of the Amazon EC2 instances. In the traditional boot process, the root partition of the image will be the local disk, which is created and populated at boot time. In the new Amazon EBS boot process, the root partition is an Amazon EBS volume, which is created at boot time from an Amazon EBS snapshot. Other Amazon EBS volumes beyond the root disk can also made part of the instance before it is booted. This allows for a very fine-grain control of software and data configuration. An additional advantage of using the Amazon EBS boot process is that root partitions are no longer constrained by the size of the local disk and can be up to 1TB in size. And the new boot process is significantly faster because a local disk no longer needs to be populated.

With this new boot process another powerful feature is available to our Amazon EC2 customers: the ability to stop an instance and restart it at a later time with the disk configuration intact. When an instance is restarted, the customer can choose to use a different instance type (e.g., with more memory or CPU), a different operating system (e.g., with new security patches installed), or add new user data. While the instance is stopped it does not accrue any usage hours and customers are only charged for the storage associated with the Amazon EBS volume. The ability to stop and restart an instance is a very powerful mechanism that makes management of instances much easier; many scenarios related to adaptive instance sizing and software management have now become much simpler.

The new boot from Amazon EBS feature is an important step in our continuing quest to remove more and more of the heavy lifting that comes with today's computer environments.

For more details on the new boot features visit the Amazon EC2 detail page and the posting on the AWS developer blog. RightScale's perspective is also worth reading.

9 Comments

Great news! This is going to save me MANY hours of deployment hassle. Thanks!

Ed Voncken said:

Excellent, this makes your cloud instances feel more like traditional machines... And there was much rejoicing ;-)

Daniel said:

We have been waiting for this feature at BitNami for a long time , looking forward to add support for this in our stacks.

Mark said:

This is an amazing advance in the platform. Congratulations to your team!

John Willis said:

Why don't you guys just segment out a pvt version of AWS and put everyone out of their misery? Well done, great new feature.

John
johnmwillis.com

Frank said:

This is excellent! Widens the gap between EC2 and 'the rest' even further. Keep up the good work!

Denis said:

How about Windows 2008 Server support? Haven't heard about that lately.

Sacha said:

Is this a traditional "start/stop" or a faster "standby/resume"? If it is the former, will the later be available at some point?

Werner Vogels said:

It is start/stop, standby/resume would require saving memory and OS state and that is not supported.

About this Entry

This page contains a single entry by Werner Vogels published on December 3, 2009 1:00 AM.

Expanding the Cloud - New AWS Region: US-West (Northern California) was the previous entry in this blog.

Expanding the Cloud - Amazon EC2 Spot Instances is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.