Documentation Index
Fetch the complete documentation index at: https://docs.equinix.dev/llms.txt
Use this file to discover all available pages before exploring further.
This reference mirrors what a working Equinix Terraform engineer needs in front of them: provider setup, module list, resource index, state strategy, import patterns, MCP integration, and recipes. Every recipe maps to a real Equinix repository or docs page — there is no synthetic Terraform here.
What’s covered
equinix.dev wraps four canonical Terraform sources:terraform-provider-equinix
equinix/equinix ~> 4.15 — the official Terraform provider. Resources for Fabric (Cloud Router, Connection, Service Profile, Route Filter, Streams), Network Edge (Device, Link, BGP), and Metal.terraform-equinix-fabric
v0.28.1 — the canonical Fabric module set. Higher-level wrappers for cloud-router connections, port connections, streams subscriptions.cloud-side providers
aws ~> 5.x, azurerm ~> 4.x, google ~> 6.x, oci ~> 6.x, ibm ~> 1.x, alicloud ~> 1.x. Each provider package on equinix.dev stages the matching cloud provider when needed.Equinix MCP servers
mcp.equinix.com/fabric and mcp.equinix.com/peeringInsights — the read-first MCP servers. Tooling to discover, validate, and propose Terraform changes from an agent.What’s not covered
- Apply. equinix.dev plans every change locally and never runs
terraform applyin any automated path. The plan stops at a readiness gate; a human runsapplyoutside the equinix.dev shell. - Drift detection. Use the standard Terraform tooling (
terraform plan, Atlantis, Spacelift, Terraform Cloud). - Cost-aware refactors. The
pricing.mdcontract gives every package a deterministic cost shape; combining pricing across packages is a follow-up.
How to read this section
Start here
Skim Getting Started for the
five-minute path from
brew install to a passing terraform plan.Configure the provider
Provider setup covers the official
equinix/equinix provider — auth, env vars, common pitfalls.Pick the right primitive
Resources is the index of every
equinix_* resource our packages write into Terraform, with a
one-line summary and a link to the per-package detail page.Use the modules where they fit
Modules shows when to wrap a resource in
terraform-equinix-fabric’s opinionated module versus calling
the resource directly.Quick reference
| Topic | Page |
|---|---|
Install + first terraform plan | Getting Started |
equinix/equinix provider config | Provider setup |
| Module list with versions and inputs | Modules |
Index of every equinix_* resource we use | Resources |
| Recommended state backends | State management |
terraform import patterns per resource | Importing existing services |
| Agents writing Terraform via Equinix MCP | MCP server |
| Three full recipes (the canonical Use Cases) | Recipes |
| Common gotchas | FAQs |