Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« IBM Tivoli Now Available on Amazon EC2 | Main | Expanding the AWS Footprint »


TrackBack URL for this entry:

Listed below are links to weblogs that reference New Amazon EC2 Feature: Boot from Elastic Block Store:


Feed You can follow this conversation by subscribing to the comment feed for this post.


This is awesome! Good workaround for persistence issues :)

Hope manual stopping and hardware failure on the physical host are the same? I mean we can restart such instance easily like if it was stopped manually?

Dane Morgridge

Will this feature finally allow us to have Windows Server 2008 instances?


Exciting news! I look forward to trying this out, and I'll post my experience on

Kimbro Staken

This is great to see. Persistence and faster boots are going to prove very, very useful. Are the EBS backed AMIs considered identical to S3 backed AMIs from the perspective of other tools that launch them?


It seems that it's impossible to create fresh AMIs from scratch:

"Another approach is to build a fresh installation either on a stand-alone machine or on an empty file system mounted by loopback. This is only applicable for AMIs backed by Amazon S3 and entails building an operating system installation from scratch."

Does that mean that we'll be only able to use the existing fc/windows AMIs to create new ones? It looks like there's no way to create a new EBS AMI other than using an existing one as it's not possible to create an EBS AMI from a S3 AMI.

Paul Prescod

Is there a documented process for moving an instance or image from local-store backing to EBS-backing?


You really need a warning message in the Management Console that when one terminates an EBS-based instance, the root EBS volume will be automatically deleted! We expect this with the instance virtual storage but not with EBS. I suspect that many API users will catch this, but I feel lucky that I caught this in the documentation. I bet most Management Console users will discover this the hard way likely before they get an S3 snapshot made. I tested it out, and there is absolutely no warning before Management Console happily deletes the EBS volume. Existing EBS volume users are not used to these volumes ever being destroyed automatically. A simple warning and suggestion to make an S3 snapshot first would go a long way. And perhaps provide a Management Console option to change the default behavior, so that an MC user can easily choose to keep them by default. I will certainly be highlighting this in my blog as soon I finish playing around with the new EBS-based S3.

The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30