Linux Test Drive Deployment

This document explains how to deploy InsightCloudSec quickly and simply for evaluation purposes using Docker Compose. If you install InsightCloudSec locally, it should take less than 15 minutes to get up and running.

Product name to be replaced

You may observe that some components, screen captures, or examples use our former product name, DivvyCloud. This doesn't affect the configuration or the product's functionality, and we will notify you as we replace these component names.

If you have questions or issues feel free to reach out to us through the Customer Support Portal.

Prerequisites and Minimum System Requirements

When deploying a test drive for InsightCloudSec, we recommend the following minimum specifications:

  • VM: 4 CPU cores - 16GB memory - 40GB storage
  • OS: Ubuntu 18.04 (Recommended), Amazon Linux, SuSE or RHEL/CentOS

Some cloud-based virtual machines that meet these specs:

  • AWS: t2.xlarge, t3.xlarge
  • Azure: D4as v5, D4ads v5, D4a v4, D4d v5
  • GCP: e2-standard-4, n2-standard-4, n2d-standard-4

The default deployment creates a self-signed certificate for use with the InsightCloudSec platform. To use your own certificate you will need the cert and key files to place on the machine once InsightCloudSec is installed.

InsightCloudSec also requires some outbound network connectivity. Full details can be found on the Product Architecture page.

In addition, to test the requirements outlined above, InsightCloudSec provides a pre-flight check script, located here: curl -s | sudo bash

Linux Installation

To simplify installation you can run this script which will install Docker and Docker Compose if they are not installed, pull down the InsightCloudSec Docker image and run our standard compose file.

curl -s | sudo bash
# To see the containers, use ``docker ps``

If you would like to install Docker community edition and docker-compose on your own, follow the instructions below. Otherwise, continue with Logging into InsightCloudSec.

Install Docker and Docker-Compose

First, you need to install Docker Community Edition and Docker Compose.

Next, add this docker-compose.yml file to your present working directory:

curl -sO
curl -s -o docker-compose.yml

Start InsightCloudSec with Docker Compose

Now you are ready to start InsightCloudSec. To run in the foreground and see logging information in your terminal, use:

docker-compose up

or to run in the background, use:

docker-compose up -d

Logging into InsightCloudSec

After InsightCloudSec has completed its launch, you can connect via browser using https. InsightCloudSec test drives use a self-signed certificate, so you'll need to accept the warning/dialog to connect.

  1. The first page is an administrator account creation page. On the page, enter your name and email address and create a userid and password.
    • Your userid can be any alphanumeric characters.
    • Your password must be at least 12 characters in length.
  2. Login with the administrator account credentials you just created.

Stop InsightCloudSec with Docker Compose

When your evaluation is over (and we hope you enjoyed it) and you’re ready to stop, use:

docker-compose down
# Exit with ``Ctrl-C`` if running in foreground

Unnecessary Costs

Remove any cloud-based instances once your test drive is finished to avoid incurring unnecessary costs!

Running Docker Compose on Instance Boot

You can have InsightCloudSec start on instance boot using crontab, but instead of using a time interval, use @reboot. In order to do so, switch to the user who will start docker-compose, enter the command crontab -e to open the crontab editor and add the following line:

@reboot /<path-to>/docker-compose -f /<path-to>/divvycloud/docker-compose.yml up -d

Using a Proxy Server

If you wish to use a proxy server for your Test Drive, you will need to add your proxy information to the following:

  • System’s environment variables before your installation
  • InsightCloudSec environment variables after your installation