Increasing an AWS instance's disk space by adding an EBS volume

I wanted to provide more free disk space for my AWS instance. I had previously discovered that restoring a snapshot to a larger EBS volume doesn't easily accomplish this, so instead I added a second EBS volume to the instance. Here's how to do so using the AWS Management Console:

Click Volumes.

Click the Create Volume button.

Type in the desired size (I entered 30 GiB). Select the Availability Zone, making sure it's the same one used by your instance. From the Snapshot dropdown, select --- No Snapshot ---.

Right-click the newly created volume and select Attach Volume. Select your instance. Accept the default value for Device. (If the state doesn't change immediately from attaching to attached, try refreshing the page.)

At first, when I used Windows Explorer to view the disks in a Remote Desktop session on my instance, I didn't see the new disk. Logging off and back on didn't help. Stopping and restarting the instance did the trick. I'm not actually sure if that's what helped, or if I just needed to wait a few minutes, or what. But in the end, it worked. In addition to the C: drive, I now had an empty D: drive with a capacity of 29.9 GB.

Restoring an AWS instance from a snapshot

I had created an Amazon Web Services instance. As is the default when creating an instance, it used EBS as the root device.

A few days ago, when I had it set up just the way I liked it, I created a snapshot. Then I did some experimental work, didn't like the results, and wanted to restore the snapshot to revert. Here's how to do that using the AWS Management Console:

1. In the AWS Control Panel, click Instances, then click on your instance. Instance details will be displayed at the bottom of the page. Note the instance's name (Steve-Jenkins in my example; yours will be different), instance ID (i-4b33962d), zone (us-east-1c), and root device (sda1).
2. If the instance is running, stop it.
3. Click Volumes. Look at the Attachment Information column to locate the volume currently attached to your instance. Right-click this volume and select Detach Volume. (The volume's state might not change from in-use to available right away. If it doesn't, try refreshing the page.)
4. Click Snapshots. Right-click your snapshot and select Create Volume from Snapshot. Set the size (30 GiB in my example) and Availability Zone. Make sure the Availability Zone matches the one you noted in step 1.
5. Return to Volumes. Right-click the newly created volume and select Attach Volume. Select your instance. For Device, type in  the root device you noted in step 1, but be sure to prepend /dev/. In my example, I entered /dev/sda1.
6. To avoid charges for the old volume that's no longer attached to your instance, right-click it and select Delete Volume.
7. Click Instances, right-click your instance, and select Start Instance. If you created and attached the volume correctly, the instance should start without error.

Tip: If you had an Elastic IP attached to your image, don't forget to reattach it now. Click Elastic IPs, right-click the IP address, select Associate, and select your instance.

Another tip: I wanted more disk space, so I tried making the new volume larger -- 60 GiB rather than 30 GiB -- in step 4. This didn't work. I ended up with a 60 GiB volume, but only 30 GiB was in a usable boot partition. The rest was in an unallocated partition, and I couldn't find a convenient way to merge the two partitions without losing data. A better alternative might be to create a second volume and attach it to the same instance.

Using Seleniun WebDriver with Windows and .NET

Wanting to write a C# program to do some automated functional testing in multiple browsers, I downloaded Selenium WebDriver version 2.21.0.

I also downloaded the Selenium Client Drivers for C#. At the time I first downloaded these, the version was 2.16.0.

I proceeded to create a Selenium hello-world program by following the C# example provided here. With all the comments and fluff stripped out, my program looked something like this:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using OpenQA.Selenium;
using OpenQA.Selenium.Firefox;
using OpenQA.Selenium.Support.UI;
namespace WebDriver1
{
    class Program
    {
        static void Main(string[] args)
        {
            IWebDriver driver = new FirefoxDriver();
            driver.Navigate().GoToUrl("http://www.google.com/");
            IWebElement query = driver.FindElement(By.Name("q"));
            query.SendKeys("Cheese");
            query.Submit();
            WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(10));
            wait.Until((d) => { return d.Title.ToLower().StartsWith("cheese"); });
            System.Console.WriteLine("Page title is: " + driver.Title);
            driver.Quit();
        }
    }
}
One note right off the bat: The example code at seleniumhq.com doesn't include using OpenQA.Selenium.Support.UI. This is needed, or else WebDriverWait can't be resolved.

When I tried to run this program, it threw an exception: OpenQA.Selenium.WebDriverException : Failed to start up socket within 45000. I found some stuff about this online, but none of it helped. What solved the problem was downloading the latest version, 2.21.0, of the Selenium Client Drivers.

With those two problems solved, the program compiled and ran, launching Firefox, doing a Google search for "cheese," and outputting the page title. Pretty cool!

Next, I wanted to do the same thing using IE.

The first stumbling block was when I added this line to my code: driver = new InternetExplorerDriver();

This class wasn't found. Easily remedied by adding this as well: using OpenQA.Selenium.IE;

My whole program now looked like this, executing a loop twice, once for each browser:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using OpenQA.Selenium;
using OpenQA.Selenium.Firefox;
using OpenQA.Selenium.IE;
using OpenQA.Selenium.Support.UI;
namespace WebDriver1
{
    class Program
    {
        static void Main(string[] args)
        {
            for (int i = 0; i < 2; i++)
            {
                string browserName = "";
                IWebDriver driver = null;
                switch (i)
                {
                    case 0:
                        browserName = "FireFox";
                        driver = new FirefoxDriver();
                        break;
                    case 1:
                        browserName = "IE";
                        driver = new InternetExplorerDriver();
                        break;
                }
                driver.Navigate().GoToUrl("http://www.google.com/");
                IWebElement query = driver.FindElement(By.Name("q"));
                query.SendKeys("Cheese");
                query.Submit();
                WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(10));
                wait.Until((d) => { return d.Title.ToLower().StartsWith("cheese"); });
                System.Console.WriteLine(browserName + ": Page title is: " + driver.Title);
                driver.Quit();
            }
        }
    }
}
This worked for Firefox but threw an exception when it opened Internet Explorer.
System.InvalidOperationException: Unexpected error launching Internet Explorer. Protected Mode must be set to the same value (enabled or disabled) for all zones. (NoSuchDriver)

Surprisingly, this meant exactly what it said, and was corrected by opening IE, selecting Tools | Internet Options | Security, clicking on all four security zones (Internet, Local Intranet, Trusted Sites and Restricted), ensuring the Enable Protected Mode checkbox was checked for each zone, and restarting IE. (Unchecking the checkbox would work, too. The point is that the setting for all four zones must be the same.) A huge tip of the hat to Tom Dupont for that.

With IE's Protected Mode settings properly configured, the above program ran successfully, automating both browsers.