System requirements

Review system requirements for deploying Tellius across on-prem, AWS, or Azure, including CPU, memory, storage, firewall ports, and access guidelines.

The following are the minimum requirements for installing and deploying Tellius. The guidelines are designed to ensure a secure and reliable installation. Tellius team requires certain access privileges, which shall be revoked or limited after successful installation. If you have any questions, feel free to email us at [e-mail].

As a best practice, access the application via DNS name and perform DNS mapping with support from your IT team.

SSL certificates need to be generated and shared (.key, .pem files) with the Tellius team.

For single-instance deployments

Infrastructure requirements

• 64 Core CPU (amd64 architecture)

• 512 GB RAM

• 50 GB Root disk size

• 2 TB external disk size for Tellius data storage (persistent disk), formatted using ext4 filesystem

• Ubuntu-20 operating system (Alternatively, RHEL 7.x)

• Internet connectivity during installation of container runtime and Kubernetes software

Accessing Tellius UI

• Access using the IP address of the instance unless you have any hardware load balancer in place.

Ports to be opened via firewall

• 443 for Tellius frontend application

• 956938892320.dkr.ecr.us-east-1.amazonaws.com for private container registry hosted by Tellius to store application Docker images

• Any other required ports depending on the type of data source connectivity

Level of access

• Tellius team will be given sudo privileges during the installation of container runtime and Kubernetes.

• Tellius deployment and platform management can be done by non-root user accounts with the least sudo privileges.

• Tellius team can directly access customer-provisioned instances using IP white-listing or any preferred method used in your environment.

For AWS deployment

Infrastructure requirements

• R4 or R5.16xlarge instance type

• EKS cluster with either single or multiple worker nodes

• Kubernetes version 1.21 or 1.22 (depends on the latest stable version available)

• Amazon Certificate Manager ARN for accessing Tellius UI securely

• Tellius team creates dynamic EBS volume for all Tellius stateful set applications

Accessing Tellius UI

Since Tellius uses AWS Certificate Manager (ACM), the UI can be accessed securely.

• Tellius team will be creating a Kubernetes load balancer serviceType for the frontend application. It can be done internal-facing or external-facing as required.

Ports to be opened via firewall

• 443 for Tellius frontend application

• 956938892320.dkr.ecr.us-east-1.amazonaws.com for private container registry hosted by Tellius to store application Docker images

• Any other required ports depending on the type of data source connectivity

Tools required

• Kubernetes command-line tool (kubectl v1.20 or higher) installed on a jump-host/bastion

• Kubeconfig file for connecting to EKS cluster from jump-host/bastion

• Git command-line tool for accessing Kubernetes manifest stored on Tellius's private GitHub repository

For Azure Deployment

Infrastructure

• standard_e64s_v3 instance type (64 CPU cores, 512 GB RAM)

• AKS cluster with single or multiple nodes inside a node pool

• Kubernetes version 1.21 or 1.22 (depends on the latest stable version available)

• Tellius team will create dynamic Azure disks for all Tellius stateful set applications

Accessing Tellius UI

• Tellius team will be creating a Kubernetes load balancer serviceType for the frontend application. It can be done internal-facing or external-facing as required.

Ports to be opened via firewall

• 443 for Tellius frontend application

• 956938892320.dkr.ecr.us-east-1.amazonaws.com for private container registry hosted by Tellius to store application Docker images

• Any other required ports depending on the type of data source connectivity

Tools required

• Kubernetes command-line tool (kubectl v1.20 or higher ) installed on a jump-host/bastion.

• Kubeconfig file for connecting to EKS cluster from jump-host/bastion

• Git command-line tool for accessing Kubernetes manifest stored on Tellius private GitHub repository

Deployment guidelines

For cloud-based deployment

• Tellius deploys nginx ingress controller which internally creates a network load balancer.

• Tellius’s deployment manifest is stored inside a private registry on GitHub.

• Disk encryption will be enabled for all dynamic volumes created by stateful set applications.

• Tellius follows the GitOps principle where automated application deployment is done via ArgoCD (in addition to supporting other CD tools).

• Access is required for Tellius team members to manage application deployment and troubleshooting

• The application Docker images are stored inside a private registry managed by Tellius on AWS (ECR).

For on-prem deployment

• Tellius team members require access for installing platform components installation (Kubernetes, container run-time) and managing/troubleshooting application deployment.

• Tellius’s deployment manifest is stored inside a private registry on GitHub.

• The application Docker images are stored inside a private registry managed by Tellius on AWS (ECR).

• The deployment will be done manually by the Tellius team.