StrataCLI

StrataCLI is the local command-line tool for operators. It installs, updates, and removes StrataBI modules in your AWS account, installs the StrataBI platform itself, and version-controls your dashboards. You run it on your own machine with your own AWS credentials.

How it works

• You run it locally — a small Python CLI that uses your AWS credentials. It

is not a hosted service.

• Module and platform installs run in your account. StrataCLI launches an

ephemeral runner inside your AWS account that fetches the artifact, runs OpenTofu, writes state and logs into your own account, and exits. Your account owns the deployment state and logs end to end — nothing long-lived reaches in from outside.

• Dashboard sync talks to S3/DynamoDB directly (no runner needed).
• StrataCLI owns your deployment configuration. You answer questions; it writes

the config and generates the Terraform/OpenTofu variable files. You do not hand-edit .tfvars.

Installation wizard (strata init)

strata init is the recommended way to configure a deployment. It asks for the values an installation needs, saves them to a human-readable YAML config (strata.yaml, the source of truth), and generates the Terraform variable files from it.

stratacli init                 # configure a StrataBI deployment (interactive)
stratacli init module <id>     # configure an official module's variables
stratacli init --update        # re-prompt for every value, not just missing ones
stratacli init --non-interactive   # use saved config + defaults, no prompts (automation)

The wizard prompts only for values that are missing, validates inputs (region, VPC and subnet ids, CIDRs, image refs, ACM ARNs), and is safe to re-run — existing values are reused. It writes terraform.tfvars (into ./infra when present) and module variables into <module>.auto.tfvars. Generated files carry a "do not edit by hand" header: edit strata.yaml and re-run instead.

Example strata.yaml:

installation:
  name: production            # also the Terraform name_prefix
  aws_region: us-east-1
  organization: acme
  edition: enterprise
runtime:
  stratabi_image: 123456789012.dkr.ecr.us-east-1.amazonaws.com/stratabi:latest
network:
  vpc_id: vpc-0123abcd
  public_subnet_ids: [subnet-aaaa, subnet-bbbb]
  private_subnet_ids: [subnet-cccc, subnet-dddd]
  allowed_ip_cidrs: [203.0.113.0/24]
security:
  enable_guardduty: false
  enable_inspector: false
  enable_securityhub: false

Modules declare their own variables (an install.schema.json, or an install_schema block in module.json), so strata init module <id> prompts for them generically with no module-specific code in the CLI. The same strata.yaml is the configuration object future commands consume, so there is one source of truth across init, install, and update.

Installing modules

stratacli install <module> [--source customer_s3|stratahq] [--to <version>]
stratacli update <module> [--to <version>]
stratacli uninstall <module>
stratacli list
stratacli logs <job-id>

install launches the runner, streams its logs to your terminal, and records the install. --source customer_s3 installs from your own S3 bucket; the default source can be set in config. update applies a new version; uninstall runs the module's destroy. list shows what's installed; logs <job-id> tails or replays a run.

Installing the platform

stratacli init                      # configure first (writes strata.yaml + tfvars)
stratacli install-stratabi          # commercial StrataBI Enterprise
stratacli install-stratabi-dev      # developer / community edition

Run stratacli init first to collect configuration and generate the Terraform variables; then install. Both editions ship as bundles and install through the same runner path, so update, uninstall, list, and logs work on them too.

Dashboards

stratacli dashboards pull        # download git-registered dashboards locally
stratacli dashboards push        # deploy local dashboards back to S3
stratacli dashboards list
stratacli dashboards diff

This is the git side of the dashboards-as-code workflow — see Dashboards as code for the full picture, including the git button in the runtime and the overwrite-in-place model.

Configuration

StrataCLI resolves its settings from these layers, highest priority first:

1. a command-line flag,
2. an environment variable (STRATA_*),
3. a local config file (./.stratacli.toml, then ~/.stratacli/config.toml),
4. AWS SSM Parameter Store / Secrets Manager,
5. packaged defaults.

AWS credentials come from your normal AWS profile or keys (e.g. --profile, AWS_PROFILE, or environment credentials). Because the CLI acts as you, what you can install or deploy is governed by your own IAM permissions in the target account.