The CGE-P labs are hands-on: you write Terraform, policies, and pipelines in your own GitHub repo against your own cloud accounts. Every lab guide lives in github.com/GRCEngClub/cgep-labs and is linked from the Labs page.
Start with the setup guide
The first item on the Labs page is a one-time setup guide. Do it before Lab 2.3. It covers:
- Installing Terraform 1.6+, AWS CLI v2, and Git.
- Windows: setting up Git Bash so every command in the guides works as written.
- Connecting the AWS CLI to your account.
- Creating your own
cgep-labsrepo with the folder layout every later lab writes into, plus a.gitignore, and pushing it to GitHub.
New to the terminal? Spend 20 minutes on terminal and Git basics first. The Git chapter in CGE-AUD is a good primer, and the Tech Stack tool walks through installs step by step.
Two repos, not one
| Repo | What goes in it |
|---|---|
Your cgep-labs repo | Every lab from 2.3 to 6.1 |
| Your fork of cgep-app-starter | The capstone only |
Do not put lab work in your capstone fork, or the other way round.
Keep your guides current
The lab guides get fixes as members report issues. Before starting a lab, re-open its guide from the Labs page rather than a copy you saved earlier.
Lab checkboxes
The checkboxes on the Labs page are saved in your browser only. They will not carry over to another computer or browser, and they are not graded. Only the capstone is reviewed.
Getting unstuck
Ask in #studygroup_cge_certs in the Club Slack. The channel's Channel Overview tab collects community study notes and resources, and someone has usually hit your error before. See also Common lab errors.