Provider aliases for multi-region in Terraform - Step-by-Step Execution

Process Flow - Provider aliases for multi-region

Define default provider

↓

Define provider alias for region A

↓

Define provider alias for region B

↓

Use alias in resource for region A

↓

Use alias in resource for region B

↓

Terraform applies resources in both regions

This flow shows how Terraform defines multiple providers with aliases for different regions and uses them to deploy resources in each region.

Execution Sample

Terraform

provider "aws" {
  region = "us-east-1"
}

provider "aws" {
  alias  = "west"
  region = "us-west-2"
}

resource "aws_s3_bucket" "east_bucket" {
  bucket = "my-east-bucket"
}

resource "aws_s3_bucket" "west_bucket" {
  provider = aws.west
  bucket   = "my-west-bucket"
}

This Terraform code sets up AWS providers for two regions and creates S3 buckets in each region using provider aliases.

Process Table

Step	Action	Provider Used	Resource Created	Region
1	Initialize default AWS provider	aws (default)	None	us-east-1
2	Initialize AWS provider with alias 'west'	aws.west	None	us-west-2
3	Create S3 bucket 'my-east-bucket'	aws (default)	aws_s3_bucket.east_bucket	us-east-1
4	Create S3 bucket 'my-west-bucket'	aws.west	aws_s3_bucket.west_bucket	us-west-2
5	Apply complete, resources created in both regions	aws (default) & aws.west	2 buckets	us-east-1 & us-west-2

💡 All resources created successfully using correct provider aliases for each region.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
aws provider	undefined	configured (us-east-1)	configured (us-east-1)	configured (us-east-1)	configured (us-east-1)	configured (us-east-1)
aws.west provider	undefined	undefined	configured (us-west-2)	configured (us-west-2)	configured (us-west-2)	configured (us-west-2)
aws_s3_bucket.east_bucket	undefined	undefined	undefined	created (my-east-bucket)	created (my-east-bucket)	created (my-east-bucket)
aws_s3_bucket.west_bucket	undefined	undefined	undefined	undefined	created (my-west-bucket)	created (my-west-bucket)

Key Moments - 2 Insights

Why do we need to use 'provider = aws.west' in the west_bucket resource?

Because the default provider is set to us-east-1, specifying 'provider = aws.west' tells Terraform to use the provider configured for us-west-2, as shown in execution_table step 4.

What happens if we omit the alias and try to create resources in multiple regions?

Terraform will use the default provider for all resources, so all resources will be created in the default region only, not in multiple regions. This is why aliases are necessary (see execution_table steps 3 and 4).

Visual Quiz - 3 Questions

Look at the execution_table, which provider is used to create the 'my-west-bucket'?

A aws.west

B aws (default)

C aws.east

D No provider specified

💡 Hint

Check step 4 in the execution_table where the provider used is listed.

At which step does Terraform configure the provider for the us-west-2 region?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the provider initialization steps in the execution_table.

If we remove the alias from the second provider block, what will happen to the 'west_bucket' resource creation?

A It will create the bucket in us-west-2 anyway

B Terraform will throw an error due to duplicate provider blocks

C The bucket will be created in the default region us-east-1

D The bucket will not be created at all

💡 Hint

Refer to the key_moments about default provider usage and alias necessity.

Concept Snapshot

Terraform Provider Aliases for Multi-Region

- Define default provider for one region.
- Define additional providers with 'alias' for other regions.
- Use 'provider = aws.alias' in resources to specify region.
- Allows managing resources across multiple regions in one config.
- Avoids conflicts by clearly separating provider configs.

Full Transcript

This visual execution trace shows how Terraform uses provider aliases to manage resources in multiple AWS regions. First, the default AWS provider is configured for the us-east-1 region. Then, a second AWS provider is configured with the alias 'west' for the us-west-2 region. Resources are created using these providers: the east_bucket uses the default provider, and the west_bucket uses the aliased provider. The execution table details each step, showing provider initialization and resource creation with their respective regions. Variable tracking shows the state of providers and resources after each step. Key moments clarify why aliases are necessary and how Terraform decides which provider to use. The quiz tests understanding of provider usage and alias effects. The snapshot summarizes the key points for quick reference.