ec2base

http://wagerlabs.com/setting-up-erlang-on-amazon-ec2

Amazon does not provide tools to cluster your instances or replicate data among them. This is a task that Erlang copes with extremely well so Amazon EC2 and Erlang are a match made in haven!

More: http://wagerlabs.com/tag/ec2

http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/

Amazon recently announced a new feature which allows you to boot from an ebs volume. But it doesn’t provide any tools to convert your existing AMIs to this new type of image. There is no easy way to create an ebs image from scratch. There are some posts that explain how to convert your existing AMI into this new type of image using ec2-unbundle and dd (a linux utility). I am going to take a little different route and explain how we can create an ebs image from an existing instance. It’s fairly simple to create a new image using dd from an existing instance.

http://www.deerwalk.com/article-1243527607.html

Today, we successfully hosted our corporate website (www.deerwalk.com) in Amazon EC2. Amazon EC2 is the premier service in cloud computing and given the excitement around cloud computing these days, we wanted to give it a try.

Before we started, we googled for similar prior experiences and we found these sites extremely helpful:

http://blogs.adobe.com/livecycle/2009/12/running_livecycle_on_amazon_ec.html

One of the major annoyances with Amazon’s Elastic Compute Cloud (EC2) has been its behavior when you shut down one of the instances. All changes you made were immediately and irretrievably lost. You had to be a programmer to backup your changes to Amazon’s Simple Storage Service (S3). If you decided to keep your instance running overnight so that you could continue working the next day, you incurred hefty charges for the 8-12 hours of night time during which you do not even use it.

Amazon then introduced the Elastic Block Store (EBS) service which essentially is your own hard disk where you could save things that would survive a machine shutdown. However, up until a week ago, you could not boot from your EBS volume. Now you can.

http://blog.shutupandcode.net/?p=374

Solr, Zabbix, Selenium

http://solutions.amazonwebservices.com/connect/thread.jspa?threadID=39361&tstart=0

I would like to share my experience mounting a S3 bucket into a Linux EC2 instance.

The steps I followed were:

http://www.elastician.com/2009/12/creating-ebs-backed-ami-from-s3-backed.html

The recent introduction of Boot From EBS for EC2 opens up a lot of new possibilities. But there are some bootstrapping issues to deal with. There aren’t many EBS-backed AMI’s available yet and, given the rather complex process involved in porting them, it may take a while for them to show up. This article will walk through the process of converting a popular S3-based AMI to an EBS-backed AMI.

http://www.danysoft.org/blog/2009/10/25/how-to-create-a-centos-5-3-ec2-ami/

after looking some usefull guides to create Amazon Machine Image based on CentOS distribution, I decide to write the steps that i followed.

First of all we need of a CentOS machine, if you don’t have it use a virtual machine program (on my Kubuntu based laptop I use VirtualBox), once we have it login and start:

http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?ami-via-loopback.html

This method involves doing a full operating system installation on a clean root file system, but avoids having to create a new root disk partition and file system on a physical disk. Once you have installed your operating system, the resulting image can be bundled as an AMI with the ec2-bundle-image utility.

http://alestic.com/2009/08/ec2-talk

Presentation: Building Custom Linux Images for Amazon EC2
By Eric Hammond on August 10, 2009 2:06 PM

At the end of July, I gave a presentation at O’Reilly’s Open Source Convention (OSCON 2009) in San Jose. The slides from the presentation have been made available on the OSCON web site in ODP and PDF formats (look for links towards the top of the page):

http://blog.dt.org/index.php/2009/06/how-to-create-an-amazon-ec2-ami-that-is-larger-than-10gb/

Recently, I have been dealing with an issue surrounding the 10GB size limit for AMIs within Amazon’s EC2 service. If you don’t what I’m talking about, here is a quick primer: a virtual instance running within Amazon’s Elastic Compute Cloud (EC2) service is launched from a read-only boot image that Amazon refers to as an Amazon Machine Image (AMI); Amazon has set the upper size limit for an AMI to be 10GB, and this restricts the amount of disk content that can be loaded on to the instance at boot.

http://groups.drupal.org/pantheon/mercurywiki

By popular request, here are step-by-step instructions for building the Project Mercury setup on a fresh ec2 image. We have both 32 and 64 bit versions of this AMI available (see http://groups.drupal.org/amazon-web-services-s3-ec2).