Deploy

Edition: this page covers the self-managed Enterprise Edition standup (the full ALB + ECS Fargate runtime). For the free local runtime, follow the Developer Edition Installation Guide instead — it provisions only the data plane, no ALB/ECS.

StrataBI deploys into your own AWS account as code. The module provisions the app (ALB + ECS Fargate), the async Athena runner and status-writer Lambdas, DynamoDB tables, a Glue catalog database, Athena workgroups, and an S3 system bucket seeded with themes and a default dashboard.

The module is written for Terraform and is compatible with OpenTofu — the commands below are identical for either (terraform ↔ tofu).

Standup at a glance

A full StrataBI Enterprise standup is three steps, all in your own account:

1. Build the runtime image — fetch the account-entitled wheel and build a

container image, on a workstation or via the CodeBuild reference pipeline. See Container image. The result is an ECR image URL you pass as stratabi_image.

1. Deploy the platform — provision the app (ALB + ECS, Lambdas, tables, Glue,

Athena, S3) with the variables below. Run it directly with Terraform/OpenTofu (this page) or through StrataCTL, which fetches the signed platform bundle and runs it in an ephemeral runner in your account — see StrataCTL and Delivery & teardown.

1. Verify — smoke-test the ALB, ECS service, Lambdas, tables, and bucket.

Teardown is always available: the platform bundle is delivered local, so its Terraform lives in your account and destroy/uninstall work without contacting Shaleio.

Prerequisites

• An AWS account and credentials that can create the resources above.
• Terraform ≥ 1.6 or a current OpenTofu.
• An existing VPC with public subnets (for the ALB) and subnets for ECS tasks.
• A built StrataBI container image in ECR.
• Optional: an ACM certificate in the same region if you want HTTPS.

Quick start (recommended: the wizard)

The recommended path is to let StrataCTL collect configuration and generate the Terraform variables — you answer questions instead of editing .tfvars by hand:

stratactl init        # prompts for region, VPC/subnets, image, security flags, ...
                      # writes strata.yaml (source of truth) + infra/terraform.tfvars
cd infra
terraform init
terraform validate
terraform plan        # review carefully
terraform apply
terraform output alb_dns_name

strata.yaml is the source of truth; re-running stratactl init reuses your answers and only asks for what is missing. See StrataCTL for the full wizard.

Manual alternative

You can still manage terraform.tfvars by hand if you prefer:

cd infra
cp terraform.tfvars.example terraform.tfvars   # then edit
terraform init && terraform plan && terraform apply

Naming and multiple installs

Every named resource is prefixed by name_prefix (default stratabi). The default reproduces the original names exactly, so existing installs see no change. To run a second install in the same account, set a distinct prefix:

name_prefix = "acme"

HTTPS

HTTPS is off by default (plain HTTP on the ALB). To enable TLS, supply a certificate:

enable_https        = true
acm_certificate_arn = "arn:aws:acm:us-east-1:<acct>:certificate/<id>"

This adds a 443 listener and ingress; the HTTP listener stays in place.

Verify the install

A smoke test checks the ALB, ECS service, Lambdas, DynamoDB tables, and bucket:

./smoke_test.sh stratabi us-east-1     # <name_prefix> <region>

Key variables