Summary
Infrastructure outside of dash-network-deploy has zero Terraform coverage. Need a new dash-infra Terraform project for shared/permanent services.
Background
- dash-network-deploy manages testnet/mainnet masternodes well (409 resources in testnet state) — don't touch it
- dash-terraform is 3+ years stale, massively drifted, state doesn't match reality — not salvageable
- Consolidating into dash-network-deploy would turn a focused codebase into a junk drawer (different lifecycle: ephemeral networks vs permanent services)
What dash-infra should manage
- DNS seed instances (migrating from dashevo)
- CloudFront distributions + S3 static sites
- Insight (if kept)
- Status dashboard
- GitHub Actions OIDC / runner infrastructure
- ACM certificates
- Route53 zones shared across services
Architecture
- Modern AWS provider (~> 5.x)
- Launch templates (not deprecated launch configurations)
- Reusable modules:
dns-seeds, static-sites, insight, github-oidc
- Single environment (no workspaces — one production)
- Fresh state +
terraform import of existing resources
- S3 backend in dashdev account
Currently Unmanaged Resources
| Resource |
Count |
| Misc EC2 instances (dashboard, various test/POC, bots) |
~10 |
| Lambda functions (2 regions, 4 on EOL runtimes) |
12 |
| CloudFront distributions |
1+ |
| S3 buckets (non-TF-state) |
~10 |
| Route53 zones |
5 |
Related
Summary
Infrastructure outside of dash-network-deploy has zero Terraform coverage. Need a new
dash-infraTerraform project for shared/permanent services.Background
What dash-infra should manage
Architecture
dns-seeds,static-sites,insight,github-oidcterraform importof existing resourcesCurrently Unmanaged Resources
Related