Installer variables (local shell)
Set these in your shell before piping the installer to bash. They influence howinstall.sh behaves during the deploy.
Precedence for installer configuration
When a value can come from multiple sources, the installer resolves it in this order:- Explicit CLI flag (e.g.
--profile builder) — highest priority - Environment variable (e.g.
AWS_REGION) - Pack manifest default (
packs/<pack>/manifest.yaml) — lowest priority
Deploy-time parameters
The installer computes these values from your pack, profile, and flags, then passes them to CloudFormation or Terraform. You don’t set these directly — they are documented here as a reference for the CloudFormation parameters and Terraform variables that control your deployment.LiteLLMApiKey and ProviderApiKey are NoEcho: true in CloudFormation — they don’t appear in stack history or describe-stacks output. However, they do pass through UserData. For long-lived secrets, use the --kiro-from-secret / Secrets Manager pattern instead. See Managing secrets with AWS Secrets Manager.Instance variables — per-pack runtime
Once the agent pack is installed and running, pack-specific variables are sourced from shell profiles on the instance. These are what each agent actually reads at runtime.- openclaw
- claude-code
- codex-cli
- kiro-cli
- bedrockify-backed packs