Hosting & Tech Specs

Zuar Runner can be hosted in either of two deployment scenarios:

  • Zuar hosted: Zuar deploys and maintains the application in its own infrastructure

  • Customer hosted: (also known as “self hosted”) the customer provides IT infrastructure for hosting the application, Zuar deploys and upgrades

This document describes both options and system requirements.

Zuar Hosted Runner

Runner is hosted by Zuar in Zuar’s AWS or Digital Ocean accounts. The customer does not need to provision any servers for Runner in this scenario however they still may need to provide network connectivity to data sources and/or targets. Work with Zuar to determine connectivity requirements for your use case. Specifications about your deployment can be found on Zuar Runner’s Settings page.

Zuar hosted Runner requires two-factor authentication:

  1. Username and password - Admin credentials are required to access Zuar Runner’s UI and database

  2. IP allow-list - Users must access Zuar Runner’s UI and database from an IP address that has been added by Zuar to the Runner instance’s allow-list (submit a Support ticket if you need an address added or removed)

Customer Hosted Runner

Runner is hosted by the customer in your public/private cloud (AWS, Azure, GCP, etc) or on-premise infrastructure.

Tech Specs (Hardware Requirements)

Note

Zuar Runner can be scaled according to data volumes and use cases.

Server Minimum Requirements

This configuration is recommended for POCs, testing, etc. and is not recommended for production Zuar Runner instances.

Component

Value

Operating System

Ubuntu 22.04

CPU

2 Core

Memory

4 GB

Disk

80 GB

Amazon AWS EC2 equivalent: t2.medium

Operating system requirements

Zuar Runner’s server must have Ubuntu 22.04 LTS installed. Other versions and operating systems are not supported.

No other applications should be installed.

Zuar Runner must be installed and run as the Ubuntu account with user id (uid) 1000. This is typically the first user account created during the installation of the operating system. The user must have root access.

Network connectivity

Zuar staff requires network access to the Zuar Runner instance for deployment, troubleshooting, and maintenance via SSH and/or VPN. Coordinate with your Zuar team to setup.

The Zuar Runner installation process, future upgrades, licensing, and operation require access to the following domains via the public internet. Air-gapped deployment is not available. These domains communicate via HTTPS (port 443) unless otherwise indicated:

  • licensing3.zuarbase.net

  • vault.zuarbase.net (port 8200)

  • amazonaws.com

  • pypi.org

  • github.com

  • docker.com

  • elastic.co

  • in-v3.mailjet.com (port 587 TLS SMTP, required if using Runner’s default service for job notification emails)

See the Data source network connectivity section below for further network considerations specific to your data sources and targets.

DNS/SSL

A hostname/domain name and matching SSL certificate will need to be assigned to the Zuar Runner instance. Wildcard SSL certificates are supported and access to the private key file is required.

Datasource network connectivity

Zuar Runner needs network access to any source and destination data sources. Data sources include databases, API endpoints, files (e.g. SFTP, file storage providers). Each data source will have it’s own domain, port, and allow list requirements. Work with Zuar and your internal IT/BI teams to determine what connectivity will be needed. Here are some typical paths that may need to be considered:

  • HTTP/HTTPS (80, 443) - Runner Admin UI, APIs, Snowflake

  • SSH/SFTP (22) - Zuar deployment access, SFTP servers

  • Runner’s built-in PostgreSQL database (5432)

  • Databases (default ports unless otherwise configured) - PostgreSQL (5432), MSSQL (1433), etc.

  • Passive FTP (40000-40100)

Zuar Runner Database

Zuar Runner’s internal database is currently PostgreSQL 13.20. This database is used to store Runner metadata, configuration, job history, and more.

Zuar Runner can also use this PostgreSQL database as the analytics database. Customers may choose to have Zuar Runner pipe some or all data into alternative database(s) (cloud or self-hosted). If Zuar hosts the alternative destination database, the cost is added to the Zuar Runner subscription.