Covers two main patterns for using multiple providers in Terraform: combining distinct providers (e.g., AWS + Kubernetes) and running multiple configurations of the same provider via the alias meta-argument for multi-region or multi-account deployments. Explains how to wire providers into child modules using configuration_aliases and the providers map, and outlines key limitations such as no dynamic alias values, no count/for_each across providers, and aliased providers not being inherited by child modules automatically.
Table of contents
What does multiple providers mean in Terraform?Case 1: Using different providers togetherCase 2: Multiple configurations of the same providerUsing multiple providers in Terraform modulesLimitations and constraints when using multiple Terraform providersHow to manage Terraform resources with SpaceliftKey pointsFrequently asked questions793 Impressions