Skip to main content
This page lists the environment variables users and administrators commonly touch. Server-side values live in the control plane .env file created by setup.sh.

CLI variables

Verify the value with:

Server variables

Server variables are release-specific. After running bash setup.sh, inspect .env.
Do not expose secrets, credentials, tokens, or private hostnames in public documentation or committed files.

IAM requirements

At minimum, the server’s AWS credentials need permission to launch and terminate the instance types you plan to use, read and write objects in S3_UPLOAD_BUCKET, and read service quota values for capacity tracking. The server repository includes a least-privilege IAM policy example at docs/iam-policy.json.

Common mistakes

  • Setting TD_SERVER_URL in one shell and running tandemn from another shell.
  • Using a server URL that is reachable from the admin machine but not from the user’s network.
  • Leaving S3_UPLOAD_BUCKET pointed at a bucket that does not exist.
  • Setting KOI_SERVICE_URL accidentally when you want standalone behavior.
  • Committing .env by accident.