Skip to main content

Installing Coginiti Team

This guide walks you through the complete installation process for Coginiti Team, from initial setup through final configuration and login.

Deployment Options​

Coginiti Team can be deployed using several methods:

AWS Marketplace

  • Pre-configured deployment on AWS infrastructure
  • One-click deployment with CloudFormation templates
  • Pricing managed through external billing relationship with Coginiti
  • Access via browser at https://<public_dns>
  • Admin console accessible at http://<instance_public_ip>:30000
  • Deploy: AWS Marketplace - Coginiti Team

Google Cloud Marketplace

  • Google Cloud Ready – BigQuery certified deployment
  • Optimized for Google Cloud infrastructure and services
  • Seamless integration with AlloyDB for PostgreSQL and Google Cloud SQL
  • Streamlined procurement through Google Cloud billing
  • Deploy: Google Cloud Marketplace - Coginiti Team

2. Self-Hosted Installation​

For organizations requiring full control over their deployment infrastructure, Coginiti Team can be installed directly on your own servers or cloud instances using the manual installation process detailed below.

Manual Installation Process​

Marketplace vs Manual Installation

If you're deploying from AWS or Google Cloud Marketplace, follow the marketplace-specific deployment process instead of the manual installation steps below. The marketplace deployments handle infrastructure provisioning automatically.

Prerequisites​

Before beginning the installation, ensure you have completed all system requirements. See the System Requirements Reference for complete specifications.

Quick Checklist​

  • ✅ Server: x64 virtual machine with 8 cores, 32GB RAM, 256GB disk
  • ✅ Operating System: Supported Linux distribution with container runtime
  • ✅ Database: PostgreSQL 16.x with pg_vector extension enabled
  • ✅ SSL Certificate: PEM-encoded certificate and key files (no passphrase)
  • ✅ Network: Fixed static IP, DNS entry, firewall rules configured
  • ✅ License: Coginiti license file received from Account Manager

Installation Overview​

The installation process consists of two main phases:

  1. Phase 1: Initial installation using command-line installer
  2. Phase 2: Web-based configuration through admin console

Phase 1: Initial Installation​

Step 1: Receive License and Installation Command​

Your Coginiti Account Manager will email you:

  • License file (.yml extension)
  • Installation command specific to your instance

Example license email:

From: Coginiti Licensing Portal <licensing@coginiti.co>
Subject: Replicated customer created

Hello John Doe,

Please find below the installation command for your Coginiti Premium 
instance and your License attached.

curl -sSL https://k8s.kurl.sh/coginiti-premium-develop | sudo bash

If you have any questions - please contact licensing@coginiti.co
Important

The installation command in your email will be different from the example above. Use the exact command provided in your licensing email.

Step 2: Execute Installation Command​

  1. Connect to your server via SSH as a user with sudo privileges:

    ssh user@your-coginiti-server.com

  2. Run the installation command provided in your license email:

    curl -sSL https://k8s.kurl.sh/coginiti-premium-develop | sudo bash

  3. Monitor the installation progress. The installer will:

    • Download required packages (3-4 GB)
    • Install container runtime and dependencies
    • Set up Docker environment for Coginiti Team
    • Configure network and storage components

Step 3: Save Admin Console Credentials​

When installation completes, the script displays important information:

Installation
    Complete ✓

The UI of Prometheus, Grafana and Alertmanager have been exposed on NodePorts 30904, 30902 and 30903 respectively.

To access Grafana use the generated user:password of admin:BtyJdp2VGN3 .

Login with password (will not be shown again): WqinBuov
This password has been set for you by default. It is recommended that you change this password; this can be done wi
th the following command: kubectl kots reset-password default

To access the cluster with kubectl, reload your shell:

    bash -l

Node join commands expire after 24 hours.

To generate new node join commands, run: curl -sSL https://kurl.sh/versions/v2022.10.21-0/coginiti-premium-develop/j
oin.sh | sudo bash -s kubernetes-master-address=172.31.15.244:6443 kubeadm-token=fsjp13.nfolem23y4xv zubeadm-token-c
a-hash=sha256:708608010125fa1f020d13b45dd34f4d10.31.15.244

🔴 Critical: Save the following information:

  • Admin Console URL: https://your-server-ip:8800
  • Admin Password: The password shown in the output (e.g., WqinBuov)
