Comment 10 for bug 670161

The tech board approved of this change. Due to recommendation from Amazon, I'm going to make our volume size 8G.

I've just put the change in place so that all future daily builds will create 8G ebs volumes.

When we release new refreshed images of lucid and maverick, they'll have 8G ebs root.

Note, that if you wanted a 15G (or larger) volume, you can simply launch the instance with a larger volume. This can be done via the RunInstances api [1] or via ec2-run-instances [2] with --block-device-mapping.

For example:
  ec2-run-instances --block-device-mapping /dev/sda1=:100 --key mykey ami-480df921
Then, inside the instance, simply:
  sudo resize2fs /dev/sda1

See [2] for more information.

Note, that in Natty, the plan is to invoke 'resize2fs' on the root volume on first boot. That means that if you launched an instance a larger-than-default volume for sda1, it would automatically resize the filesystem to fill it.

--
[1] http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-RunInstances.html
[2] http://docs.amazonwebservices.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html
[3] http://alestic.com/2009/12/ec2-ebs-boot-resize