Multiple provider configurations in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS provider region.

Terraform

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

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

Aaws-region

Bus-west-2

Cmy-region

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid or placeholder string for the region.

Leaving the region blank.

The AWS provider requires a valid AWS region like us-west-2 to know where to deploy resources.

2fill in blank

medium

Complete the code to define a second AWS provider with an alias.

Terraform

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

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

Awest

Bdefault

Ceast

Dprimary

Attempts:

3 left

💡 Hint

Common Mistakes

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

Using an alias that does not describe the provider region.

The alias east is used to distinguish this provider configuration from the default one.

3fill in blank

hard

Fix the error in the resource block to use the aliased provider.

Terraform

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

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

Adefault

Bprimary

Cwest

Deast

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' or other incorrect aliases that do not exist.

Omitting the provider attribute when multiple providers exist.

To use the aliased provider named east, specify provider = aws.east in the resource block.

4fill in blank

hard

Fill both blanks to configure two AWS providers with different regions and aliases.

Terraform

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

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

Aus-west-1

Bus-east-2

Cwest

Deast

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing region and alias values incorrectly.

Using invalid region codes.

The first provider uses region us-west-1 with alias west.

5fill in blank

hard

Fill all three blanks to create a resource using the aliased provider and specify the bucket name.

Terraform

resource "aws_s3_bucket" "example" {
  bucket   = "[1]"
  acl      = "private"
  provider = aws.[2]
  tags = {
    Environment = "[3]"
  }
}

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

Amy-app-bucket

Beast

Cproduction

Dwest

Attempts:

3 left

💡 Hint

Common Mistakes

Using a provider alias that is not defined.

Using an invalid bucket name.

Omitting the environment tag.

The bucket name is my-app-bucket, the provider alias is east, and the environment tag is production.

Practice

1. What is the main purpose of using multiple provider configurations in Terraform?

easy

A. To reduce the size of Terraform state files

B. To speed up Terraform plan execution

C. To manage resources in different cloud accounts or regions

D. To automatically backup Terraform configurations

Solution

1. Step 1: Understand provider role

   Providers in Terraform define where resources are created, such as cloud accounts or regions.

2. Step 2: Purpose of multiple providers

   Using multiple providers allows managing resources across different accounts or regions simultaneously.

3. Final Answer:

   To manage resources in different cloud accounts or regions -> Option C

4. Quick Check:

   Multiple providers = manage multiple accounts/regions [OK]

Hint: Multiple providers = multiple accounts or regions [OK]

Common Mistakes:

• Thinking multiple providers speed up execution
• Confusing providers with state file management
• Assuming providers handle backups

2. Which Terraform syntax correctly defines a second AWS provider with an alias named east?

easy

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

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

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

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

Solution

1. Step 1: Check provider block syntax

   The alias attribute must be inside the provider block, before or after region.

2. Step 2: Validate provider "aws" { alias = "east" region = "us-east-1" }

   provider "aws" { alias = "east" region = "us-east-1" } correctly places alias = "east" inside the provider block with region.

3. Final Answer:

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

4. Quick Check:

   Alias inside provider block = correct syntax [OK]

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

Common Mistakes:

• Placing alias outside provider block
• Using alias without quotes
• Misordering block elements causing syntax errors

3. Given this Terraform snippet:

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

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

resource "aws_s3_bucket" "bucket1" {
  bucket = "west-bucket"
}

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

Which region will bucket2 be created in?

medium

A. us-west-2

B. us-east-2

C. us-west-1

D. us-east-1

Solution

1. Step 1: Identify provider for bucket2

   bucket2 uses provider = aws.east, which refers to the aliased provider with region us-east-1.

2. Step 2: Confirm region of aliased provider

   The alias "east" is set with region = "us-east-1".

3. Final Answer:

   us-east-1 -> Option D

4. Quick Check:

   Aliased provider region = us-east-1 [OK]

Hint: Resource uses aliased provider region [OK]

Common Mistakes:

• Assuming default provider region applies
• Ignoring provider alias in resource
• Confusing region names

4. What is wrong with this Terraform configuration snippet?

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

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

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

resource "aws_instance" "example2" {
  provider = aws.west
  ami      = "ami-654321"
  instance_type = "t2.micro"
}

medium

A. The provider alias 'east' is missing region

B. The alias 'west' is not defined for any provider

C. The resource 'example' is missing provider assignment

D. The provider block syntax is invalid

Solution

1. Step 1: Check provider aliases defined

   Only alias 'east' is defined; no alias 'west' exists.

2. Step 2: Identify usage of undefined alias

   Resource 'example2' uses provider = aws.west, which is undefined and causes an error.

3. Final Answer:

   The alias 'west' is not defined for any provider -> Option B

4. Quick Check:

   Undefined alias causes error [OK]

Hint: Check all provider aliases are defined before use [OK]

Common Mistakes:

• Assuming default provider applies to aliased names
• Missing alias attribute in provider block
• Incorrect provider block syntax

5. You want to deploy resources to two AWS accounts: Account A in us-west-2 and Account B in us-east-1. You have two provider blocks with aliases west and east. How do you ensure that an S3 bucket resource is created in Account B using Terraform?

hard

A. Set provider = aws.east in the S3 bucket resource block

B. Set region = "us-east-1" inside the S3 bucket resource block

C. Use alias = "east" inside the S3 bucket resource block

D. Create a new provider block inside the S3 bucket resource

Solution

1. Step 1: Understand provider alias usage

   To deploy to Account B, the resource must use the provider with alias 'east'.

2. Step 2: Assign provider alias to resource

   Setting provider = aws.east in the resource block directs Terraform to use that provider configuration.

3. Final Answer:

   Set provider = aws.east in the S3 bucket resource block -> Option A

4. Quick Check:

   Resource provider = aliased provider [OK]

Hint: Assign provider alias in resource block to target account [OK]

Common Mistakes:

• Trying to set region inside resource instead of provider
• Using alias attribute inside resource block incorrectly
• Defining provider block inside resource block