Security Warning

The admin console password is only displayed once. Save it immediately in a secure location.

Phase 2: Web Configuration​

Step 1: Access Admin Console​

  1. Open your web browser and navigate to:

    https://your-server-ip:8800

  2. Accept the security warning for the self-signed certificate (you'll configure your SSL certificate later)

Step 2: Configure HTTPS Certificate (Skip Initially)​

On the "HTTPS for Coginiti Premium admin console" screen:

  1. Click "Skip & continue" to use a self-signed certificate initially
  2. You'll upload your production SSL certificate in a later step

HTTPS Configuration Screen

Certificate Configuration

Skip the initial certificate upload. You'll configure your production SSL certificate after completing the basic setup.

Step 3: Admin Console Login​

  1. Enter the admin password from the installation output
  2. Click "Log in" to access the admin console

Admin Console Login

Step 4: Upload License File​

  1. Upload your license file (.yml file from email):
    • Click "Drag your license here or choose a file"
    • Select the license file sent by your Account Manager
    • Click "Upload license"

License Upload

Step 5: Configure Superuser Account​

Create the primary administrator account:

  1. Superuser Name: Enter the admin username (often the license recipient)
  2. Superuser Password: Create a strong password (minimum 8 characters)
  3. Confirm Password: Re-enter the password to confirm

Superuser Configuration

Step 6: Database Configuration​

Configure the PostgreSQL database connection:

Database Connection Settings​

  1. Postgres Host Type:

    • Select "Postgres Hostname" for external databases
    • Select "Postgres IP Address" if using IP directly

  2. Postgres Instance Hostname: Enter your PostgreSQL server hostname or IP

  3. Name of Postgres Database: Enter database name (e.g., coginiti_db)

  4. Username for Postgres Database: Enter database username (e.g., coginiti_user)

  5. Password for Postgres Database: Enter database password

Database Configuration

Database Setup Commands​

If you haven't already set up the database, run these commands on your PostgreSQL server:

-- Create dedicated user with database creation privileges
CREATE USER coginiti_user WITH CREATEDB PASSWORD 'your_secure_password';

-- Create dedicated database owned by Coginiti user  
CREATE DATABASE coginiti_db OWNER coginiti_user;

-- Connect to Coginiti database and enable vector extension
\c coginiti_db
CREATE EXTENSION vector;

Verify Database Connectivity​

Test the connection from your Coginiti server:

echo "SELECT extname FROM pg_extension WHERE extname = 'vector';" | \
psql postgresql://coginiti_user:password@pg_hostname:5432/coginiti_db

Expected output:

extname 
---------
vector
(1 row)

Step 7: Encryption Configuration​

Configure encryption keys for securing sensitive data:

  1. Encryption Settings: Choose "Generate Encryption key and JWT secret" for new installations
  2. Save the generated keys: The system will display encryption key and JWT secret

Encryption Configuration

Critical Security Information

SAVE YOUR ENCRYPTION KEY AND JWT SECRET in a secure location. These are essential for:

  • Reinstalling the system
  • Recovering from backups
  • Migrating to new infrastructure

Without these keys, encrypted data cannot be recovered.

Step 8: Domain and SSL Configuration​

Configure your production domain and SSL certificate:

  1. Ingress Hostname: Enter your Coginiti domain (e.g., coginiti.yourcompany.com)

  2. TLS Configuration:

    • Private Key: Upload your .key file
    • Certificate: Upload your .crt file

Domain and SSL Configuration

SSL Certificate Verification​

Before uploading, verify your certificate and key match:

# Check certificate modulus
openssl x509 -in server.crt -noout -modulus | openssl md5

# Check private key modulus
openssl rsa -in server.key -noout -modulus | openssl md5

# Both should return identical hash values

Step 9: Preflight Checks​

The admin console runs preflight checks to validate your configuration:

Preflight Checks

Common preflight checks:

  • ✅ Required Kubernetes Version
  • ✅ Container Runtime
  • ✅ Check Kubernetes environment
  • ✅ Total CPU Cores in the cluster is 6 or greater
  • ⚠️ Check Licensing Portal is available (may warn for air-gap)
  • ✅ Check Bugsnag is available
Air Gap Installations

Air-gapped installations may show warnings for online service checks. This is expected and normal.

Click "Continue" when preflight checks pass.

Step 10: Deploy Application​

The admin console will deploy Coginiti Team:

  1. Monitor deployment progress in the admin console
  2. Wait for all services to start (this may take several minutes)
  3. Verify successful deployment when status shows "Ready"

Deployment Progress

Post-Installation Verification​

Step 1: Access Coginiti Application​

  1. Open a new browser tab and navigate to your configured domain:

    https://coginiti.yourcompany.com

  2. Login with superuser credentials created during setup

Coginiti Team Application

Step 2: Verify License Application​

The license should be automatically applied. You can verify by:

  1. Check the license information in the application interface
  2. Confirm user limits match your license agreement
  3. Verify expiration date is correct

Step 3: Initial Configuration​

Complete these initial setup tasks:

  1. Configure user accounts and permissions
  2. Set up database connections to your data sources
  3. Configure authentication (SSO, LDAP if required)
  4. Test basic functionality with sample queries

Troubleshooting​

Common Installation Issues​

Installation Command Fails​

Symptoms: Installation script exits with errors

Solutions:

  1. Verify system meets all requirements
  2. Check internet connectivity for package downloads
  3. Ensure sufficient disk space (256 GB minimum)
  4. Verify Docker/container runtime is compatible
  5. Run with verbose logging: bash -x install_script.sh

Admin Console Inaccessible​

Symptoms: Cannot access admin console on port 8800

Solutions:

  1. Verify server is running: systemctl status docker
  2. Check firewall allows port 8800: ufw status
  3. Confirm installation completed successfully
  4. Check for port conflicts: netstat -tulnp | grep 8800

Database Connection Fails​

Symptoms: Database connectivity errors during configuration

Solutions:

  1. Test database connectivity from Coginiti server
  2. Verify PostgreSQL is running and accepting connections
  3. Check firewall rules allow database port (5432)
  4. Confirm pg_vector extension is installed
  5. Verify database user permissions

SSL Certificate Issues​

Symptoms: Certificate upload fails or HTTPS errors

Solutions:

  1. Verify certificate format is PEM-encoded
  2. Check certificate and key files match using OpenSSL
  3. Ensure certificate includes full chain if needed
  4. Confirm hostname matches certificate common name
  5. Verify certificate is not expired

License Upload Problems​

Symptoms: License file rejected or not recognized

Solutions:

  1. Verify license file format (should be .yml)
  2. Check file is not corrupted during download
  3. Confirm license matches your organization
  4. Contact Account Manager if license issues persist

Performance Issues​

Slow Installation​

  • Verify sufficient resources (CPU, memory, disk I/O)
  • Check network bandwidth for package downloads
  • Monitor disk space during installation

Application Startup Issues​

  • Verify all containers are running: docker ps
  • Check resource utilization: top, free -h, df -h
  • Review application logs for errors

Getting Help​

Log Collection​

For support requests, collect these logs:

# System logs
sudo journalctl -u docker > docker.log

# Installation logs
sudo kubectl logs -n default deployment/coginiti > app.log

# Admin console logs  
curl -k https://localhost:8800/api/v1/troubleshoot > troubleshoot.log

Support Contacts​

  • Installation Support: Your Account Manager
  • Technical Support: support@coginiti.co
  • Emergency Support: Contact Account Manager for escalation
  • Documentation: Latest guides and troubleshooting

When contacting support, provide:

  • System specifications and OS version
  • Installation method and any custom configurations
  • Complete error messages and log files
  • Network topology and security configurations

Next Steps​

After successful installation:

  1. Configure Users - Set up user accounts and permissions through the admin interface
  2. Configure Database Connections - Connect to your data sources
  3. Configure Security - Implement additional security measures through admin settings
  4. Set up Backup Procedures - Establish backup processes for encryption keys and configurations

Summary​

You have successfully installed Coginiti Team! Key takeaways:

✅ Phase 1: Command-line installation sets up Coginiti Team infrastructure ✅ Phase 2: Web-based configuration completes application setup ✅ Critical Data: Encryption keys and admin passwords must be saved securely ✅ SSL Certificates: Production certificates ensure secure access ✅ Database Setup: PostgreSQL with pg_vector extension is required ✅ Verification: Test application access and basic functionality

Your Coginiti Team instance is now ready for use. Configure users, connections, and security settings to complete your deployment.

Understanding the System​

Next Steps​