.tf files, run terraform plan to preview changes, and terraform apply to create them. Use it for repeatable, version-controlled provisioning of VPCs, instances, clusters, security groups, and filesystems.
Prerequisite: You need a service token to authenticate the Terraform provider.
Quick Start
The provider is distributed via the Terraform Registry asnscaledev/nscale. Declare it in your required_providers block:
Pin your provider version in production to avoid unexpected changes when new versions are released. Use
version = "~> 0.0.8" (or your current version) in the required_providers block.Authentication
The provider authenticates with Nscale using a service token, which you can generate and rotate in the Nscale Console.Environment Variables
The recommended way to configure the provider is via environment variables. This avoids hard-coding credentials in your.tf files:
Supported Resources
The following table maps Terraform resource types to their corresponding console pages:| Terraform Resource | Description | Console Page |
|---|---|---|
nscale_network | VPC networks | VPC Networks |
nscale_security_group | Firewall rules | Security Groups |
nscale_file_storage | Shared NFS filesystem | Filesystem |
nscale_compute_instance | Virtual machines | Instances |
nscale_compute_cluster | GPU clusters | Clusters |
Documentation
Full documentation for the provider is available on the Terraform Registry, and you can find examples in the GitHub repository.Related Resources
Service Tokens
Generate the token used to authenticate the Terraform provider
API Reference
The underlying API that the Terraform provider calls
Terraform Registry
Full provider documentation and resource reference
GitHub Examples
Example Terraform configurations