Deploy a basic AWS cluster¶
When you finish, a three-node Qumulo cluster runs in one availability zone of your VPC, and you can sign in to its web UI.
Before you start¶
- A VPC and subnet that meet the AWS network prerequisites
- AWS credentials with the AWS IAM permissions the provider needs
- Terraform 1.11 or later
- For a subnet shared from another AWS account, the extra setup in AWS Cross-Account VPC
1. Copy the configuration¶
Save this as main.tf in an empty directory.
terraform {
required_version = ">= 1.11"
required_providers {
qumulo = {
source = "qumulo-terraform-registry.s3.us-east-1.amazonaws.com/qumulo/qumulo"
version = "~> 1.0"
}
}
}
provider "qumulo" {
aws {}
}
resource "qumulo_filesystem_aws" "cluster" {
cluster_name = "qumulo"
deployment_name = "qumulo"
region = "us-east-1" # <-- Replace with your region
subnet_ids = ["subnet-0123456789abcdef0"] # <-- Replace with your subnet ID
node_count = 3
instance_type = "m6idn.2xlarge"
cluster_product_type = "HOT"
admin_password = "YourSecurePassword123!" # <-- Replace with your admin password
allow_cidrs = ["10.0.0.0/8"] # <-- Replace with your client networks
deletion_protection = true
}
output "endpoint_ips" {
value = qumulo_filesystem_aws.cluster.endpoint_ips
}
output "web_ui" {
value = "https://${qumulo_filesystem_aws.cluster.endpoint_ips[0]}"
}
Replace the four values marked <-- Replace, and leave the rest as written.
Note
The configuration turns on deletion_protection, so terraform destroy refuses to run. To remove the cluster later, set deletion_protection = false and run terraform apply first.
2. Apply¶
The plan ends with Plan: 1 to add, 0 to change, 0 to destroy. The apply typically runs 60 to 80 minutes and ends with Apply complete! Resources: 1 added, 0 changed, 0 destroyed., followed by the endpoint_ips and web_ui outputs.
3. Check the cluster¶
Open the web_ui address in a browser on a network inside allow_cidrs, and accept the cluster's self-signed certificate. Sign in as admin with the password you set, and the web UI shows the cluster named qumulo.
Next¶
Harden the setup with Deploy a production AWS cluster, or look up any attribute in the qumulo_filesystem_aws reference. If a step fails, see Troubleshoot an AWS deployment.