Installer variables (local shell)
Set these in your shell before piping the installer to bash. They influence howinstall.sh behaves during the deploy.
| Variable | Effect |
|---|---|
AWS_REGION / AWS_DEFAULT_REGION | Sets the AWS region for deployment. Overrides the default from your AWS CLI profile. |
AWS_PROFILE | Uses the named AWS CLI profile for all AWS API calls made during installation. |
DEBUG_IN_REPO=1 | Runs the installer from the current working directory instead of cloning from GitHub. Equivalent to passing --debug-in-repo. |
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.| Setting | CloudFormation parameter | How to set it |
|---|---|---|
| Agent pack | PackName | --pack <name> flag |
| Permission profile | ProfileName | --profile <name> flag |
| Bedrock region | BedrockRegion | AWS_REGION env var or advanced mode |
| Default AI model | DefaultModel | Set automatically per pack; override in advanced mode |
| Model access mode | ModelMode | bedrock (default), litellm, or api-key; advanced mode |
| LiteLLM proxy URL | LiteLLMBaseUrl | Advanced mode |
| LiteLLM API key | LiteLLMApiKey | Advanced mode (marked NoEcho in CloudFormation) |
| LiteLLM model alias | LiteLLMModel | Advanced mode |
| Provider API key | ProviderApiKey | Advanced mode (marked NoEcho in CloudFormation) |
| Kiro API secret | KiroFromSecret | --kiro-from-secret <secret-id> flag |
| OpenClaw gateway port | OpenClawGatewayPort | Advanced mode (default: 3001) |
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