Provider aliases for multi-region in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a provider with an alias for the us-east-1 region.

Terraform

provider "aws" {
  region = "[1]"
  alias  = "useast1"
}

Drag options to blanks, or click blank then click option'

Aus-east-1

Bus-west-2

Ceu-central-1

Dap-southeast-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the default region instead of the specific region for the alias.

Misspelling the region name.

The alias is set for the us-east-1 region to enable multi-region usage.

2fill in blank

medium

Complete the resource block to use the aliased provider for us-east-1.

Terraform

resource "aws_s3_bucket" "example" {
  provider = aws.[1]
  bucket   = "my-bucket-us-east-1"
  acl      = "private"
}

Drag options to blanks, or click blank then click option'

Auswest2

Bdefault

Cuseast1

Deucentral1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' which refers to the default provider, not the alias.

Using a region name instead of the alias.

The resource uses the aliased provider useast1 to deploy in the us-east-1 region.

3fill in blank

hard

Fix the error in the provider block by completing the missing alias.

Terraform

provider "aws" {
  region = "eu-west-1"
  alias  = "[1]"
}

Drag options to blanks, or click blank then click option'

Aeuwest1

Bdefault

Capne1

Duseast1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' as an alias which is reserved for the default provider.

Using an alias unrelated to the region.

The alias should reflect the region name euwest1 to clearly identify the provider for eu-west-1.

4fill in blank

hard

Fill both blanks to define two providers with aliases for different regions.

Terraform

provider "aws" {
  region = "[1]"
  alias  = "uswest2"
}

provider "aws" {
  region = "[2]"
  alias  = "apne1"
}

Drag options to blanks, or click blank then click option'

Aus-west-2

Bap-northeast-1

Cus-east-1

Deu-west-1

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up region codes and aliases.

Using the same alias for both providers.

The first provider is for us-west-2 with alias uswest2, and the second for ap-northeast-1 with alias apne1.

5fill in blank

hard

Fill all three blanks to create resources using aliased providers for multi-region deployment.

Terraform

resource "aws_s3_bucket" "west_bucket" {
  provider = aws.[1]
  bucket   = "my-bucket-west"
  acl      = "private"
}

resource "aws_s3_bucket" "asia_bucket" {
  provider = aws.[2]
  bucket   = "my-bucket-asia"
  acl      = "private"
}

resource "aws_s3_bucket" "default_bucket" {
  provider = [3]
  bucket   = "my-bucket-default"
  acl      = "private"
}

Drag options to blanks, or click blank then click option'

Auswest2

Bapne1

Caws

Duseast1

Attempts:

3 left

💡 Hint

Common Mistakes

Using region codes instead of aliases in the provider attribute.

Assigning the same alias to multiple resources incorrectly.

The first resource uses the uswest2 alias, the second uses apne1, and the third uses aws for the default provider.

Practice

1. What is the main purpose of using provider aliases in Terraform when working with multiple regions?

easy

A. To configure multiple providers with different regions in the same Terraform project

B. To create multiple resources in the same region automatically

C. To avoid using providers in Terraform

D. To deploy resources only in the default region

Solution

1. Step 1: Understand provider aliases concept

   Provider aliases allow defining multiple configurations of the same provider, each with different settings like region.

2. Step 2: Recognize multi-region use case

   Using aliases lets you deploy resources to different regions by specifying which provider alias to use.

3. Final Answer:

   To configure multiple providers with different regions in the same Terraform project -> Option A

4. Quick Check:

   Provider aliases = multi-region config [OK]

Hint: Aliases let you set different regions per provider [OK]

Common Mistakes:

• Thinking aliases create resources automatically
• Confusing aliases with resource names
• Assuming aliases remove the need for providers

2. Which of the following is the correct syntax to define a provider alias for AWS in the us-west-2 region?

easy

A. provider "aws.west" { region = "us-west-2" }

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

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

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

Solution

