Creating Route 53 Records (Alias) to Route Traffic to an ALB Using Terraform

Find the details for logging in to the Terraform Controller node provided by the hands-on lab interface and log in to the node using SSH.

Note: This instance already has an EC2 instance profile (role) attached to it and has all necessary AWS API permissions required for this lab. It also has the AWS CLI set up and configured with the AWS account attached to this lab, for which the console login credentials are also provided in the lab interface page once the lab spins up.

After logging in, verify the version of Terraform installed (should be 12.29). Execute the following command to check.

Use the git command to clone the GitHub repo which has the Terraform code for deploying the solution of this lab. GitHub repo URL.

Change to the directory for lab Terraform code.

Examine the contents of the directory you're in.

You will need the values for a few pre-configured resources to complete this lab, such as Security Group IDs. These values can be found in the resource_ids.txt file in the cloud_user home directory.

• Absolute path to the resource_ids.txt file:

/home/cloud_user/resource_ids.txt

• Complete path to file:

/home/cloud_user/resource_ids.txt

Plug the appropriate value inside the import_resources.tf file inside the cloned Git repo folder.

A publicly-hosted domain is provided for you as part of this lab and your Terraform controller node has the permissions to make API calls to Route 53 to fetch it.

Fetch the domain and plug it into a variable.

Copy the DNS value, ensure that you copy the trailing . at the end as well, and replace it against the default value of the dns-name variable in the variables.tf file.

Initialize the Terraform directory you changed into to download the required provider

terraform init

Ensure Terraform code is formatted properly:

terraform fmt

Ensure code has proper syntax and no errors:

terraform validate

See the execution plan and note the number of resources that will be created:

terraform plan

Deploy resources:

terraform apply

Enter yes when prompted.

After terraform apply has run successfully, you can either use the AWS CLI on the Controller node to list and describe created resources or you can log in to the AWS Console to verify and investigate created resources.

Finally, on the Terraform Controller node CLI, delete all resources which were created and ensure that it runs through successfully.

terraform destroy