Provider deployment designs
AWS and Azure share request semantics and governance outcomes, but they do not share Terraform modules, state backends, identities, or cloud operations. The provider adapters are credential-free simulations; separate real-capable Terraform and bootstrap roots are implemented and mock-validated. The sandbox and enterprise pages are implementation references, not live deployment reports.
Start with the administrator deployment guide for the complete capability, responsibility, prerequisite, and acceptance boundary.
- AWS simulation adapter
- AWS sandbox and enterprise design
- Azure simulation adapter
- Azure sandbox and enterprise design
- Provider comparison
Operating modes
| Mode | AWS boundary | Azure boundary | Production |
|---|---|---|---|
| Simulation | mocked provider behavior | mocked provider behavior | represented locally only |
| Sandbox | one account, one region | one subscription, one region | forbidden |
| Enterprise | separated accounts and shared services | tenant/management groups and separated subscriptions | explicitly governed |
Every real mode requires separate operator setup, protected configuration, short-lived OIDC, remote state, budgets, cleanup ownership, and approval. None of those real operations is being run for this release.