Skip to content

Latest commit

 

History

History
51 lines (28 loc) · 4.54 KB

README.md

File metadata and controls

51 lines (28 loc) · 4.54 KB

Implementing-Terraform-on-AWS

UPDATE 08-05-2022: The exercise files have been updated for compatibility with version 4 of the AWS provider and version 1.2.3 of Terraform. What you see in the videos may diverge from the code, but the core concepts remain the same. I've also updated some of the commands.txt files to be more clear in terms of what you should do.

I also realized that the commands for 8-app-deploy and 9-cf-template were not explicitly using the app profile for the state backend, so I fixed that in the backend block. You could remove the profile argument from the backend block and specify it as part of the terraform init command. I'm not the boss of you!

Welcome to Implementing Terraform on AWS. These exercise files are meant to accompany my course on Pluralsight. The course was developed using version 0.12.24 of Terraform. As far as I know there are no coming changes that will significantly impact the validity of these exercise files. But I also don't control all the plug-ins, providers, and modules used by the configurations.

Using the files

Each folder follows in succession as the course progresses. All of the folders include a commands.txt file that has example commands for that portion of the exercise. All folders also include an example terraform.tfvars file creatively named terraform.tfvars.example. Simply update the values in the file and rename it to terraform.tfvars.

Many of the modules in the course build on the infrastructure created by previous modules. Bearing that in mind, jumping around in the course will be difficult. When you complete a module, you might be tempted to run terraform destroy to delete the resources. You can do that, but remember that you will need to deploy the resources again a future module.

Course Prerequisites

There are a few prerequisites for working with the course files.

Visual Studio Code

You are going to want to use Visual Studio Code or a similar code editor. Personally I like VS Code because it's free and cross-platform, and it has source control built-in. But hey, that's just me. You do you.

AWS Accounts

This is a course all about using Terraform on AWS. It is safe to assume you'll need at least one AWS account and the root or Full Administrator role on that account. The exercises use two accounts - one for infrastructure and another for security - to demonstrate multiple instances of the AWS provider. You can try to use a single account, but things might get a little funky.

Each account should have a group called FullAdministrators with the AdministratorAccess AWS managed policy attached.

There are also three Users created for the exercises. Two in the infra account and one in the security account. You should create these users and assign them the level of access documented in the course. The users are as follows:

Username Account Access
ElVasquez infra FullAdministrators group
JoMcGee infra AmazonRDSFullAccess, AmazonEC2FullAccess, AWSLambdaFullAccess, IAMFullAccess, AmazonDynamoDBFullAccess, AWSCloudFormationFullAccess
JaGibson security FullAdministrators group

MONEY!!!

A gentle reminder about cost. The course will have you creating resources in AWS. Some of the resources are not going to be 100% free. I have tried to use free resources when possible, but EC2 instance, S3 Storage, and RDS all cost money. We're probably talking a couple dollars for the duration of the exercises, but it won't be zero.

Each module builds on the previous one to create a complete deployment for the Globomantics scenario. As I mentioned before, destroying the resources after each module will make things more difficult. For that reason, I waited until the last module to deploy any actual EC2 or RDS instances. Those are the things that will actually cost you money. Once you complete the course, I highly recommend tearing everything down with terraform destroy or by deleting the resources in AWS. CodeBuild and CloudFormation tend to leave some S3 buckets laying around that Terraform does not destroy, so it probably makes sense to spot check through the AWS Console.

You can also use this handy tool to nuke everything in your AWS account. Use with caution!!!

Conclusion

I hope you enjoy taking this course as much as I did creating it. I'd love to hear feedback and suggestions for revisions. Log an issue on this repo or hit me up on Twitter.

Thanks and happy automating!

Ned