I'm trying to produce an EBS-backed image from the running instance, much like this post on SO. I am using mainly these websites as references:
- Create a bootable EBS AMI from a running instance
- A script to rsync a running Linux OS to an image file
I effectively produced the EBS volume, went
mkfs.ext3 against it (I formatted the entire drive, not really a partition -- is the issue, possibly?) and used the next
rsync command to create a copy from the filesystem:
rsync --stats -avv --exclude=/root/.bash_history --exclude=/home/*/.bash_history --exclude=/etc/ssh/ssh_host_* --exclude=/etc/ssh/moduli --exclude=/etc/udev/rules.d/*persistent-net.rules --exclude=/mnt/* --exclude=/proc/* --exclude=/tmp/* --exclude=/sys/* --exclude=/dev/* --exclude=/production --exclude=/media / /mnt/ebs-root/
/production are sites mounted using their company EBS volumes, and
/mnt/ebs-root/ may be the new EBS volume that will retain the image)
the rsync is effective enough, I'm able to unmount the amount, snapshot it, and employ the AWS console to create a bootable image... however when it boots, I can not can get on over the internetOrssh (after altering its elastic IP within the AWS console).
I observed which i should edit some files within the new EBS volume (like /etc/fstab) but I am unsure. Here's the items in my /mnt/ebs-root/etc/fstab, anyway:
# Legacy /etc/fstab # Supplied by: ec2-ami-tools-1.3-34544 /dev/sda1 / ext3 defaults 1 1 /dev/sda2 /mnt ext3 defaults 0 0 /dev/sda3 swap swap defaults 0 0 /dev/sdp1 /production ext3 defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0
I am way outdoors my understanding base here and wishing someone can point me within the right direction. Thanks ahead of time.
The issue was which i tried to image the instance although it was running. I believed since nobody was being able to access the website which i could image it while running, but apparently not. This is what I went:
after which I re-went my
rsync command previously mentioned, and also the instance has become obtainable by SSH! (I've got a new problem now, but that is for an additional subject )
Thanks Jonners for that tips.