Infrastructure Automation with Terraform and AWS
Strengths
Granular Resource Explanation
Instruction provides a detailed breakdown of every code block and resource, explaining the reasoning behind specific configurations.

Create production-grade scalable deployments with GitLab, EC2, ALB, ECS, ECR, VPC, S3 and Infrastructure as Code (IaC).
InstructorMark Winterbottom

Free
Free


FreeInstruction provides a detailed breakdown of every code block and resource, explaining the reasoning behind specific configurations.
Editorial course preview
These 4 complementary views highlight concrete, legible examples from the course presentation.
This architectural diagram illustrates the deployment automation structure, mapping CI/CD tools like GitLab and GitHub to shared AWS resources such as S3, DynamoDB, and ECR.
This diagram displays a collection of icons for various AWS infrastructure components such as ECS, RDS, ALB, VPC, Route 53, IAM, ACM, S3, Subnets, and VPC Endpoints.
This screen recording displays a coding environment where a developer is editing a .gitignore file for a Django project, accompanied by a sidebar listing the video chapters.
This diagram illustrates the relationship between Staging and Production environments, depicting servers and networks linked by a user interface.
The workflow encourages security best practices by utilizing distinct AWS accounts for different environments rather than a single root account.
The curriculum covers automated workflows for both GitHub Actions and GitLab CI/CD.
One signal suggests that certain Terraform state management methods, specifically involving DynamoDB tables, may be deprecated in favor of newer S3 lockfile approaches.
One sampled review suggests that some learners noted a lack of clarity regarding the specific connections between various components, such as how an RDS database interacts with the application.
The curriculum aligns with the goal of transitioning into DevOps via AWS and Terraform automation.