2.2. Working with Multiple Providers
💡 First Principle: Because a provider is just a configured client, you can instantiate the same provider more than once with different settings — which is how a single configuration deploys to two regions, two accounts, or two clouds at once.
Why care: Real infrastructure rarely lives in one place. Multi-region deployments, multi-account setups, and multi-cloud architectures all rely on having more than one configured provider instance, and the exam expects you to know the mechanism: aliases.
The mental model: A provider configuration is like a labeled phone line to a platform. By default you have one line. An alias adds a second labeled line to the same platform with different settings — so a resource can choose which line to call out on.
⚠️ Common Misconception: Learners sometimes think you need a separate Terraform configuration or workspace per region. You don't — multiple provider configurations in a single configuration handle this cleanly, and resources select the right one with the provider meta-argument.
