We're pleased to announce new AWS AMIs for Mercury 1.1 on Ubuntu Lucid. These Beta AMIs were made using the instructions posted here: http://groups.drupal.org/node/70268. AMI IDs after the jump...
us-east:
ami-294aa340 pantheon-amis-us-east/mercury-pressflow-drupal-lucid-32-1.1-Beta2.manifest.xml
ami-554aa33c pantheon-amis-us-east/mercury-pressflow-drupal-lucid-64-1.1-Beta2.manifest.xml
us-west:
ami-2b8ddc6e pantheon-amis-us-west/mercury-pressflow-drupal-lucid-32-1.1-Beta2.manifest.xml
ami-298ddc6c pantheon-amis-us-west/mercury-pressflow-drupal-lucid-64-1.1-Beta2.manifest.xml
eu-west:
ami-6d3c1619 pantheon-amis-eu-west/mercury-pressflow-drupal-lucid-32-1.1-Beta2.manifest.xml
ami-673c1613 pantheon-amis-eu-west/mercury-pressflow-drupal-lucid-64-1.1-Beta2.manifest.xml
ap-southeast:
ami-27e39c75 pantheon-amis-ap-southeast/mercury-pressflow-drupal-lucid-32-1.1-Beta2.manifest.xml
ami-25e39c77 pantheon-amis-ap-southeast/mercury-pressflow-drupal-lucid-64-1.1-Beta2.manifest.xml
A couple of notes:
1) These are our first Mercury images to support multi-site ApacheSolr and Memcached. We'll post instructions here soon on how to set this up. Multi-site instructions are here: http://groups.drupal.org/node/72488
2) These images were made using the code at http://launchpad.net/pantheon/1.1 - this is the same path we'll use for Mercury 1.1 when it's out of Beta. This means that a simple "sudo /usr/local/bin/update_mercury.sh" will update a server made from the above images to Mercury 1.1 stable (when it's released).
3) We'll targeting Ubuntu Lucid and CentOS 5.5 (coming very soon) for Mercury 1.1. While we've done nothing (that we know of) to prevent Ubuntu Jaunty and Karmic servers from running Mercury 1.1, we strongly suggest that folks use Ubuntu Lucid (being a a long-term support release) or CentOS as they are the focus of our development and testing.
4) I have previously indicated the I thought we would release an EBS-boot AMI for Mercury. This no longer seems likely. The issue is spending development time for a platform that is so unique. However, all our code is posted at http://launchpad.net/pantheon and we would be more than happy to integrate any working code that helps folks to use Mercury on EBS-instances. Having said that, the Mercury 1.1 instructions (http://groups.drupal.org/node/70268) should install on an EBS-boot instance, but I would use "sudo bcfg2 -vqed" rather than "sudo bcfg2 -vqed -p 'mercury-aws'" in step 5 to prevent BCFG2 from moving data into /mnt (which is non-persistent on an EBS-boot instance). Then, after Mercury 1.1 is installed, one would want to install some of the AWS-specific packages like ec2-ami-tools, ec2-api-tools, and ec2-consistent-snapshot.
As always with our releases, we are very interested in feedback. Please post here any issues/questions/suggestions you have.
Thanks and enjoy!
Greg