Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views

General Why Troll Purse Migrated to AWS

Martin H Hollstein


Originally posted on Troll Purse Dev Blog

Recently, Troll Purse made the decision to migrate from the cloud in Digital Ocean to Amazon Web Services for cloud and website services. There were several reasons behind this critical decision. These reasons are infrastructure, flexibility, and future plans.



Digital Ocean has a nice setup. They have a slick looking User Interface, easy to find services, and awesome community driven documentation. Troll Purse quite liked Digital Ocean if not for a few issues regarding infrastructure in comparison to Amazon Web Services (AWS).


Digital Ocean was not overly expensive. However, their base monthly rate ($5 / month + $1 / month for backups), was still higher than hosting a static website on AWS. This is because, to host a static website and blog, Digital Ocean achieves this via Droplets. This does not scale the wallet very well - especially if traffic started to boom. Digital Ocean only offers referral bonuses. So, if we were famous - we could potentially host everything for free. Big gamble at this moment.

AWS charges $0.50 / month forRoute 53 (DNS Name Servers) and a variable cost for S3 storage of our static website content. Based on traffic trends, the variable costs of AWS were a huge benefit. Finally, it helps that AWS offers a full year of various resources for free.

Continuous Delivery

Digital Ocean had a lot of APIs for Continous Delivery of our website, but it didn't offer a full suite of solutions for proper Developer Operations. Digital Ocean would require a lot of extra Developer Operations overhead writing build and deployment scripts using their APIs. AWS integrates with Bitbucket and Github - two services we use for source control. AWS also offers managed build and deployment services that Troll Purse will be leveraging.


Digital Ocean is limited to Droplets. This pales in comparison to AWS's robust EC2, ECS, or serverless services. In AWS, Troll Purse can decouple services and code for various solutions. To do the same distributed computing in Digital Ocean as Troll Purse is enabled to do in AWS would require a significant investment in architecting infrastructure. In AWS, this is vastly done for Troll Purse - once an architecture is designed, only configuration of the services need to be done.

With Digital Ocean, Troll Purse had to setup an Nginx server for serving static website content. It did not scale well (without more invested time in building an architecture and more configurations) as all content was stored on that server. In AWS, Troll Purse can distribute web content using Cloud Front for CDN and server static content from S3. Totally serverless and decoupled from the blogging platform and the forum servers (the latter is yet to be deployed).


In Digital Ocean it was difficult to manage servers and logical groupings of services. AWS offers tagging of resources and services to help better monitor health, costs, and grouping of application services built and provided by Troll Purse.

Unfortunately, Digital Ocean does not offer the robust services and infrastructure needed for a company built with development speed in mind. A lot of services need to be hand crafted, as well as servers. This slows development efforts and makes iterative development a nightmare. Using small, simple services each with a specific purpose in mind, Troll Purse is better able to develop an experiment based on the offerings provided by AWS.

Digital Ocean only provides five real services, Compute, Object Storage, Block Storage, Networking, and Monitoring. Each of these are small in comparison to comparable AWS services such as Compute Services (ECS or EC2), Storage, Virtual Private Cloud (Networking), and Cloud Watch (Monitoring). In AWS each of those services / categories work with each other or are umbrellas to a myriad of other flexible offerings.

Finally, AWS has way more to offer - just take a look!

Future Plans

After much discussion, Troll Purse concluded our future development needs will be implemented faster and scale naturally in AWS over Digital Ocean. While we enjoyed our brief experience with Digital Ocean, we are excited to build using AWS as our cloud and hosting provider.

While we do not plan to build anything with Lumberyard now, we have some exciting projects that will easily leverage the power of AWS. Such projects are backend analytics of our games using Amazon API Gateway, Lambda, and data services. We also hope to build an integrated environment so that each game shares common interfaces into our development and publishing environment. 


While this blog post is mostly given as an explanation of our tactical decision to migrate to AWS, Troll Purse hopes it will serve as guidance to future developers facing the same decisions. We found that AWS provides a lot for small and large companies when it comes to infrastructure, flexibility, and accommodating future plans.

Originally posted on Troll Purse Dev Blog


Recommended Comments

Thanks for sharing your experience!

Did you consider any other options (such as Google's services) or just Digital Ocean and AWS?

I'd be interested to hear why other options were discarded if any were considered. :)

Share this comment

Link to comment
4 hours ago, jbadams said:

Thanks for sharing your experience!

Did you consider any other options (such as Google's services) or just Digital Ocean and AWS?

I'd be interested to hear why other options were discarded if any were considered.

No problem jbadams! Always glad to help. 

I had looked into Google cloud services, but the lack of community and, what seemed to me features for the cost, turned me off. It may have also hurt that configuration for service integration in Google cloud seemed wonky at best ( I had started to set up a Google Home integration service). The reason being is that there are configuration options in the console not only for Google cloud, but also for all of their other services (Google+ for instance). This made it feel like a management nightmare.

I have experience in Azure, but I found it too rigid. If I was planning on going full Windows Stack, I may have actually gone with Azure. But, from past experience, the simple act of running the equivalent of an AMI was expensive. I actually had to shut down a repo server due to the overwhelming cost. I had also deployed a game out to Azure as well . It still runs but I found managing infrastructure a nightmare in Azure.

AWS was a natural fit (disclaimer: I have since become a certified Solutions Architect) for what I wanted to achieve. Fast iterations of cloud infrastructure, simple UI on the web and a sensible CLI. From previous experience, I had deployed a defunct game and editor to AWS back in 2013/2014. That was the smoothest and most straight forward experience I had with cloud infrastructure.

Now, I do find AWS great, but one thing that peeves me off right now is the lack of Dev Ops for Windows builds. I really want to use CodeBuild, CodeCommit, CodeDeploy (might as well as use CodePipeline at that) to start deploying and distributing ALL of my game builds in UE4. However, at this point, I will have to provision an AMI to build Windows, which means deploying a CI tool as well (such as Jenkins).


I hope you find that information useful. If you have any other questions, feel free to ask! I really enjoy conversation and feedback.

Share this comment

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!