# Building an Amazon Discourse pilot, planning for scale

**URL:** <https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458>\
**Category:** Self-hosting\
**Created:** [June 9, 2016, 3:59am UTC](https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458 "2016-06-09T03:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [June 9, 2016, 4:25am UTC](https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458/4 "2016-06-09T04:25:39Z")

</div>

The best documentation is our own [30 minute install guide](http://blog.discourse.org/2014/04/install-discourse-in-under-30-minutes/). The DO one-click installer forces you to use a bigger droplet than you really need. If all you want to do is run a single VM you can do that on AWS, too, but it won’t be “the AWS way”, taking advantage of their proprietary features to more easily manage and scale the setup.

It’s easy to move a Discourse instance from one hosting provider to another, provided you’re using our Docker setup – copy the container defintion YAML file out of `containers` onto the new host, bootstrap/start, then take a backup of the data from the old and load it into the new.

---

_[View the full topic](https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458)._
