Skip to main content

Migrating to Amazon EC2 from GoGrid

Recently Amazon EC2 announced that they were going to support Windows Server 2008 instances.

The experience with GoGrid has been rocky to say the least and most recently the MyGSI’s shortcomings confirmed that the service was not able to meet our applications requirements for using instances on demand.

Which brings me to this post. After 14 months with GoGrid I have just recently completed a migration of all applications and databases to Amazon EC2 and thought I would outline the steps I took.

Creating New Instances

Before you start you will need to create your new instances in Amazon EC2. I have covered this previously in another post.

When you set up the firewall it is important that you open Port 1433 for traffic coming from your previous web server in GoGrid. Or if you want you can even create a temporary VPN between your GoGrid web server and EC2 database server using Amazon Virtual Private Cloud. This is an important step in ensuring minimal downtime.

At this point you’ll want to create CNAMES for the Amazon instance and add these bindings to IIS so that you can test all your applications before the DNS changes take affect.

Transferring Files & Data

The way I transferred the files was via Amazon S3, download speeds between EC2 and S3 are very fast. If you don’t have an S3 account yet just go to and click the “Sign Up” button.

You will need to put an S3 Client on your servers, I tend to use a combination of FireFox and the add-on S3Fox.

Once these are done all you need to do is backup any databases then zip the databases and files up and upload to a bucket in S3.

Once Uploaded you can download from within your EC2 instance, unzip and change any configuration values.

If you can put an indicator on one of your web pages which will help you to see that the DNS has gone through.

Test, Test, Test

Goes without saying but once you have all files and databases setup on your new instance you will want to perform some serious testing.

Don’t forget those Folder Permissions.

Making the DNS Change

Whether or not you have downtime depends entirely on the nature of your application. For a standard content managed website your data and files aren’t going to change that often so you should have plenty of time.

If you have a highly active system with lot’s of database writes then the downtime will be limited to the Backup, Restore process of your database. This was the case for me.

Load a temporary message onto your app advising users of the scheduled maintenance and make sure no users can log in.

Backup any data and files on your live GoGrid instance that may have changed after the last backup.

Upload to S3.

Download an unzip on EC2 instance. Restore any files and databases.

Change any Database Connection Strings on your live instance to point to your new EC2 instance on port 1433.

Update the DNS to point to your new server.


Once the DNS change has taken full affect (wait a week) you can terminate your GoGrid instances and enjoy the goodness of Amazon EC2.

I will still be using GoGrid as a failover provider in case of any outage on Amazon EC2.

Popular posts from this blog

ASP.NET MVC Release Candidate - Upgrade issues - Spec#

First of all, great news that the ASP.NET MVC Release Candidate has finally been released.  Full credit to the team for the hard work on this.  You can get the download here  However this is the first time I have had upgrade issues.  Phil Haack has noted some of the issues here   If like me you have lot's of CTP's and Add-Ins then you might experience some pain in Uninstalling MVC Beta on Vista SP1  This is the list of Add-Ins / CTP's I had to uninstall to get it to work  Spec# PEX Resharper 4.1  Sourcelinks ANTS Profiler 4   Can't say I'm too impressed as it wasted over an hour of my time.  As it turned out Spec# turned out to be the offending culprit, it's forgiveable to have issues with a third party product but a Microsoft one? Guess no-one on the ASP.NET team has Spec# installed. 

Freeing Disk Space on C:\ Windows Server 2008

  I just spent the last little while trying to clear space on our servers in order to install .NET 4.5 . Decided to post so my future self can find the information when I next have to do this. I performed all the usual tasks: Deleting any files/folders from C:\windows\temp and C:\Users\%UserName%\AppData\Local\Temp Delete all EventViewer logs Save to another Disk if you want to keep them Remove any unused programs, e.g. Firefox Remove anything in C:\inetpub\logs Remove any file/folders C:\Windows\System32\LogFiles Remove any file/folders from C:\Users\%UserName%\Downloads Remove any file/folders able to be removed from C:\Users\%UserName%\Desktop Remove any file/folders able to be removed from C:\Users\%UserName%\My Documents Stop Windows Update service and remove all files/folders from C:\Windows\SoftwareDistribution Deleting an Event Logs Run COMPCLN.exe Move the Virtual Memory file to another disk However this wasn’t enough & I found the most space was

Consuming the SSRS ReportExecutionService from a .NET Client

  I’ve just finished writing a nice wrapper which internally calls the SSRS ReportExecutionService to generate reports. Whilst it was fairly simple to implement there has been some major changes between 2005 and 2008 and the majority of online and documentation is based on the 2005 implementation. The most important change is that the Report Server and Report Manager are no longer hosted in IIS which will be a welcomed change to Sys Admins but makes the security model and hosting model vastly different. So far I’ve yet to figure out how to allow Anonymous Access, if anyone knows how to do this leave a comment and it will be most appreciated. Getting Started To get started you’ll want to add a service reference to http://localhost/ReportServer_SQL2008/ReportExecution2005.asmx where ReportServer_SQL2008 is the name you configure in the Reporting Services Configuration Manager. The Web Application files are located in C:\Program Files\Microsoft SQL Server\MSRS10.SQL2008\R