Adventures with Project Mercury

I've been trying to improve the performance of my Drupal sites for the longest time. Finally, I've decided to jump in and give Project Mercury and Pressflow a crack. This is a log of that adventure.

ec2-describe-instances

I was having trouble with this command from the AWS command line tools. Other commands were working so I knew I was connecting ok to my account. Turns out adding the following to my .bash_profile fixed the problem:

export EC2_URL="https://ec2.us-west-1.amazonaws.com"

use ec2-describe-regions to see regions. 

Which installation profile: Project Mercury or Pressflow?

When you first visit your Project Mercury/Pressflow instance on EC2,you will be asked to choose a Drupal installation profile: ProjectMercury or Pressflow. Choose Project Mercury. You can find moreinformation on this by shelling into your PM instance as root andreading the README.txt

Getting Started

In the Panthon Group, they make a distinction of installing a preconfigured EC2 AMI stack or "rolling your own" using a very complex bunch of steps. See http://groups.drupal.org/node/50408

Syndicate content