1. Step 1: Recall correct provider block syntax

   Provider blocks use key-value pairs inside braces, with each pair separated by new lines or spaces, no semicolons.

2. Step 2: Identify correct order and syntax

   The alias attribute must be inside the provider block along with region, separated by new lines or spaces, no semicolons.

3. Final Answer:

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

4. Quick Check:

   Alias and region inside provider block without semicolons [OK]

Hint: Put alias and region inside provider block, no semicolons [OK]

Common Mistakes:

• Using semicolons inside provider block
• Placing alias outside the provider block
• Incorrect order with alias after block

3. Given the following Terraform snippet, what region will the aws_instance resource be created in?

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

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

resource "aws_instance" "example" {
  provider = aws.west
  ami      = "ami-123456"
  instance_type = "t2.micro"
}

medium

A. us-east-1

B. Region is not specified, so error occurs

C. us-west-2

D. Default region of AWS CLI

Solution

1. Step 1: Identify provider alias usage in resource

   The resource uses provider = aws.west, which refers to the aliased provider with region us-west-2.

2. Step 2: Confirm region of aliased provider

   The alias "west" is configured with region "us-west-2", so the resource will be created there.

3. Final Answer:

   us-west-2 -> Option C

4. Quick Check:

   Resource uses aliased provider region [OK]

Hint: Resource uses provider alias region, not default [OK]

Common Mistakes:

• Assuming default provider region is used
• Confusing alias name with region
• Thinking AWS CLI config affects Terraform provider region

4. You wrote this Terraform code but get an error: Invalid provider configuration. What is wrong?

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

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

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

medium

A. The alias must be declared as alias = "east" inside the provider block

B. You cannot have two providers with the same region

C. The resource should not specify a provider alias

D. The alias name must be different from the provider name

Solution

1. Step 1: Check alias syntax

   The alias is declared outside the provider block after the closing brace, which causes the invalid configuration error.

2. Step 2: Correct placement

   The alias attribute must be inside the provider block along with the region.

3. Final Answer:

   The alias must be declared as alias = "east" inside the provider block -> Option A

4. Quick Check:

   Alias must be inside provider block [OK]

Hint: Alias must be inside provider block exactly [OK]

Common Mistakes:

• Defining alias outside provider block
• Using same alias for multiple providers
• Not specifying provider in resource

5. You want to deploy an AWS EC2 instance in us-east-1 and an S3 bucket in us-west-2 using provider aliases. Which Terraform configuration correctly sets up the providers and assigns them to the resources?

hard

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

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

resource "aws_instance" "example" {
provider = aws.west
ami = "ami-abc123"
instance_type = "t2.micro"
}

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

B. provider "aws" {
alias = "east"
region = "us-east-1"
}

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

resource "aws_instance" "example" {
provider = aws.west
ami = "ami-abc123"
instance_type = "t2.micro"
}

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

C. provider "aws" {
region = "us-east-1"
alias = "east"
}

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

resource "aws_instance" "example" {
provider = aws.east
ami = "ami-abc123"
instance_type = "t2.micro"
}

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

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

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

resource "aws_instance" "example" {
ami = "ami-abc123"
instance_type = "t2.micro"
}

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

Solution

1. Step 1: Define providers with and without alias

   Default provider is for us-east-1 (no alias). Aliased provider "west" is for us-west-2.

2. Step 2: Assign providers to resources

   EC2 instance uses default provider (us-east-1). S3 bucket uses aliased provider aws.west (us-west-2).

3. Step 3: Verify resource provider assignments

   Resource aws_instance has no provider attribute, so uses default. Resource aws_s3_bucket specifies provider = aws.west.

4. Final Answer:

   The configuration using a default provider for us-east-1 and an aliased provider for us-west-2 -> Option D

5. Quick Check:

   Default provider for us-east-1, alias for us-west-2 [OK]

Hint: Default provider for main region, alias for others, assign in resource [OK]

Common Mistakes:

• Assigning alias to default provider
• Not specifying provider for multi-region resources
• Using alias inside default provider block