ZebClient
Zebware.comCustomer Portal
  • ZebClient Documentation
  • Product Overview
    • Introduction to ZebClient
    • Functional Overview
    • Product Components
    • Data Flows
    • Data Striping
  • USE CASES
    • ZebClient Analytics
      • Architecture
        • Data Pipeline
        • Data Storage
        • Consumption
      • Deploy a ZebClient Advanced Cluster
        • Step 0 - Setup
      • FAQ
  • Planning & Getting Started
    • How to Choose your Deployment Mode
    • Deployment Modes and Tuning
    • Performance
    • License
    • Order Your ZebClient License
    • Pricing
  • Installation
    • Types of Installations
    • Guided Installation
      • ZebClient with Azure Blob Storage
        • Defining Backend with Azure Blob Storage
        • Mounting ZebClient with Azure Blob Storage
      • ZebClient with AWS S3
        • Defining Backend with AWS S3
        • Mounting ZebClient with AWS S3
      • Mount Additional Agent Node
    • Kubernetes
      • Azure Quickstart Guide
      • ZebClient CSI
      • ZebClient Helm
      • ZebClient Terraform
    • Virtual Machines
      • Azure Installation Guide
        • Installing Using Terraform
        • Uninstalling Using Terraform
    • Checking Installation
    • Running First Test
  • Management HOW-TOS
    • Add a New Agent VM into an Existing Cluster
    • Retrieve Cluster Log Files
    • CloudFormation Deployments
      • Understanding our CloudFormation Template
      • Uninstalling Using CloudFormation
    • Command-line Interface
  • Operations & Monitoring
    • Importing Your Data
    • Inlets
      • Data from External S3 Bucket
    • System Recovery Guide
      • Restore KeyDB Backup from S3
    • Port a Deploy
    • Add Resources to a Cluster
      • Add Application Node to Existing Machine (Manually)
      • Add Application Node to Existing Machine (via zc-cli)
      • Add New Application Node
      • Add Jumpbox
    • Verifying License Validity
    • Monitoring Your ZebClient Cluster with Netdata
Powered by GitBook
On this page
  • Install Blob Storage and Database Node
  • The Goal of This Step
  • Prerequisites
  • Authenticate with Azure CLI
  • Supply Necessary Details for the Terraform Deployment
  • Deploy the Terraform Script
  1. Installation
  2. Guided Installation
  3. ZebClient with Azure Blob Storage

Defining Backend with Azure Blob Storage

PreviousZebClient with Azure Blob StorageNextMounting ZebClient with Azure Blob Storage

Last updated 1 year ago


Install Blob Storage and Database Node

The Goal of This Step

The goal of this step is to set up the storage resources needed for ZebClient. The following components will be deployed in your cloud environment:

  • 1 x db node: Standard D4s v4

  • 1 x Azure blob storage container

The above two components are the minimum requirements for running the ZebClient agent on any machine e.g. your workstation.

Prerequisites

  • A ZebClient license: A trial license can be ordered for free from www.zebware.com/store.

Install Azure CLI

You can obtain Azure CLI and consult the documentation here:

curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

Install GIT

Install Terraform

Authenticate with Azure CLI

Once all your dependencies are installed, run az login and authenticate with your credentials.

az login

Supply Necessary Details for the Terraform Deployment

Once authenticated, it's time to check out our git repository which will help you get started.

git clone https://gitlab.com/zebware/public/azure-zebclient-start.git

Switch your directory to checked out repository:

cd $(pwd)/azure-zebclient-start

Then copy the tfvars file:

cp examples/start.tfvars terraform.tfvars

Update the contents of the terraform.tfvars file accordingly

# Azure general
prefix = "<your prefix>" # your cluster's name. Cannot contain the special characters: `\/"[]:|<>+=;,?*@&~!#$%^()_{}'`
location = "<azure region>" # Azure region

# ZebClient
zebclient_license_key = "<your ZebClient license key>" # Provide the "zebClientLicense" part of your zebclient license json file.

# Allow access to your resources on Azure
public_access_cidrs = ["<your ip address>"] # IP addresses that will be allowed to access the cloud resources: the db and the blob storage i.e. [ "xxx.xxx.0.0/16", "xxx.xxx.xxx.xxx/32" ]

To quickly obtain an external IP address of your machine you can run;

curl http://checkip.dyndns.org and obtain external IP that you can use with confidence when setting public_access_cidrs value.

Once this is done save your changes, and you are ready to deploy!

Deploy the Terraform Script

Run the following commands to start the deployment process:

terraform init
terraform plan -out main.tfplan
terraform apply main.tfplan

The deployment process will now start and take a couple of minutes. When it's done, you should see the following output:

_1_keydb_public_ip = "xxx.xxx.xxx.xxx"
_2_keydb_password = "your database password <sensitive>"
_3_zebclient_license = "your ZebClient license <sensitive>"
_4_azure_storage_account_access_key = "your Azure storage account access key <sensitive>"
_5_azure_storage_account_name = "zc{your prefix}"
_6_azure_container_name = tolist([
  "zc{your prefix}",
])
_7_azure_storage_account_endpoint = "https://zc{your prefix}.blob.core.windows.net"
_8_ssh_key = "Your keypair to ssh to the resource on azure i.e. the db node. <sensitive>"

For security reasons, some of the values are hidden. To reveal them, use the command in the example:

terraform output _4_azure_storage_account_access_key

It will print out the value you need. In the next step, you can use it with other sensitive values like _2_keydb_password and others. It is recommended to use two (2) terminal windows for convenience.

Example: If you are using use the following command.

If you need alternative ways to authenticate with Azure CLI check .

Ubuntu or Debian
this section
Install the Azure CLI on LinuxMicrosoftLearn
Logo
Install Git | Atlassian Git TutorialAtlassian
Install | Terraform | HashiCorp DeveloperInstall | Terraform | HashiCorp Developer
Logo
Logo