Going off the Grid: Part 3 – Console Commander

Greetings! If you haven’t already read Part 1, or Part 2, do so now. Today we’ll be going over the stuff you’ll need in order to host your services. We’ll be using Ubuntu all the way for it’s ease of use for beginners especially at the console. So fire up an AWS account if you haven’t already and let’s get to it!

If you’re at the dash you’ll want to go to Route 53 which can be found in the options or by typing it into the search bar(note you can use any domain registrar, but some may find it convenient to have it all in one place). Set up the domain name of your choice. Now head over to the EC2 service on the AWS website. Create an EC2 instance choosing the AWS Ubuntu distro as your OS, most of the services we’ll be using support it and usually have easy to install packages for their software.

Now that we’ve got a VM we have to decide what kind of setup we want. There are a bunch of ways to host a litany of services, so let’s go over each of them in detail.


This is perhaps the more complex option but you could install docker an open source container service that will let you host multiple services on the same VM whilst letting them separate from each other. This is definitely more cost effective, as it allows your services to share hardware and the kernel.

Virtual Machines!

If you elect to host each of your services on a separate VM, your cost will be higher, but you may find higher performance and responsiveness.  So ultimately this choice will be yours to make, and will be dictated by what you as a person value: performance or value.

Now that your VM is setup you’ll want to setup your network(there is an option when you create the VM to add a network). There are quite a few ways to set this portion up but typically you’ll want to expose the ports that your application uses to the world. In most cases this involves leasing an elastic IP and assigning it to a VM. If you have multiple VMs and don’t want to lease more than a single static IP you can setup a reverse Proxy, but we’ll cover that in a later article.

Once you’ve got the network setup you’ll want to setup your domain to point to the IP we just leased. Now that your domain is setup and your network is open you should be good to go to setup your service and deploy!

Though I used AWS in this article, the same principles apply to any particular web based service.


Leave a Reply

Your email address will not be published. Required fields are marked *