Tabsdata

Set Up Security Groups Ensure you have a security group set with:

1. Inbound Rules including Port 22
2. Inbound rules that include the ports you will be running your TabsData server on.

Connect to the VM Launch an EC2 instance from the AMI. SSH into it as the default user: ssh -i /path/to/your-key.pem ec2-user@<EC2_PUBLIC_DNS>

Switch to the tabsdata user When you log in as ec2-user you will be prompted to switch to the preconfigured tabsdata user. Selecting Yes loads the environment that already includes Tabsdata configuration, helper scripts, a ready to use Python virtual environment (tabsdata-env), and the tabsdata CLI on your PATH. To switch manually later: sudo su - tabsdata All steps below assume the tabsdata user.

Option A: Quickstart (recommended) Run the interactive setup tool: tabsdata init This guides you through creating or starting an instance, selecting external and internal API sockets, and generating a self signed HTTPS certificate. After setup, access the Tabsdata UI in your browser using the configured socket. If you are using HTTPS, run this once per new server socket: td auth add-cert --server https://<PUBLIC_IP>:<PORT> --pem cert.pem

Option B: Manual setup

Activate a Python virtual environment You may use the provided tabsdata-env or create your own.

Create or configure a Tabsdata instance Example: tdserver create --instance tabsdata This creates ~/.tabsdata/instances/<INSTANCE_NAME>/ which contains workspace and config files.

Configure ports Edit: ~/.tabsdata/instances/<INSTANCE_NAME>/workspace/config/proc/regular/apiserver/config/config.yaml

Set your external and internal sockets: addresses: 0.0.0.0:<external_port> internal_addresses: 127.0.0.1:<internal_port>

The external ip address must be either 0.0.0.0 or the EC2 private IP address. Each Tabsdata instance must use unique internal and external ports.

Configure HTTPS Follow Setting up Tabsdata over HTTPS https://docs.tabsdata.com/latest/guide/security/main.html 

to create a self signed certificate. To use a CA issued certificate, upload the CA certificate and key into config/ssl/ and point the config.yaml addresses to the certificate hostname.

Start the server tdserver start

NOTE There is a bug where tdserver stop fails to release the ports used by the apiserver. You must manually kill the process. ps aux | grep apiserver Then kill the process.

You can also run tabsdata init which sources a function called kill_legacy_process that automates this action.

Next steps If using HTTPS, add the certificate for CLI access: td auth add-cert --server https://<socket> --pem cert.pem This must be done for every new socket your server is run on.

Log in through the CLI: td login --server https://<socket> --user admin --password tabsdata --role sys_admin

After login you can create publishers, transformers, subscribers, and triggers. These can be configured through the Tabsdata UI or through the CLI. Once configured, workflows can be registered, executed, and monitored directly on the VM.