IaC, Git and GitHub learning guide
Learn configuration as code alongside version history, reviews, checks and AWS integration. Choose CloudFormation, Git and GitHub, or CI/CD for your goal.
Manage infrastructure as code: CloudFormation, CDK and Terraform
Start by separating configuration from execution. Then choose CloudFormation/CDK or Terraform for your needs; the branches are alternatives, not one required sequence.
Shared principles and CloudFormation
The first IaC lesson is shared. YAML, changes and drift form the CloudFormation path.
After CloudFormation: AWS CDK
After resources and Ref, connect source code to synthesized artifacts.
An alternative path: Terraform
Start directly from shared IaC concepts; CDK is not a prerequisite. Follow the change workflow into sensitive data.
Compare adoption and migration
After reviewing the relevant mechanisms, compare requirements, ownership and existing resources.
Manage changes with Git and GitHub
Before provisioning a server, learn to record and review file changes. No installation or account is needed. A small SQL edit in the PR lesson connects the stages between proposing a change and delivering it to users.
- Git basics: working tree, staging, commits and branches →
- GitHub basics: Git, repositories, pull requests and collaboration →
- GitHub pull request basics: review a SQL diff, checks and merge →
- GitHub Actions basics: workflows, jobs, runners and permissions →
- GitHub Actions OIDC for AWS: trust conditions, STS and permissions →
The PR lesson explains WHERE and AND where they are used. Continue to OIDC after understanding Actions and IAM role responsibilities. Diagrams and questions are teaching examples, with no live GitHub, AWS or database operations.
After the basics: design CI/CD
After Git, PRs and Actions, connect the conditions between a checked change and user-visible delivery: CI example → stage dependencies → execution identity → artifact verification → release gates → deployment strategies → recovery → postmortems. Choose the topic you need. Lessons distinguish general principles from GitHub/AWS examples.
- What is CI? Automated checks and what passing tests cannot prove →
- CI/CD pipeline design: dependencies, artifacts and deployment targets →
- CI/CD identity design: jobs, credentials and AWS role permissions →
- CI/CD supply-chain security: verify dependencies, digests and provenance →
- CI/CD release gates: match required checks, approvals and the deployed version →
- AWS deployment strategies: ECS rolling, blue/green and canary compared →
- AWS deployment rollback: application recovery and database compatibility →
- Incident postmortems: evidence, customer impact and verified corrective actions →
Examples use fictional inputs and records. No live workflows, destination changes or credential entry are involved.
Continue into infrastructure automation
When you begin managing real infrastructure with tools such as Terraform or Ansible, review the target operating system and networking. Those subjects are not prerequisites for starting the Git and GitHub lessons above.