amazon-ebs

I attached an EBS volume to my EC2 instance, turned it into a EXT3 file system, and successfully mounted it. However, I was thrown off a little bit initially mainly due to what the AWS console said my EBS device ID was. According to the AWS console: i-xxxxxxx :/dev/sdf (attached) I took this to mean that my attached EBS device id was /dev/sdf. So when I attempted to turn the device into a file system using this device id, I received the following error message. ubuntu@ip-xx-xx-xx-xx:~$ mkfs -t ext3 /dev/sdf mke2fs 1.42 (29-Nov-2011) Could not stat /dev/sdf --- No such file or directory The

I have a server running the recent Ubuntu AMIs from Canonical. The size of the EBS boot volume is 8GB. I know that I can resize EBS volumes by taking a snapshot, creating a new volume and expanding the partition on it. How can I increase the size of the volume while the machine is running? If this is not possible, what is the preferred method for increasing the boot volume size with minimal downtime? Unfortunately it is not possible to increase the size of an Amazon EBS root device storage volume while the Amazon EC2 instance is running - Eric Hammond has written a detailed (I'm inclined to

I have an EBS volume (e.g. /dev/sdf ) that has been attached to an EC2 instance (which boots from a different EBS volume), and I have mounted the volume (through mount /dev/sdf /data ). When I stop and start again the instance, the volume is still attached but no longer mounted, and I have to manually mount it again. Is there a way to make the volume /dev/sdf automatically mounted to /data upon starting the instance? Sanket Dangi Make an entry to /etc/fstab Entry would be like: /dev/sdf /data ext3 defaults 1 1 This will automatically mount the volume during reboot. It would seem that the

I couldn't find the answer on EC2 documentation. What is it for? If I launched an EBS backed instance, the root device for the instance would be an EBS volume. If I install a few tools/software on the instance, will those be installed on the root instance by default? Still I guess the question really came from the little understanding of the root device. Any detailed info on that? Also if I need to launch another EBS backed instance, and also want to have the same copy of the tools/software installed on the earlier instance, how to do that? EC2 instances have two types of storage -- ephemeral

I see that you can convert an instance stored instance to be EBS backed as this question shows. However, I want to do the opposite, take an EBS backed instance and convert it to be Instance Store backed. Is this possible? How do I do this? Shlomo Swidler Launch an instance-store instance from an AMI that uses the same kernel used by your EBS-backed AMI. Create an EBS volume from the snapshot underlying the EBS AMI. (Alternatively, launch an instance of the EBS AMI and Stop the instance when it begins booting. Detach the root volume from the instance - this is usually the volume attached to

I'd expect this to be fairly routine, but cannot find a simple approach for creating an managing EBS snapshots automatically. Was hoping there'd be a shceduler in the AWS console.. alas not yet. Would appreciate any suggestions as to how best to do this on from Ubuntu. Thanks You can easily script something to do this for you. setup the EC2 commandline API tools set EC2_CERT and EC2_PRIVATE_KEY in order to be able to use the API tools parse the results of ec2-describe-snapshots delete the appropriate snapshots The results look something like: SNAPSHOT snap-xxxxxxxx vol-xxxxxxxx completed 2009

I am using EBS volume to store MySQL data. I do have enough space on ephemeral device as well. I will move the data to /root/, provided it will improve the query performance. Is ephemeral storage faster than EBS volumes? Steffen Opel Daan's answer is pointing to Eric Hammond's excellent summary of all EBS benefits already (+1), but to stress one point again upfront: Ephemeral storage will be lost on stop/start cycles and can generally go away , so you definitely don't want to put anything of lasting value there, i.e. only put temporary data there you can afford to lose or rebuild easily , like