Drupal in the Cloud, Part 2D: Rackspace's Cloud Servers

Rackspace is another (awesome) option for a cloud service provider. I think their interface is extremely easy to navigate, and you have the added bonus of getting an external IP immediately instead of having to assign an external IP. The benefit of this is that your server, as long as it stays on, retains the IP.

So, go forth and create a Rackspace account! When you are done, come back and follow these instructions:

  • Click on the Cloud Servers in the left-hand side menu
  • Click on the Add Server button
  • Select the distro you wish to use. I recommend Ubuntu 12.04
  • Give your server an internal name and the size. I'm setting mine up as a 256MB instance. Don't sweat this step, as Rackspace allows you to easily resize the server in minutes.
  • You will be given a password. Store this in a secure location and select Close Window
  • The building process will take about two minutes, in which time you can grab a drink, refill, or just watch the progress-o-meter
Share this


Drupal in the Cloud, Part 3: Installing Virtualmin

Let me preface this section with a caveat: you do not need Virtualmin for Drupal to work. Drupal will work just fine without Virtualmin, provided it gets the three things it does need: Apache, MySQL, and PHP.

For those at home taking notes, this is typically called a LAMP setup- Linux, Apache, MySQL, PHP. LAMP. Get it? Cool, let's continue.

What Virtualmin does is provide an easy interface to manage your server, which is an absolute godsend for those who hate doing things by command line.

There are three things we need to get Virtualmin up and running:

  1. Be on a supported system (CentOS, Debian, Ubuntu LTS, etc.)
  2. Change the hostname to what its final hostname will be
  3. Run the install script

The first requirement is done, provided you have been doing things according to the tutorial.

The second requirement is fairly easy:

Share this


Drupal in the Cloud, Part 2C: Give your AWS Instance a Public IP

This part is fairly simple. If you are using AWS, your server does not get a public IP by default. This means that from the internet, your server is only accessible by that public DNS name when it is first launched.

However, it's fairly straightforward to give it a public IP using Amazon's Elastic IP service.

  • From the EC2 Navigation, select Elastic IP on the left-hand side
Share this


Drupal in the Cloud, Part 2B - Connecting to your AWS Instance

If you're using Linux or a Mac, this will be super easy. If you've got Windows it will be slightly harder. But only slightly.

Connecting to your Instance with Linux or a Mac

  • From the EC2 Console, locate your instance.
  • Select your instance and scroll down on the info page until you get to the Public DNS. Save this for later.
  • Open a terminal session and go to the folder that you saved the Key Pair in. Using the Public DNS address and your Key Pair name, type the following to connect to your AWS Instance:

    ssh -v -v -i *****.pem

Connecting to your AWS Instance with Windows

  • From the EC2 Console, locate your instance.
  • Select your instance and scroll down on the info page until you get to the Public DNS. Save this for later.
  • Download PuTTY from here. You will need both PuTTY and PuTTYGen, but if you do the full Windows installer you'll get them both.

Share this


Drupal in the Cloud, Part 2A - Amazon's Web Services

In Drupal in the Cloud: Part 1 I went over some basic background for why I wanted to use the cloud. If you are planning on using Amazon's Web Services, or AWS, start here.

AWS is a tricky beast. Nothing is truly external, at least not without some authorization keys. I'm not going to go over signup completely, but be warned- it involves a phone call, a credit card, and your first born son. Ok, maybe not the last one, but it sure feels like it.

Once you are signed up, you'll see a bunch of services they offer. The one that we are looking for is EC2, which stands for Elastic Computing Cloud. This is essentially their "cloud server", which they refer to as an Instance.

  • From the EC2 Console Dashboard, click on the Launch Instance button.
  • There are three options to choose from, select the Classic Wizard and continue
  • Depending on your budget and needs you can select a different instance type, but for me the 613MiB RAM Micro instance will be just fine. If you have a Zone preference you can select that as well, but the Micro instances are limited to only a few zones.
  • Select the most recent Ubuntu LTS release, which is 12.04 at the time of this writing.
Share this



Subscribe to RSS - cloud