Convert an Instance-Store AMI to EBS-Backed AMI


  1. Launch an instance from an instance store-backed AMI.
  2. Make a note of the ramdisk ID and kernel ID your running instance is using 
  3. Create a 10GiB Amazon EBS volume in the same Availability Zone as that of your newly-launched instance e.g. /dev/sdf
  4. Attach the volume to the running instance using either the AWS Management Console or the command line interface.
  5. Make sure all services are turned off like mysqld, nginx etc.
  6. Format the volume with a file system. Newer kernels use /dev/xvdf convention
    • mkfs.ext3 /dev/xvdf
  7. Create a directory /mnt/ebs and mount the volume on it.
    • mkdir /mnt/ebs  
    • mount /dev/xvdf /mnt/ebs
  8. Copy the data on the root storage device to the newly-attached volume.
    • rsync -avx --exclude /mnt/ebs / /mnt/ebs
  9. [SPECIFIC TO UBUNTU]
    1. Edit /mnt/ebs/etc/fstab,/mnt/ebs/boot/grub/menu.lst and /mnt/ebs/boot/grub/grub.cfg and replace uses of LABEL=cloudimg-rootfs with /dev/xvda1  
    2. Remove /dev/xvda2 and /dev/xvda3 specific instructions from /mnt/ebs/etc/fstab
  10. [SPECIFIC TO CENTOS]
    1. Edit /mnt/ebs/etc/fstab,/mnt/ebs/boot/grub/menu.lst and replace uses of LABEL=/ with /dev/xvde1.
    2. Remove /dev/xvde2 and /dev/xvde3 specific instructions from /mnt/ebs/etc/fstab
  11. Create the following devices within the /mnt/ebs
    1. MAKEDEV console
    2. MAKEDEV generic
    3. MAKEDEV zero
    4. MAKEDEV null 
  12. Detach the volume from the instance.
  13. Create a snapshot of the volume.
  14. Register the snapshot of the volume as an AMI. While registering make sure you enter the architecture correct and the Kernel ID and Ramdisk ID should match the one taken a note of in Step 2. If the Ramdisk ID information is not available form the instance then leave it to Use Default.

Comments

Post a Comment

Popular posts from this blog

To DR or Not To DR

Image
Most organizations these days look at strategies and ways of implementing a "working" DR solution. Often a DR plan of action is a manual process based on multiple approvals at each level from Incident Management Teams to Product Ownership teams. What if there was a way to keep an active DR running where failure of a primary site would seamlessly transfer the traffic to the secondary site. In fact if the DR is active or warm then the only manual bit would be disabling the primary site via DNS. A few tips and tricks that would help in a simple implementation of a warm DR for an application hosted on AWS. AMI  Make sure that the AMIs are built across both the primary and secondary region.  The fastest way to build multi-region AMIs would be to use different builds for each region using the same configuration management code altering the "REGION" parameter each time. This would make the AMIs consistent and available in each region. PACKAGE REPOSITORY ...
Read more

Blue/Green Deployments with AWS Cloudformation

Image
Off late I've been working a fair bit on Amazon Web Services. AWS provide a wide range of high end and mature services which, when used in combination with each other could provide an enterprise a highly available, scalable and resilient infrastructure solution. In the past few months, I've worked a fair bit on implementing blue/green deployments for our services. Since we were already using Cloudformation to implement zero downtime deployments, we decided to re-use the same code and approach. The place that slowed us down was that no one has tried to implement blue/green deployments using cloudformation because I couldn't find a decent article/blog/anything that documented a decent approach for the same. So here's the approach that I implemented for the said scenario. The first and foremost thing to remember here is to split your cloudformation templates into smaller templates that are task based. Another important thing to remember is that blue/green ...
Read more