Install the provider¶

When you finish, Terraform has downloaded the Qumulo provider, checked its signature, and pinned the verified build in your lock file.

Before you start¶

Terraform 1.11 or later
HTTPS (port 443) egress to qumulo-terraform-registry.s3.us-east-1.amazonaws.com. Downloads are anonymous, with no AWS account or credentials.

1. Add the provider to a `.tf` file in your working directory¶

terraform {
  required_providers {
    qumulo = {
      source  = "qumulo-terraform-registry.s3.us-east-1.amazonaws.com/qumulo/qumulo"
      version = "~> 1.0"
    }
  }
}

The configuration now names the provider, and nothing has downloaded yet.

2. Initialize¶

terraform init

The output includes - Installed qumulo-terraform-registry.s3.us-east-1.amazonaws.com/qumulo/qumulo v1.4.22 (self-signed, key ID <key ID>) and ends with Terraform has been successfully initialized!

Self-signed is expected

Every provider hosted outside registry.terraform.io reports as self-signed, and there is nothing to do. Terraform has still checked the signature and the checksums in full.

3. Commit the lock file¶

Commit .terraform.lock.hcl alongside your configuration. Every teammate and CI run now installs the identical, verified build.

4. Upgrade later¶

terraform init -upgrade

Raise the version constraint first if the new release falls outside it. The - Installed line then shows the new version, and .terraform.lock.hcl records its hashes.

Fix install errors¶

Symptom	Fix
`Failed to query available provider packages`	Allow `qumulo-terraform-registry.s3.us-east-1.amazonaws.com` on port 443 in your proxy or firewall. `curl -s https://qumulo-terraform-registry.s3.us-east-1.amazonaws.com/.well-known/terraform.json` prints `{"providers.v1": "/v1/providers/"}` once it is reachable.

Next¶

Deploy your first cluster on AWS, Azure, GCP, or bare metal.