Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.envzero.com/llms.txt

Use this file to discover all available pages before exploring further.

Deployment targets

env zero includes dedicated credential management for the platforms below, with secure storage and automatic credential injection at deploy time.
PlatformCredential typeSetup
Amazon Web Services (AWS)Cross-account IAM role (recommended) or Access KeysConnect AWS
Google Cloud (GCP)Service Account key (JSON)Connect GCP
Microsoft AzureService Principal (client credentials)Connect Azure
Oracle Cloud Infrastructure (OCI)API Key (RSA key pair + OCID)Connect OCI
KuberneteskubeconfigConnect Kubernetes
Any other provider with a Terraform, OpenTofu, or Pulumi provider is also supported. Pass credentials as environment variables at the organization, project, or environment scope and they will be injected at deployment time. See Other Cloud Providers for details.

Infrastructure-as-code frameworks

FrameworkNotes
TerraformSupported up to version 1.5.x. Versions 1.6 and later use the BSL license and are not supported — use OpenTofu instead.
OpenTofuFully supported. Drop-in replacement for Terraform 1.6 and later.
TerragruntFully supported.
PulumiFully supported.
CloudFormationFully supported.
HelmFully supported.
Kubernetes manifestsFully supported.
Terraform version limit: env zero supports Terraform up to version 1.5.x. Terraform 1.6.0 and later are licensed under the Business Source License (BSL) and are not supported. If your IaC requires Terraform 1.6+ features, use OpenTofu, which env zero fully supports as a drop-in alternative.
For information on pinning or managing specific tool versions, see Managing IaC Binaries Versions.

Custom tools

The Custom Flows capability lets you run any other tool as part of your deployment process, including configuration management tools like Ansible, Chef, and Puppet, or plain bash scripts.

Next steps