Data Quality Detect. Quantify. Resolve.
← Back to download

A101 Installer Runbook

Audience: your cloud-ops team on install day. Prerequisite: you received an onboarding email from AltitudeIQ containing a download page URL and a bootstrap token. If either is missing, stop and contact support before proceeding.

Scope of work

The next four sections describe what the installer will create in your subscription, what it needs from you to do so, and how its outbound traffic is shaped. These are the items a procurement, security, or cloud-governance reviewer typically wants signed off before install day. The full pre-install checklist lives at pre-install checklist — it covers RBAC, policy, quota, and conditional-access checks in detail.

What we'll provision

All resources land in a single resource group named rg-<app-name> in the region you choose. The installer creates:

What permissions we need

Networking shape

1. Get the installer binary

Open the download page URL from your onboarding email. Type the email address that received the welcome message and click "Show download". You'll see:

Run the installer on the Linux host where az login is configured. If that's the host with your browser, click the download link directly. If you're SSH'd into a server, copy the curl command and paste it into your terminal:

curl -L -o altitudeiq-installer "<paste-the-URL-from-the-page>"
chmod +x altitudeiq-installer

The download URL is short-lived (1 hour). If it expires before you've downloaded the binary, refresh the download page and re-enter your email — a new URL will be minted.

2. Authenticate to Azure

Before running these commands:

az login --tenant <your-tenant-id>
az account set --subscription <your-subscription-id>

The installer reads the current az context. Confirm the right subscription is selected:

az account show --query '{name: name, id: id}'

3. Run the installer

Pick an application name. Rules: 3–12 lowercase characters, digits, and hyphens, starting with a letter. Example: acme-aiq or contoso. The installer will prompt for it (and for the admin email + region) if you don't pass them as flags.

Recommended — interactive walk-through:

export ALTITUDEIQ_BOOTSTRAP_TOKEN='eyJhbGciOiJFZERTQSIs...'
./altitudeiq-installer

The installer prompts for app-name, admin-email, and region, runs pre-flight checks, prints what it's about to deploy, and asks for confirmation before any Azure resource is created.

Scripted / non-interactive — pass values as flags:

export ALTITUDEIQ_BOOTSTRAP_TOKEN='eyJhbGciOiJFZERTQSIs...'
./altitudeiq-installer \
  --app-name acme-aiq \
  --admin-email admin@acme.com \
  --location eastus2

The bootstrap token is always supplied via the ALTITUDEIQ_BOOTSTRAP_TOKEN environment variable (or the interactive prompt) — never as a CLI flag. Flag values are visible in ps/proc listings and shell history, which makes them a poor place for secrets.

The control plane URL and performance tier are resolved automatically: the URL is embedded in the release binary, and the tier is read from the bootstrap token claim. You don't need to pass either.

Expected output for a healthy install:

  1. Parameter validation — [OK] All parameters valid and ARM template embedded.
  2. Authentication — [OK] Authenticated to Azure (subscription: …).
  3. Pre-flight checks — 10 checks run in ~40 seconds; all should be [PASS] or [WARN]. See §6 if any are [FAIL].
  4. Confirmation — Proceed with deployment? [y/N] — type y and press Enter.
  5. Deployment — => Deploying AltitudeIQ bootstrap infrastructure (this may take 5-10 minutes) followed by per-resource progress.
  6. Reconciler bootstrap — => Watching reconciler bootstrap (the next 10–15 min is hands-off) while backend, frontend, matching, and PostgreSQL get provisioned.
  7. Success — Frontend URL: https://… printed at the end. That URL is your instance.

Total elapsed time: ~20–30 minutes for a green install.

4. Verify

Open the printed Frontend URL in a browser. You should see the AltitudeIQ login page. Sign in with the admin email you supplied.

If the URL doesn't respond yet, wait up to 5 more minutes — the CDN may still be warming. After that, see §6.

5. Hand-off to end users

Once the frontend is live:

  1. Your admin completes their initial profile + SSO configuration via the in-app onboarding flow.
  2. Invite other users via the "Team" page.
  3. Begin configuring data sources.

6. Troubleshooting

"Pre-flight checks failed"

The installer prints each failing check with a remediation hint. The most common ones:

"Invalid bootstrap token" during register

Three common causes:

ARM deploy fails mid-way

Status "Deploying" for >20 min with no progress typically means a policy or quota block.

az deployment group list --resource-group rg-<app-name> \
  --query "[].{Name:name, State:properties.provisioningState, Error:properties.error}"

Look at the Error field. If it's RequestDisallowedByPolicy, see the installer output — the error translator names the remediation. If quota, file a ticket with Azure and re-run with --cleanup first to remove the partial install.

Frontend URL doesn't respond

Reconciler register returns 403

Usually means your AltitudeIQ tenant has been suspended (contract issue). Contact AltitudeIQ support.

7. Getting help

8. What NOT to do