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.


  1. Hi there Will, So what you are saying you were not to pleased with the services of GoGrid and you made the switch to EC2, thnak you by the way for your execellent explanation of the migration, I think many can use thsi as valuable information. !
    1 question however: you found the services of Gogrid rocky , what have you experienced with them, bad performance , outages, datamisconnections ? they claim to have 100% uptime and SLA. What went wrong with their idea!

  2. Hi Ron,

    Performance, pricing, uptime and support (most of the time) were all very good with GoGrid.

    My experience with MyGSI was not a good one and cost a lot of time and frustration. In general the MyGSI feature is along way behind what Amazon EC2 offers and the release cycle IMO is too slow compared with EC2.

    I've outlined some of the frustrations in previous posts:

  3. I found this blog in search results while i am searching for aws jobs in hyderabad. Thank You admin sharing for this information. Which is useful for me.


Post a Comment

Popular posts from this blog

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

CPF Contribution Rates for new Singapore Permanent Residents (SPR’s)

Recently my wife and I applied and got approved for Singapore Permanent Residency. After completing the formalities the most significant immediate change is the contribution to CPF which is Singapore’s mandatory social security savings scheme requiring contributions from employers and employees. CPF contributions start from the date you obtain SPR status, which is the date of the entry permit.   Being a relentless budgeter I needed to know exactly how much I and my employer would have to contribute so that I could adjust my budget accordingly as the employee contributions get deducted from the monthly salary. After doing some research I discovered that there is a “graduated” approach to CPF contributions for new SPR’s where the contributions gradually increase in the first and second year and then upon reaching the third year are at the full amount. Note: There is an option for employers to contribute the full amount for year 1 and year 2 and the employee can use the graduated ra

Populating Duplicate Fields with DocuSign's REST API

If you're using DocuSign's REST API for integrating e-Signing into your application then it's possible you'll come up against the issue of duplicate fields not populating. This is when you have the same field with the same label e.g. Company Name in multiple places on the Document but you only want to send a single label, value instance to the API and have it populate in all places where the field is. When you pass the label and value like so: { label: "company_name", value: "" } If you have the field company_name more than once in the document then only the first field will be populated. After a lot of digging into the DocuSign documentation I discovered the solution is to append "\\*" to the label name: { label: "\\*company_name", value: "" } Why this isn't the default behaviour is beyond me but the solution works as expected. DocuSign Rest API Documentation