Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an Amazon EC2 Windows 2008 R2 x64 instance that I upgraded from "micro" to "large". I upgraded it by stopping it, then right clicking on the instance in the AWS Management Console and change the instance type. When I booted it up again, it still had only a 30GB HDD, and I could find no unallocated space in the Disk Manager.

Any suggestions would be appreciated!

share|improve this question
up vote 1 down vote accepted

The 30GB you're seeing is the EBS-backed volume that was carried over from your t1.micro instance.

To gain access to the ephemeral disk that comes with the m1.large instance, you need to specify that when you start the instance:

$ ec2-run-instances ami-XXXXXX -k <key> -g <security_group> -b "xvda=ephemeral0" -t m1.large

Keep in mind that this really, truly is ephemeral storage. It will go away, so don't use it for anything other than temporary storage. For anything that matters, use EBS-backed volumes.

share|improve this answer
Is it possible to increase the EBS-backed volume? – gorzan Feb 7 '12 at 8:52
You can snapshot it and launch a new volume with a larger size, then swap them out. – ceejayoz Mar 21 '12 at 17:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.