CI/CD learning guide
Connect change checks, artifacts and release decisions to delivery and verified recovery. Distinguish general principles from their GitHub and AWS application conditions.
Start with Git and GitHub Actions
If these are new, review history → pull requests → Actions checks → AWS federation first. View the Git, PR and Actions learning order →
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.