Recommended minimum server sizes

Although most cloud providers offer servers with the minimum specs required to run Ubuntu, we do not recommend using these, even for testing. We recommend the following minimum specs for any virtual machine being used to host an application or one of its components (such as a database):

  • At least 2GB of RAM
  • At least 4 vCPUs
  • At least 25GB of storage

Potential consequences of using under-powered servers

Using any of these server sizes may result in slow response times and intermittent downtime. Some applications may not function at all with the limited headroom afforded by these machines.

In particular, Elasticsearch on a standalone under-powered server will not start up. This is because we configure Elasticsearch to lock its memory and prevent swapping on standalone servers as per the official recommendation, and there is simply not enough memory for it to run it successfully.

Depending on whether or not you have deployed your application elsewhere, it may be hard to gauge the amount of resources that you need. On a PaaS like Heroku for example, you can choose between 1X (512 MB), 2X (1 GB) and PX (6 GB) server sizes. This makes it easy to calculate your server requirements, and we recommend that you use similar server resources when deploying your application with Cloud 66. We also recommend that you have a seperate server for your database in production environments.

If you haven't deployed your application in a production environment yet, you can deploy to a reasonably sized server and use load testing to determine your exact needs.

The following server sizes are not recommended (especially not in production). Some of these may only be available via Registered Servers.

Amazon Web Services

  • t1.micro
  • t2.micro


  • 512 MB - General Purpose


  • 512MB - 1 CPU

Google Compute Engine

  • f1-micro

Microsoft Azure

  • A0


  • Cloud Compute - 1 vCPUs - 1024 MB RAM - 25 GB SSD - 1.00 TB BW
  • Cloud Compute - 1 vCPUs - 2048 MB RAM - 55 GB SSD - 2.00 TB BW
Managing required restarts