Operations · AWS baseline

Deploy the AWS service with reviewed Terraform.

Deploy the AWS service with the versioned Terraform module used for releases. Configure gateway routes, policies, budgets, and identities in the app or API for now.

Create a free workspace Read current API behavior

How the connection works

How Terraform works with the gateway

Use the release module

The AWS module used by the release process includes named environments, version constraints, reviewed plans, and controlled apply roles.

Protect remote state

Terraform state can contain sensitive values. The baseline keeps it encrypted, remote, locked, and limited to approved roles.

Manage gateway settings separately

Routes, policies, budgets, and identities are available in the app and control API. They are not Terraform resources yet.

Current shared controls

What every supported connection includes

Encrypted BYOK credentials that remain hidden after setup Stable model aliases and compatible route targets Organization and key budgets, rate limits, and concurrency limits Observe, Shadow, and Enforce modes with metadata-only evidence

Review the plan, remote-state controls, and apply role before approving an environment.

Client boundary

AIGHQ_BASE_URL=https://api.aigatewayhq.com/v1
AIGHQ_API_KEY=from-your-workspace
AIGHQ_MODEL=company-approved-fast

Terraform deploys AWS infrastructure. It does not send model requests, select models, or change provider accounts.

Implemented boundary

Supported protocols

Use the AWS module to deploy a reviewed environment. Manage routes, policies, budgets, and identities through the app or control API. A public Terraform provider for those gateway settings is not available yet.

Version-pinned Terraform AWS provider Remote encrypted state with locking Plan-then-apply release boundary

Compatibility follows the provider's current published interface. Review the provider documentation before approving Terraform for production.