With Terraform, you can deploy Deadline Cloud infrastructure as code. These configurations use the AWS Cloud Control (AWSCC) provider, which supports AWS Deadline Cloud resource types.
This table covers every immediate sample directory below terraform/farm_templates/.
| Sample | What it demonstrates | Start here when |
|---|---|---|
| Starter farm | A farm, queue, service-managed fleets, and package-build support using AWSCC resources | Your team manages infrastructure with Terraform |
| KNFSD cross-region cache | A service-managed fleet reading a distant NFS filer through a KNFSD read cache over a VPC resource endpoint, deployed cross-region to stand in for an on-premises origin | You cache reads from an on-premises or otherwise-distant filer for a render/simulation fleet |
The starter farm can run rendering, reconstruction, and data-transformation jobs from the job bundle index. It is the Terraform equivalent of the CloudFormation starter farm and includes support for building custom Conda packages.
Both starter configurations create equivalent infrastructure. Choose based on your team's existing tooling and state-management practices.
| Aspect | CloudFormation | Terraform |
|---|---|---|
| Provider | AWS native | HashiCorp AWSCC |
| Deadline resources | AWS::Deadline::* |
awscc_deadline_* |
| State | Managed by AWS | Local or remote backend |